Why does the Windows Modules Installer Worker require such a high CPU usage?

L

Luisito Ortiz

This service is a resource hog, and it becomes clearer the older a CPU is. Now, I have laptops from 2008, 2012, 2016 up to 2020. The newer CPUs have no issue with the service, but a simple Windows Update brings the Core 2 Duo T6400 to it's knees. If you skip a couple of months of updates, forget about it. I'm better off just installing the next major Windows 10 update fresh in that case. The question is why is this such a resource hog? Note that this laptop has a vanilla Windows 10 64-bit install on an SSD that runs great when not getting updates. Heck, since it has a GPU, I can still run Star Trek Online or Team Fortress 2 on it. The service has always been an issue with how slow it performs on older laptops due to the high CPU usage, but today I got hit extra hard as I hadn't updated in 6 months. In my opinion, an integral part of Windows as updates are shouldn't be something that's resource intensive. Any plans for improving it?

Continue reading...
 
Back
Top Bottom