Monday, August 14, 2006

Generic Host Process for Win32 Services

The process svchost.exe is doing many kinds of tasks and consequently, there can also be many sources of the error. You have to investigate a bit...

Update from February-March 2007: First, try to follow the instructions at Microsoft KB 931852 related to Windows Update and the Catroot2 folder. If it doesn't fix your problem, try the following recipes, too.

Update from January 2007: Start/Run the command called regedit.exe (Registry editor). Navigate to HKEY_LOCAL_MACHINE\System\
and on the right side, double-click TransportBindName - press delete and give it an empty value. That will close port 445. Also, go to HKEY_LOCAL_MACHINE\Software\Microsoft\OLE and change the value of EnableDCOM from Y to the value N - that will close port 135. If you know how, you may also disable NETbios. Restart the computer and the bug might be gone.

Update: the most efficient way to fix the error in most cases is to install the update offered on this Microsoft page even though this page doesn't explicitly mention the error: choose the update for your correct operating system. It works for 50% of users. Are you among them? Let us know by clicking "fast comments" at the end of the article.

Another hope: Also, 25% of the users can fix the bug by: turning off automatic updates in the Control Panel; going to; manually installing the updates there; rebooting. You can turn on the automatic updates again and pray.

If it doesn't fix the problem but you think you have a problem with svchost.exe and Windows Update - e.g. you're getting an access violation error and/or svchost.exe eats 100% of your CPU time - install KB 927891, to be released as a standard update in May or June 2007. If you add this patch, you should also manually update to the update client WSUS 3.0 and pray.

Original text from 2006:

Everyone who has recently encountered the Windows XP error

should know that this problem with svchost.exe (an executable file that is started to run all kinds of processes that depend on dynamically linked libraries) went away as soon as I updated the drivers for the Hewlett-Packard printers and scanners.

Update May 2007: If your generic host process error is related to Hewlett-Packard drivers, a solution is also explained in KB 821690.

You may find the executable file to update the drivers somewhere in

  • C:\Program Files\HP\ ...
or HP may be replaced by Hewlett-Packard. The subdirectory normally has "update" in it, and you should find and run an EXE file that connects you to the Internet and updates all the drivers automatically. Alternatively, you may try to search for the drivers for your HP device on the Hewlett-Packard website.

In fact, later I found out that I discovered a wheel: Microsoft agrees that the old or expired HP drivers are responsible for the bug. A Hewlett-Packard page offers a more complicated explanation that you will hopefully avoid. It is likely that the microscopic reason of the bug is that the HP drivers incorrectly interact with the firewall.

A new broadband-spread worm - worm.mocbot.a

The major broadband ADSL operators recently had to increase the security because of a worm in Shanghai but believe me that you are probably not infected. If you are, see this Microsoft page.

Update: The update that you may install from the page under the link "Microsoft page" in the previous sentence removes the "generic host process" error in 50 percent of cases/users regardless whether you're infected by a worm or not.

If you're sure that you don't have such a problematic HP software, try to look for other similar programs that might try to be contacting their companies and be killed by the firewall. If the problem appeared suddenly, we are probably talking about your provider's firewall. If you did something yourself, turning your firewall off could also circumvent the problem.

An alternative reason

In the past, the same error was also caused by another problem whose fix is described on another Microsoft page, KB 894391, but it is likely that most people already have installed these hotfixes. But if you have encountered this error message since you installed Windows XP SP2, the Microsoft page will almost certainly apply to you.

See also XP Service Pack 3 final build.


  1. Thank you so much for helping me get rid of the 'Generic Host Process' error... was really a nuisance! :)

  2. This ought to be helpful
    but I have no HP hardware or
    drivers - not even a printer
    But I get the message 'Generic
    Host Process etc when I am
    connected to the internet
    and effectively lose the
    connection - even though
    the connection is not released
    for reloading unless I reboot.

    What do I do?



  4. can i get some solutions for this. This is a urgent requirment for me. I have gone through several links on google and has worked accordingly. No solutions till now.

  5. Had the same problem. Used Avast and Ad-Aware and problem solved.Picked up "warezov and Tenga virus" .Some files I deleted and some repaired. It also resolved an exploit picked up by firewall.

  6. I have the EXACT problem rayk334 has. The error randomly occurs and my internet (DSL) connection is lost, although my connectio manager is still "connected" in the system tray and I cannot disconnect. When I right click desktop connection manager icon, I can select "disconnect" with no results. I have to reboot to gain internet access. This is a major pain in the axx. Please help!!!


  7. hi,very glad to find others with this exact problem,including rayk334's comment that they dont even have HP hardware,me either..I've used XP pro for a few years n never seen this error,but formatted and reinstalled XP a week ago all was ok for 2 days then 'whack' i couldnt be online more than 20mins. downloaded suggested MS updates. reconnected, 2hrs later, yay! still on,Was about to write n say thanx,then..'whack' 2& 1/2hrs that rotten error msg is back! PLEASE HELP...Jenny

  8. I've seen the same problem in my pc while updating my pc with windows update for XP update preventing from another user can't be able to hack. after installing it my pc was raising the same error all the time on booting. I've restored my previous Restore Point and after that the update completed successfully and now my system is running properly.

    moral of story is this error raise due to corrupt installation or something fishy in your system.

    RAVI K.
    CELL : +91 98339 72300

  9. IT works for me 100% thanks to all guys here ,, that really was awesome

    i downloaded the security patch from microsoft link above and, bam

  10. IT works for me 100% thanks to all guys here ,, that really was awesome

    i downloaded the security patch from microsoft link above and, bam

  11. Check out this post on the WSUS Product Team Blog here about the WSUS 3.0 update and svchost issues here:

    Thank you for your help on this issue it has been quite a pain on some of our dell machines. I found it seemed to occur more when the Microsoft Update was selected on the machine rather than just leaving it as a windows update.

  12. Thank you very much for the Generic Host Process fix!

  13. hey there, i followed the steps where i have to change the file names n all.. it worked!! thanks so muchhhh for the post. im really head almost burst thinking about how to rectify this pesky problem.. now it's solved because of this post :)

  14. i noticed that the screenshot of ur generic host has a debug button. mine doesn't. not sure if it means anything. anyway, i tried the link to that microsoft site. i cant seem to find the drive:\WuTemp folder. anyone mind helping? i'd really appreciate it, this problem is so freakin annoying!

  15. *My name's Jonathan*


    DECEMBER 30, 2007

    After 36 hours of no sleep at all in my innumerable attempts to fix this DAMN "Generic Host Process for Win32" error of my Windows XP SP2, here's what I did after tinkering around the configurations. This was the ONLY fix / solution that made that error never show up again (I tell you, those Microsoft hotfixes/updates are useless; even the "port-closer" programs are ineffective, too. This problem isn't caused by a virus, either.)


    1. Turn on your Windows Firewall, and turn off Automatic Updates. Even though you have turned this thing off, you still have to follow the next steps.

    2. Right-click My Computer and click Services. If you want the long way around, go to Control Panel, double-click Administrative Tools, then double click Services.

    3. Double-click Automatic Updates.

    4. If it is running, click Stop.

    5. On the Startup Type drop-down menu, select Disabled.

    6. Click Apply, then click OK.

    Reboot your computer and observe if the error will show up again. (Chances are, it will not do so, anymore!)

    OPTIONAL: Download a copy of the SafeXP program and install it to your computer. (You can find this program on the Internet.) Once installed, open it from Control Panel, apply its recommended settings and reboot your computer.

    I hope that this solution I discovered will make everyone's Windows XP SP2 free from the damn "Generic Host Process for Win32" error!

    If my above fix / solution works for you, let us know as soon as possible.

  16. This comment has been removed because it linked to malicious content. Learn more.

  17. i deleted the two values in the registry which got rid of the generic process error, but now I've lost file sharing with other computers on my network? how do I resolve this.

  18. If you're using XP SP3 this might fix (part of) your problem:

    Good luck.

  19. thanx ravi ur solution was of great help.regedit.exe and deleting the transportnameid and description and restoring the computer to previous check point helped me solve my problem...
    thanx karan

  20. Microsoft Update Patch looks to be the winner.

    I also had problems with this, it just appeared from nowhere and I tried everything: virus checking, regedit, cmd, but nothing worked. It stopped my internet connexion and sound then it started to freeze my whole pc.

    I didn't really want to download the Microsoft Patch because I tought it wouldn't work on my Windows if you know what I mean ;) But I took the WinXP patch and looks like it's doing fine.

    I hope it doesn't come back, because I really can't do anything with my pc if it does. If I'll se some change I'll notify you.

  21. correction: regedit is the winner