Windows 10: TiWorker.exe Windows Modules Installer Worker high CPU/RAM/Disk usage

Hi, my device is slowing down and the CPU cooler is very loud, I opened the Task Manager and saw Windows Modules Installer Worker using a lot of the CPU, and not that much disk probably because I use an SSD. When running a game, the framerate drops from 240FPS Framerate Per Second to about 30-70. This is how my task manager looks like. I apologize if you cannot read this language, but it's only important to look at the process itself and the CPU load.The process is located under Windows Component Store C:\Windows\WinSxS\..., and has an argument of -Embedding only, so it's not a virus or

:)

 

Windows Modules Installer Worker - high CPU usage

Hi Gregory,

The Windows Modules Installer Worker is a background application that checks for new updates from the Windows server and install them in your computer. It's task takes high usage of CPU that causes load on the system especially when Windows Update is running.

We recommend that you check the following first:

• if your device is running the Scheduled Automatic Maintenance
• if the Windows Update is running and installing

You may check the resolution provided by TnTzzz on this thread.

Update us with the results.

 

Windows Modules Installer Worker - high CPU usage

Windows Modules Installer Worker - high CPU usage

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

I'm running Windows 10 Pro

Version 1703

OS Build 15063.540

Product ID 00330-80000-00000-AA902

Processor AMD A6-3400M APU with Radeon(tm) HD Graphics 1.4 GHZ

Installed RAM 6.00 GB (5.48 GB usable)

System type 64-bit operating system, x64-based processor

Pen and touch No

***Post moved by the Forum Moderator to the appropriate forum category.***

 

How to fix high CPU usage by Windows Modules Installer Worker?

Hi Abhilash,

For us to isolate your concern with high CPU usage by Windows Modules Installer Worker, we would like to know the following:

• Is this the first time you experienced the issue?
• To make sure that we have not missed on anything, what troubleshooting steps have you done so far?
• Have you checked in safe mode if it's the same?

We look forward to your response.