Windows Modules Installer Worker - high CPU usage

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.

This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.

Answer

TnTzz

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:

Open services.msc (In Windows 8, WindowsKey+R and enter services.msc)
Search "Windows module installer".
Double click the "Windows module installer", and make it manual. It is usually set Automatic.
Search "Windows update".
Double click the "Windows update", and make it manual.
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)
Click "Windows update"
In left you can see "Change settings"
Change the setting into "Check for updates but let me choose whether to download and install them". It is usually set automatic.
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

770 people were helped by this reply

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Answer

Zodiac3011

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

547 people were helped by this reply