If you notice Window modules installer worker eating up your CPU, these tips might help you out.
.
1) run Windows update troubleshooter
Control Panel Troubleshooting View All Windows Update => Right click => Run as Administrator Click Next After the wizard has been run, click Close the troubleshooter
2) run disk cleanup
http://windows.microsoft.com/en-us/windows/delete-files-using-disk-cleanup
Open Administrator CMD prompt C:\>cleanmgr.exe Wait a few minutes for the scanning to complete. Select only [x] Windows Update Cleanup for "Files to delete:". Deselect everything else Click OK
3) If you’re unable to run cleanmgr.exe due to high CPU utilization, you can
clean the WinSXS folder.
This seems to do the same thing than Windows Update cleanup.
C:\>Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase
https://technet.microsoft.com/en-us/library/dn251565.aspx
4) run dism.exe /online
Open Administrator CMD prompt C:\>dism.exe /online /cleanup-image /scanhealth C:\>dism.exe /online /cleanup-image /restorehealth
https://technet.microsoft.com/en-us/library/hh825265.aspx
DISM Operating System Package Servicing Command-Line Options
You can also use these servicing commands to enable or disable Windows features, either offline or on a running Windows installation.
The following operating system package-servicing options are available for a running operating system:
DISM.exe /Online [/Get-Packages | /Get-PackageInfo | /Add-Package | /Remove-Package ] [/Get-Features | /Get-FeatureInfo | /Enable-Feature | /Disable-Feature ] [/Cleanup-Image]
Use /ScanHealth to scan the image for component store corruption. This operation will take several minutes.
Use /RestoreHealth to scan the image for component store corruption, and then perform repair operations automatically. This operation will take several minutes.
July 12, 2017 at 3:42 pm
After updating my windows 10, it start a problem in my pc, High CPU usage. I am just fedup with a lot of windows versions and updates. I suffer few days with this problem. By studying online I found the problem is related with Windows Modules Installer Worker. I followed instructions of an article and it solved my issue. In my opinion, Microsoft should have control releasing Windows versions randomly and to be serious about releasing its updates.
LikeLike