jmw7541
asked on
Win 8.1 - network & sharing and firewall icon will not open
When network & sharing or firewall icons are clicked the window opens and shows the spinning wheel but nothing happens - have waited 10 minutes. The only way to close the window is to use task manager. Win 8.1
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks to both John Hurst and Maclean for your input
Tried Maclean first - Turned on Bluetooth but no change
Next tried the input from John Hurst. The solution didn’t work the way I had hoped but it did lead to a fix.
Ran SFC /SCANNOW and shut down. Restart showed no change
Next ran DISM.exe /Online /Cleanup-Image /Scanhealth It took almost two hours to complete instead of 15-20 minutes, but it did complete successfully with no component store corruption
Next ran DISM.exe /Online /Cleanup-Image /Restorehealth. Again it took almost 2 hours but this time did not complete successfully – showed error 0x80240021 and referred to the DISM.log file. This file had a half page of readable text and 4 pages of Chinese characters. At this point decided to back up the data and reload the operating system. System now works
Tried Maclean first - Turned on Bluetooth but no change
Next tried the input from John Hurst. The solution didn’t work the way I had hoped but it did lead to a fix.
Ran SFC /SCANNOW and shut down. Restart showed no change
Next ran DISM.exe /Online /Cleanup-Image /Scanhealth It took almost two hours to complete instead of 15-20 minutes, but it did complete successfully with no component store corruption
Next ran DISM.exe /Online /Cleanup-Image /Restorehealth. Again it took almost 2 hours but this time did not complete successfully – showed error 0x80240021 and referred to the DISM.log file. This file had a half page of readable text and 4 pages of Chinese characters. At this point decided to back up the data and reload the operating system. System now works
@jmw7541 - Thanks for the update and I am glad you got the system fixed.
Unfortunately I am unable to locate the official article on this, but I do recall having had the same issue on Windows 7.