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

Once or twice a week taskhost.exe slows my computer to a halt! It takes up 25% of my CPU power (ie. 1 processor). I can't kill it an have no idea what it is doing. I imagine that its some kind of window's scheduled activity.

How can I figure out what is causing this problem? How can I stop it?

share|improve this question

2 Answers 2

TaskHost.exe itself is a wrapper for dll or other exe and run as a windows service.

3 things to try

#1

Before spending time hunting down what taskhost actual loaded. Check Event Viewer for errors. That may give out a quick answer or point you to the right direction.

#2

Open Task Manager, go to Processes tab. On menu bar (top), click View -> Select Columns.... In pop-up windows, select Command Line.

That may give you an idea which dll taskhost.exe loaded.

Additionally, pay attention at the path of taskhost.exe. It should be

<Windows directory>\System32\Taskhost.exe

If not, you may have other problem.

#3

Same idea as #2, but use a better tools. Download Process Explorer from Microsoft. It is free. It is able to give more details of running process.

share|improve this answer
    
The path of taskhost.exe is simply: "taskhost.exe $(Arg0)". I've downloaded and run the latest Microsoft Security Essentials and it detected no viruses. –  user145395 Nov 14 '12 at 22:15
    
What windows version are you running? Do apply all patches from MS? –  John Siu Nov 15 '12 at 3:06
    
Yes system is up to date. I actually just figured this out finally. About to post an answer. –  user145395 Nov 15 '12 at 19:51
    
#2 is extremely useful, thanks. I am using Windows 8, it's a little different there - open task manager, tab 'Processes', right click on the column headers, then check the command line column. –  Martin Hansen Sep 7 at 12:23

Turns out this was caused by the "RacTask" (Reliability Analysis Custom Handler). I used the Task Scheduler to view "All Running Tasks" and then killed it from there. The problem was immediately addressed.

http://screencast.com/t/1LJUbkdNGbwS

The suggestion to try this was taken from this thread...

http://www.tomshardware.com/forum/5032-63-taskhost-running

share|improve this answer
    
Very nice to see solution feed back! Learn something new. –  John Siu Nov 15 '12 at 21:53
    
So how did you find out what task it was? What method did you use? –  Martin Hansen Sep 7 at 12:21

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.