Just a warning that this has noting to do w/Hubitat...it's all about me and Wi-Fi on my laptop.
In the last day or two I got a Windows update on my laptop and my Wi-Fi has been hosed ever since. Every other device in the house is fine. This isn't a Wi-Fi issue, rather it's a SW issue that is blocking me from using my Wi-Fi card in my laptop.
The symptom is that Windows can't use my Wi-Fi device because the device can't be started...info from Device Manager below:
I've run HW tests and the Wi-Fi module is working/receives and sends packets when tested.
Resulting experience:
No Wi-Fi networks found, and Airplane Mode is in accessble:
Windows doesn't see my wi-fi device from Network Settings:
If I'm not connected via etherent I have the "Globe" icon in the task bar - the one that appears when you're not connected to any network.
I've worked w/HP Support (Envy 13t laptop) and Googled extensively and nothing I've tried works from either source has worked:
Uninstalled every version of the driver from my system until the only one left was the built-in MS driver. Didn't help. Use current driver version from HP SW dowload, and current driver version from Intel. Also tried other versions.
Tried reinstalling Windows from Download Windows 10 using the "Update Now" option.
-- This worked last night when it was done, my laptop could connect to Wi-Fi again for the evening. However, this morning it was not working again
Rebooted and shut down and restarted my laptop repeatedly
Diasabled/Re-enabled the device several times
Uninstalled the device and rebooted to let it re-install again several time s
Reset networking settings in Windows (the one w/the five minute wait and then Windows reboots the computer it's own)
My remaining option to clear out whatever sw corruption there is is evidently to re-install windows desctructively - loose all my apps, settings, configurations, etc. Really want to avoid that pain I can.
First time I was disappointed to not have a problem.
Just realized...my first run was just in the \windows\system32 folder. Re-running from \Windows just in case... Unfortunately same result in \Windows folder - nothing found.
I have done this process but minus step 3. I did find that when I was removing drivers, the built-in Windows driver for the Wi-Fi card can't be removed. The "Delete Drivers" option when you uninstall the device goes away when you get down to just the Windows driver.
But I haven't looked for anything else related to Intel Wi-Fi in Programs, so that is a new step. Off to take a look at this. Thanks!
Thanks...I've done that. I've actually been managing my Intel Wi-Fi and Bluetooth drivers via the Intel Driver and Support Assistant almost since I got the laptop. I thought that might be my problem, but going back to the most up-to-date HP version of the driver, or back to the built-in Windows version of the driver didn't help.
Something is clearly not right, but changing drivers has not helped at all so far. The only thing that gave me brief respite was updating to the most current version of windows (as I noted above). The HP tech said that I wasn't up-to-date and updating might help. It did for a few hours, but as noted by the next morning Wi-Fi was broken again.
Below are what the tool finds in my driver store for Intel Network adapters and Bluetooth. Is the general idea that you clean out the drivers from the store so you can start over w/"fresh" copies of the drivers getting added to the store?
I found his wifi card was disabled in the network settings (not devuce manager but the page where it shows all your network cards). And was stubborn about reactivating. What is happening to you sounds strangely like what happened to him.
You'd think that, but when I do HW tests of the card it passes, and it worked for a while last night after I updated teh Windows version. So it seems more like SW/FW issue, than HW.
I have a lot of errors related to the Intel card...
Warning
Source NDIS
The network interface "Intel(R) Wireless-AC 9560 160MHz" has begun resetting. There will be a momentary disruption in network connectivity while the hardware resets. Reason: The network driver requested that it be reset. This network interface has reset 1 time(s) since it was last initialized.
Error
Source NDIS
Miniport Intel(R) Wireless-AC 9560 160MHz, {ab8501d5-10e9-44bb-96e0-1302acf59d4f}, had event Fatal error: The miniport has detected an internal error
Error
Source: Ntwtw08
1. Intel(R) Wireless-AC 9560 160MHz : A required parameter is missing from the registry.
2. Intel(R) Wireless-AC 9560 160MHz : The version number is incorrect for this driver.
3. Intel(R) Wireless-AC 9560 160MHz : Has determined that the network adapter is not functioning properly.
4. Intel(R) Wireless-AC 9560 160MHz : Could not allocate the resources necessary for operation.
Oh crap, the registry. Maybe, try one of the free registry scan tools that are about, just back it up first. And rather than delete or fix all, look at them and see if it’s registered as an issue?
Thinking the same. Also going to remove the Intel driver from the Driver Store so I can start completely fresh there as well. I've done anothe Delet device in Device manager and I'm down to the built-in Windows driver that can't be deleted.
There are a lot of registry cleaners and repair options - but would prefer to use one someone has used and trusts...anyone have a specific suggestion for one they've used or know something about?
Or - avoid? I have used some cleaners in the past, but not for quite a while. Been a while - I may have mosty used the old scanreg from MS, but AFAIK that's no longer available.
Verify that Windows "WLAN AutoConfig" service is running with startup type set to Automatic; if not your adapter won't be seen by Windows:
Enter 'services.msc' into the Windows search box; find the WLAN service near the bottom of the list. It should show 'Running' status; if not try restarting it (right click > Restart). Startup type can also be changed by modifying Properties.
If it doesn't start successfully, check to see if Windows has logged anything helpful (right click on Windows logo in lower left corner > Event viewer).
Btw, re: registry cleaners; I have used CCleaner (Piriform) a few times; it's been OK for me but as they say, YMMV. Create a System Restore point (via System Protection) and backup your registry beforehand, just in case.
