Author: Konstantinos Tsoukalas ,
If you are experiencing a significant decrease in your computer's performance due to high CPU usage caused by the "Windows Modules Installer" service, continue reading below to fix the problem.
The "Windows Modules Installer" or "Trusted Installer" is a Windows service that is responsible for installing, modifying, and removing Windows updates and optional components.
More specifically, the Windows Modules Installer (TrustedInstaller.exe) process is designed to install Windows updates and other system files, but sometimes it can hang or experience other problems that cause it to use too much CPU resources. Some of the most common causes of high CPU usage by the "Windows Modules Installer" service are listed below:
- Pending Windows updates:If there are updates waiting to be installed on your computer, the Windows Modules Installer process runs continuously in the background until they are installed.
- Corrupted System files: If one or more system files are corrupted, the Windows Modules Installer process cannot complete its tasks and uses an excessive amount of CPU resources as it tries to complete the installation of Windows updates.
- Oversized CBSD.LOG file: The Component-Based Servicing file (C:\Windows\Logs\CBS\CBS.log), is a log file maintained by Windows to store information about the components installed or uninstalled during updates. If the CBS. LOG exceeds the size of 2GB, may cause the Windows Module Installer service to use many CPU resources.
In this tutorial you'll find several methods to fix the "Windows Modules Installer/TrustedInstaller" high CPU usage issue on Windows 10/11.
How to Fix High CPU Usage in Windows Modules Installer (TrustedInstaller.exe) on Windows 10/11.
Method 1: Use the Windows Update Troubleshooter
Windows has many built-in tools for troubleshooting operating system problems. "Windows Update Troubleshooter" is one of them and can help you solve the high usage problem caused by the "Windows Modules Installer" process.
1. Press Windows + R keys to open the Run command box.
2. Type the following command nd press Enter.
- ms-settings:troubleshoot
3. Then select Additional troubleshooters if you own Windows 10, or Other troubleshooters in Windows 11.
4. Click on Windows Update and then hit the Run the troubleshooter button.
5. Let the troubleshoot to try to detect and fix the problem and then check if the Windows Modules Installer process is still causing high CPU usage.
Method 2. Delete the Windows Update Store folder.
The second method to fix the Windows Modules Installer high CPU usage issue, is to delete and re-create the Windows Update Store folder ("C:\Windows\SoftwareDistribution"), which is the location where Windows stores the downloaded updates. To do that:
1. Simultaneously press the Windows + R keys to open run command box.
2. In run command box, type: services.msc and press Enter.
3. Right click on Windows Update service and select Stop.
4. Now, open Windows Explorer and explore the contents of "C:\Windows" folder.
5. Locate and Delete the SoftwareDistribution folder.* (Click Continue at "Folder Access Denied" message).
* Note: The next time that the Windows Update will run, a new empty "SoftwareDistribution" folder will be automatically created by Windows to store updates.
6. When done, restart your computer.
7. Check if the problem has been resolved.
Method 3. Delete CBS.LOG & Windows Temp files.
The next method to eliminate the high CPU usage problem caused by the Windows Modules Installer service, is to delete CBS.LOG file which stores information about the changes made to your computer during Windows Update, and the Windows temporary files.
1. Simultaneously press the Windows + R keys to open run command box.
2. In run command box, type: services.msc and press Enter.
3. Right-click on Windows Modules Installer service and click Stop.
4a. Now, navigate to the following folder:
C:\Windows\Logs\CBS
4b. Delete the CBS.LOG file.
5a. Now go to the following folder (press Continue when prompted):
C:\Windows\Temp
5b. Press CTRL + A to select all files and then Delete them.
6. Finally, restart your PC and check if the problem is fixed.
Method 4. FIX Windows Modules Installer High CPU Usage with DISM & SFC tools.
The final method to fix the mentioned problem, is to repair Windows 10/11 by following the steps below:
1. Open command prompt as administrator. To do that:
1. In the Search box type: cmd or command prompt
2. Right click on the command prompt (result) and select Run as Administrator.
2. At the command prompt window, type the following command & press Enter:
- Dism.exe /Online /Cleanup-Image /Restorehealth
3. Be patient until DISM repairs component store. When the operation is completed, (you should be informed that the component store corruption was repaired), give this command and press Enter:
- SFC /SCANNOW
4. When SFC scan is completed, restart your computer.
That's it! Which method worked for you?
Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others.
If this article was useful for you, please consider supporting us by making a donation. Even $1 can a make a huge difference for us in our effort to continue to help others while keeping this site free:
We're hiring
We're looking for part-time or full-time technical writers to join our team! It's about a remote position that qualified tech writers from anywhere in the world can apply. Click here for more details.
- Author
- Recent Posts
Konstantinos Tsoukalas
Konstantinos is the founder and administrator of Wintips.org. Since 1995 he works and provides IT support as a computer and network expert to individuals and large companies. He is specialized in solving problems related to Windows or other Microsoft products (Windows Server, Office, Microsoft 365, etc.).
Latest posts by Konstantinos Tsoukalas (see all)
- FIX: Outlook or Word closes or crashes when typing. (Solved) - September 9, 2024
- FIX: Hyper-V did not find Virtual Machines to import from location. - September 3, 2024
- How to Move a Hyper-V Virtual Machine to another Host? - August 28, 2024