Windows 10: yet again with high cpu usage post update modules installer worker...

ok, fair warning, there's a bit of a rant in this plea for help, I am THAT frustrated.



just received 2017-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4022725) last night, installed it, nothing unusual, eg the usual post update windows modules installer worker bs did not happen.

I booted up this morning to do my usual routine, namely star trek online, the risa summer event, went to have breakfast whilst the computer completed its boot routine, came back to find the windows modules installer worker doing its usual chug along like a snail, eating up most of my cpu cycles.

I love windows 10 dont get me wrong, its vastly more reliable in my experience than vista, seven and eight ever were, but this routine windows has post update? rather frankly has me wanting to throw my computer out the window when it happens.

I mean..I cant do anything with it whilst its like this. I'm gonna go play the division on my xbox, and wait for my computer to kindly unfrak itself.

:)

 

Windows Modules Installer Worker - high CPU usage

etc.

So what do I do ?

keep killing the install modules process ? (getting the cpu back) and for the reboot ? just do hibernate and never do a full reboot ?

 

Windows Modules Installer Worker - high CPU usage

If your system is trying to install and update over and over, the file is probably very large and it does explain why the modules installer is constantly running. I have no way to get such a file.

You probably also have a very large CBS.log which another user was complaining about its size or number of archived logs.

Since I do not see any of the updates you reference, could you go to the Settings-System-About and look under Windows specifications and let us know the OS Build version. Is it 16299.214 or something else.

If you do not have that number listed, open an admin command prompt or PowerShell and type
winver to get that number. A small window should open showing the number.

 

Place your computer in clean boot and see if there is any change in performance:


https://support.microsoft.com/en-us/...oot-in-windows
How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki

 

its always done this, in either state. I've been up for an hour and a half and it took that long for it to settle itself.

 

Open administrative command prompt and type or copy and paste these commands:

1) winver (on the pop up view your windows version and build and post into the thread)
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan

After the 4 commands have completed: right click on the top bar of the administrative command prompt box > left click edit then select all > right click the top bar again > left click edit then copy > paste into the thread.

Download and Install the Windows performance recorder (WPR)
Perform tracings when you are experiencing problems.
To launch it open administrative command prompt and type the command wprui.exe
The WPR will create tracings which can be analyzed. The challenge will be learning how to interpret the results or finding someone already trained with the tool.
Windows performance recorder - Microsoft Community

 

at the next occurrence I will do so. as the problem has subsided for the moment, there's no real point.

 

clean boot did nothing to change the situation. I think its something fundamentally to do with how the updates are processed and installed.