Broadcom Bluetooth drivers and Win 11 22H2 security situation.

[RangerHawk]

I have a decade of computer tech support myself, so I understand you guys can't fix the issue yourself, but there are options for HTC here to fix this. It should also be noted that HTC is in breach of contract with their customers. 

[BIll Ryder]

This is very disappointing. I want to use core isolation.

I guess I'll have to move off the Vive and leave HTC behind for my next VR purchase. I'm only staying on it for the wireless functionality at the moment.

 

[Jack Warner]

I purchased an HTC Vive, basically at launch, then an HTC Vive Pro, then a wireless adapter, then an HTC Vive Pro 2.  I used the Vive a lot until I started having issues about 2 years ago.  I upgraded from a PC with an Nvidia 2080TI to a new PC with an Nvidia 4080 graphics card about a year ago.  The new PC, for which I paid about $3,000.00, did not solve my issues.  I think part of my problem is the incompatibility of the btwusb.sys driver, which will not let me isolate memory cores.  It is noted above that this driver is required.  Is it required for using the Vive Pro 2 at all, or only if I want to use it with the wireless adapter?

[ZestyLemming]

The original Vive, Vive Wands and Valve Index controllers work fine with the driver removed. The only thing you appear to lose is lighthouse related activities such as turning them on, turning them off or patching firmware wirelessly.

It's likely that Vive Pro / Vive Pro 2 also does not require this driver for any functionality you actually care about to work. It's also likely HTC or Valve could just write a Lighthouse driver for the standard Bluetooth stack to enable the missing functionality for this case, remove the Broadcom chip, and save a few dollars per unit - and then also have an easier time with the FCC, etc. certifications (which are complicated by radios).  However, I don't suspect the people reading this are in a position to, you know, care about any of that.