OK, you're talking about two different issues.
Issue #1 is that, when you plug your WM5 device into USB on the PC, the WM5
device will no longer be able to make a WiFi connection. This *is* a
security thing to prevent accidental bridging of whatever WiFi network the
device is hooked to with the PC, which is naturally trusting of the device,
since it's hard-wired via USB. This is something that MS wants the device
to do and has nothing to do with Intel hardware.
Issue #2 is that, when connecting a WM5 device to a PC running Intel WiFi
hardware and with WPA enabled, the PC will drop off of the WPA network. In
some cases, the WPA connection won't be reestablished until the PC is
rebooted, regardless of whether the WM5 device is disconnected or not. The
current thinking is that the Intel driver is responsible for causing the
local machine to drop off of the WPA network when an unsecured network, like
the one created when you plug your device in, is connected. There may be
some other side-effects of using the Intel WiFi manager application, too,
but in all cases reported so far, it's Intel hardware/software that is
responsible. No, Microsoft can't magically change what Intel's code does.
We're assuming that this operation is intentional by Intel and that they are
doing it to secure the WPA network, but we don't know that for a fact. In
any case, it *doesn't* happen on any other devices, clearly pointing at
Intel as the culprit.
Paul T.