up vote 3 down vote favorite
share [g+] share [fb]

I'm trying to fix a few low end single core desktops running Vista. In normal use they're fast enough not to be a problem. The issue is that because these machines are only on when being used, primarily for school work, windowsupdate begins installing patches it launches TrustedInstaller which in turn hogs 100% of the CPU and renders the machines all but unusable for however long it takes to patch them.

How can I limit the amount of CPU time TrustedInstaller.exe can have?

link|improve this question
67% accept rate
I found a utility that's designed to cap a processes CPU share. Unfortunately while it works fine on processes I started it can't lock onto trusted installer (running in kernel mode?). deztec.jp/x/05/faireal/BES-index.html – Dan Neely Mar 25 '10 at 1:37
I tested win7 on one of the systems, it's version of Trusted Installer was much better behaved. If nothing else works I might end up recomending for an OS upgrade. – Dan Neely Mar 25 '10 at 13:00
feedback

1 Answer

up vote 0 down vote accepted

When a process is already running, you can call the task manager (or Process Explorer) to lower its priority to idle. This should normally make this process no longer hog 100% of CPU, as it should be the last one in the priority of processes.

However, I don't know how to force a priority for a particular process, for the next times it opens. Maybe someone else will have a way to do that.

Edit: This other question seems to have a good answer on the way to save a priority for a particular process.

link|improve this answer
First thing I tried. I don't know why, but even at the lowest priority it was still devouring the CPU and leaving the rest of the system lagged to unusability. – Dan Neely Mar 25 '10 at 1:35
feedback

Your Answer

 
or
required, but never shown
discard

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