TX2-1000, Broadcom wireless, fried Vista wireless stack

I decided to post this here instead of networking, since it seems machine specific, or maybe something to do with an HP bundled software.

We have a bunch of these tablets for our providers, and so far we have two definitely affected, with signs on of a couple others. This is out of 10 tablets.

Basically, what's happening is, providers in our larger clinic that needs two access points are having issues getting an address from dhcp. They associate with the AP and all, but then fall back on the internal Windows IP when DHCP fails. We noticed that some of the tablets can still pull an IP when connecting with the 2nd AP in the building. Naturally, we threw the AP's on channel 1 and 11 to ensure they weren't interfering with each other, and eventually moved one AP and pulled the other for the time being.

One tablet went so far as not being able to find any signals, as if the radio went out. Reinstalling Windows (used a Win7 upgrade) caused things to function normally.

So today I'm at a providers house helping him setup his network so he can VPN in. I can't get onto the otherwise working wireless with his tablet. It connects, and appears to get an IP, but Vista says it can't see outside the internal network. In reality, it can't even ping the gateway. Using ipconfig reveals its addresses are still 10.x.x.x, which we use at the clinics. His network is 192.168.x.x. Trying /release and /renew makes ipconfig state that it can't operate when the media is disconnected. However, the Windows connection manager is reporting wireless connected with local access. The wired interface functions normally.

Has anyone seen this and gotten to the bottom of it? We plan on upgrading all the machines to Win7 regardless, but we don't know if the same problem will present itself yet.