Question

Q: Windows Modules Installer Worker - high CPU usage This thread is locked from future replies

Windows Module installer worker is constantly running with very high CPU usage.

My PC has suddenly ground to a halt.

All the latest updates are installed as well.

I'm running Windows 8.1 Pro 64 + update.

Thanks.

 

 

Answer

A:

In Windows 8 or 8.1 laptop, sometimes CPU fan run very fast and make noise because Windows Module Installer Worker occupies CPU more than 50%.
In this case, you can solve the problem by changing windows update into manual mode.
How to do it:
  1. Open services.msc (In Windows 8, WindowsKey+R and enter services.msc)
  2. Search "Windows module installer". 
  3. Double click the "Windows module installer", and make it manual. It is usually set Automatic. 
  4. Search "Windows update".
  5. Double click the "Windows update", and make it manual. 
  6. Open Control panel (click the right button of your mouse at the lower left of you display monitor or LCD, e.g., at the Windows logo. and then you can see control panel menu)
  7. Click "Windows update"
  8. In left you can see "Change settings"
  9. Change the setting into "Check for updates but let me choose whether to download and install them". It is usually set automatic.
  10. Reboot
The Windows module installer workers cannot bother you anymore. 
Important:
Because Windows update is set manual, you MUST check regularly (weekly or monthly) windows update by yourself. 

Also, cleaning up your disk may help to reduce CPU usage by windows module installer worker

Did this solve your problem?

Sorry this didn't help.

575 people were helped by this reply

Answer

A:

Hey Trek178 you should check if the PC is under schedule maintainance and try to troubleshoot the windows update to check if there was any problems. I've just got a same problem and troubleshoot it. Now it's over
Hope this may help you

Did this solve your problem?

Sorry this didn't help.

497 people were helped by this reply

 
Question Info
Views: 1554061 Last updated: February 7, 2018 Applies to: