HP Pro x360 Fortis 11 inch G10 Notebook PC
We have over 10,000 of these units, imaged with Windows 10 Enterprise x64 [21H2] getting driver version 126.96.36.199 via HP's MECM Driver Package. They are also running Cisco AnyConnect Secure Mobility Client & Umbrella Roaming Security Module version 4.10.05111.
They had been working just fine since July, up until the last couple of weeks. We are now getting hit with driver version 188.8.131.52 via WUfB. (HP has made 22.170 available and Intel has made 22.180 available, but we have not done any testing with these yet.) We have approximately 25-50 of them per day dropping WiFi connectivity. Sometimes the device is splatted out in device manager and the device appears to be in Airplane mode, but it isn't.
This device cannot start. (Code 10)
The requested operation was unsuccessful
Problem Code 0000000A
Other times WiFi will be enabled and listing SSIDs, but it won't connect. Sometimes a reboot, multiple reboots, or even a lid closure and re-opening will get WiFi working again. If it is driver related, it is not immediate. Sometimes they work the rest of the day or so, then will break.
We also have lots of 6xxx/7xxx Event IDs from source Netwtw10: "The description for EventID xxxx from source Netwtw10 cannot be found. Either the component that raises this event is not installed on your local computer or the information is corrupted. You an install or repair the component on the local computer.
I saw that others reported similar issues, even specific to 22.150, but unfortunately they ghosted Intel support.
Is anyone else seeing this issue? I'm currently trying to reliably reproduce this issue so I can do some testing, but we have only been engaged for 24 hours now. It would be nice if we could confirm a known issue and work on deploying 22.170 or 22.180 to prevent this from continuing. Especially with Christmas coming and losing our devices for a few weeks. I'd hate for them to break off-prem and not have any support available. Then there is the issue of tons of devices potentially coming back after the break that now need immediate attention.
UPDATE: It seems as though this might be occurring after taking the 22.250 update then going to modern standby then being woken up.
Just chatted with Intel support and they confirmed the known issue with older driver versions and advised to go with the latest from Intel since HP is lagging behind. Details below:
Code 10 Solution: