Your Windows computer may face a lag when TrustedInstaller.exe consumes high memory and CPU processing. You need to ensure that this process utilizes an adequate percentage of CPU power.
There’s a simple fix for reducing the high CPU usage caused by the TrustedInstaller.exe process. Before you learn the solution, you need to understand what TrustedInstaller.exe process means.
What is TrustedInstaller.exe Process?
In your Windows 10/8/7, ‘TrustedInstaller.exe’ is a secure process used by Windows Modules Installer service.
It is responsible to allow permissions when you install, remove or update any software on your Windows computer. The TrustedInstaller.exe process enables users to modify Windows Updates and other optional system components.
This process runs with normal Windows startup. As a service, the TrustedInstaller.exe process runs independently under the Local System Account.
Easy Fix for High CPU Usage Caused by TrustedInstaller.exe
Is TrustedInstaller.exe causing high memory and CPU usage? Here’s how you fix it.
There’s only one secure way of fixing this issue. You need to ‘take Ownership’ of the TrustedInstaller.exe file and allow permissions. This reduces the high CPU usage and the TrustedInstaller.exe process consumes minimum memory.
To take ownership of the TrustedInstaller.exe process,
- Open the File Explorer window
- Go to C: drive on My Computer (This PC for Windows 10)
- Open the Windows folder
- Locate the System32 folder and right-click on it
- Select ‘Properties’ from the context menu
- This opens the System32 Properties window
- Go to the Security tab
- Click on ‘Advanced’ button
- Click on the ‘Change’ link next to Owner
- To select a User or Group, click on ‘Check Names’
- Select your current administrator (admin user account)
- Confirm by clicking on OK
- Now, you’ve changed the owner from TrustedInstaller.exe to your selected user account
- Under the Owner section, you need to check the box for ‘Replace owner on subcontainers and objects’
- Click on OK to save changes
- This brings you back to the System32 Properties window
- Now, click on the Edit button
- Select the administrator and allow the Full Control permission
- Click on OK to save the new permissions
This way, your Windows won’t seek TrustedInstaller.exe’s permission to install or uninstall the software.
Consequentially, the TrustedInstaller.exe consumes less memory and doesn’t cause high CPU usage.
Can You Disable TrustedInstaller.exe Process?
You can disable the TrustedInstaller.exe process. But, we suggest you don’t do that. Disabling the TrustedInstaller.exe causes irreproachable harm to your Windows 10/8/7 computer.
The TrustedInstaller.exe process is a protected service developed by Microsoft. It is present in every Windows system and allows you to install anything and everything.
When you disable the TrustedInstaller.exe process, your Windows operating system is unable to install new apps and software updates. And, when you’re unable to update your Windows, you face innumerable problems while using it.
Common risks of an outdated Windows operating system include:
- Device disruptions: When you disable TrustedInstaller.exe, Windows is unable to update device drivers and system adaptors. Your computer is unable to run connected devices, which also include the mouse and the keyboard.
- Prone to ransomware attacks: In business settings, a network of outdated Windows computers get targeted by ransomware. Your computer data is at a greater risk when you disable the TrustedInstaller.exe process.
- Cyber attacks: In addition to ransomware, your Windows computer is at a risk of being attacked by malware, viruses, and other cyber threats.
- Unsecured user experience: Disabled TrustedInstaller.exe process means you can’t protect your confidential data as you cannot update Windows Defender. As a result, you lose valuable information from your computer.
- Incompatibility: Your system is unable to work with other Windows computers that are running on updated versions.
So, it is recommended that you don’t disable the TrustedInstaller.exe process. Instead, you can try fixing the high CPU usage with the solution presented above.