Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Does anyone know how to fix issue with TrustedInstaller.exe when it takes a lot of CPU?

Operating system: Windows 2008 x64

Windows' Modules Installer service is set to Manual.

share|improve this question

migrated from stackoverflow.com Mar 15 '10 at 14:17

This question came from our site for professional and enthusiast programmers.

add comment

5 Answers 5

Windows Server 2008 will run TrustedInstaller.exe shortly after rebooting after installing the monthly Windows Updates.

The program will take up ~75-100% of a CPU core for up to ~30 minutes, as it is running the malicious software removal scanning code.

While this is running on a single-core machine, certain programs or services will not work properly, such as SQL Server -- most single-core SQL Server installations will not take connections while the above is running.

So, plan accordingly. After your first reboot, expect a CPU hog.

If you're running on Amazon EC2, it may be wise to make sure to boot up as a dual-core server after installing updates, and then back down to a single-core once TrustedInstaller is done hogging a core.

share|improve this answer
add comment

Don't do any of this, just make sure you're running the latest Service Pack.

share|improve this answer
add comment

You can also try clearing solution and problem history in the "Problem Reports and Solutions" control panel, and turning off problem reporting for all users. It appears that TrustedInstaller.exe periodically polls for solutions for any logged "problems" (i.e. application or system crashes) and this tends to be resource-intensive.

share|improve this answer
add comment

You aren't alone. Others are having issues with TrustedInstaller.exe.

This one looks like the best: TrustedInstaller.exe Process 100% High CPU Usage in Vista Task Manager Fix. Hope that what's true for Vista will do for Win 2k8.

share|improve this answer
add comment

I tried clearing the Problem Reports - didn't help.

Running a blade with 64GB RAM and Trusted installer was making hundreds of processes for each login when we only look for updates at 3:00am - when no one is on the machine.

The way to fix this is the old fashion way - turn off Windows Updates.

share|improve this answer
1  
On Win 7 at least, turning off Windows Updates makes no difference to the problem. –  John Gardeniers Jun 9 '11 at 2:06
    
TrustedInstaller.exe runs under "Windows Modules Installer" service. There are a few reports of it having a memory leak (including myself). marc.durdin.net/2012/02/… –  floyd Aug 2 '12 at 19:53
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.