Windows 7 will not shut down

[REDACTED]

After the June Windows update, the "Windows is updating - do not switch off" message stuck at 8%. Using an iPad to search for options, I switched off (after 24 hours), re-booted, rolled back to the previous restore point, used chkdsk, sfs and Avast virus check and all came back "Clear". Installed the MS update that caused the problem and re-booted. Again OK
However Windows will not shut down since. After much checking, it appears that Avast! Antivirus in the Services is the problem. If I manually stop this service then shutdown, the computer will switch off.
Do I uninstall Antivirus then re-install it? If so, where is the source program? Your advice please.

[Asyn]

- Which Avast..? (Free/Pro/IS/Premier)
- Which version..?
- OS..? (32/64 Bit..? - which SP/Build..?)
- Other security related software installed..?
- Which AV(s) did you use before Avast..?

[bob3160]

You could try the following:

Repair Avast:
Control Panel> Program and Features (Add/remove program)>Select Avast> Select Repair. Reboot when completed
https://www.avast.com/faq.php?article=AVKB204

If Repair doesn't fix the problem, try the following:
Clean Install of Avast:
https://goo.gl/4Ptzkf
If you need additional help with the Clean Install, watch this:
https://youtu.be/p-h3myRD51A

[REDACTED]

Thank you Asyn and bob3160 for your replies. I have wasted so much time on this problem that I have had to stop and catch up on other things.
Anyway, the Repair and Clean Install options did not work; I still had to stop the avast! Antivirus Service first to get windows to shut down.
While doing this I had a look at WmiPrvSE.exe using 60 to 90% of the CPU a Microsoft Forum and came across:-

for me the high CPU usage started after a blue screen.. Was resolved thanks to this post using the following steps.

    go to elevated command prompt
     net stop "Windows Management Instrumentation"
    lodctr /r
    net start "Windows Management Instrumentation"

I think that performance counters database got corrupted and the lodctr fixed it but it need it the Windows Management Instrumentation and all dependent services to be stopped.
Wednesday, January 17, 2018 3:51 PM


This stopped the high CPU usage and allowed my computer to shut down. Hooray

BUT it is back when the computer was switched back on. Boo

So why a Windows Server command is fixing a Windows 7 Home Premium operating system problem is for a different Forum.