Boarded the train and tried to connect to Wi-Fi, no luck, explorer mostly working but not the wi-fi button – I was teased networks are available but clicking the little wireless icon nothing happened. Even if I clicked clicked clicked hundreds of times.
Now I could have connected to wi-fi via netsh command but though I’d take a quick look into what might cause this…
Launching Control Panel also resulted in a “blank” screen. Start Screen operation seemed fine.
In Task Manager, I expanded to advanced view and selected Details tab, then right clicked explorer.exe and chose Analyse Wait Chain
Analyse wait change revealed pages of data…
All of these were blocked by svchost.exe with process ID of 976 and thread 7348.
And we found:
I then resorted to Process Explorer (http://live.sysinternals.com/procexp.exe) and selected Explorer.exe and chose Properties
Looking at the stack I notice netprofm …
To then I did the save for svchost.exe and process ID 976 … and what do we have in this list…none other then netprofm we saw earlier. We could also use this to translate the Thread ID we found into the service.
Note: IF this is not showing any details make sure you have symbols configured (http://support.microsoft.com/kb/311503), and you run ProcExp as admin (File -> Show Details for All Processes)
This matches up with our Network List Service
However I couldn’t stop the service.
I killed off Explorer
Then service immediately stopped. I restarted Explorer through File -> Run New Task -> Explorer
The Explorer hang was gone, and wi-fi could finally be connected!
Oh and now analyse wait chain on explorer.exe it looks happy:
If I see this re-occur frequently I might investigate further as to why netprofm is hanging up explorer…let me know if you see this issue yourself.