If so, which one? Possibly some other piece of software? Maybe new hardware Windows XP can't completely work with? This is exactly the issues you get when working with ancient code. Zero updates, zero 3rd party apps.
This is fresh install, going to windows updates to check for updates. This is interesting now. My colleague did have exactly this fairly recently and I, being on the high horse I was at the time, told he's just doing something wrong and didn't really take a good notice.
Don't know what he did to the poor thing in the end, offline updates perhaps, but it was hanging there for way more than 4 minutes. I had this problem on 2 XP machines lately for customers. It is a pain. I disabled auto updates all together just to get it to work right. Did you try autopatcher to bring xp up to date? I believe that has been a problem with xp for a while now, disable the windows update service Use sysinternals procexp to check which service inside of service host is actually using the CPU, and then use procmon or windbg to figure out why its hogging CPU.
Once again these are clean installs that are just doing windows updates. It's windows updates, they did something to it. I've noticed this happen but it turned out the machine I had the problem on had a dying motherboard. Is this a common problem for you, or just confined to a single unit?
Multiple services run using this executable. Is it one of the automatic updates services, or something else? If you manually download and install the October cumulative patch, then you should be able to use Windows Update with no problems. The precise download location varies depending on which version of IE you're using. For IE6 go here. IE7 is here.
And IE8 is here. You would think that simply upgrading to the latest version of IE would solve the problem, but it doesn't. You have to manually download and apply the patch for your version of IE. Will Microsoft go in and fix wuauclt. I wouldn't bet on it. Get the first word on what the important tech news really means with the InfoWorld Tech Watch blog.
For the latest developments in business technology news, follow InfoWorld. Match up the PID and you'll see which svchost has which services.
Make a note of these services. Still from the command prompt, taking the processes from the crazy svchost, we want to seperate each service into its own process which will create many svchost. Do that for every service under your crazy svchost. Upon restarting, give the computer some time for an svchost.
Once you see it, mentally note the PID. Compare the PID from the crazy svchost. This will immediately tell you which service is the problem child. In my case, it was themes. The services you made into their own processes - if you want to put them back under the umbrella svchost. Reboot the computer when you're done. Like I said.. It's a great troubleshooting step to probably pin-point the problem. Office Office Exchange Server. Not an IT pro?
Windows Client. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Windows Vista Applications. For compatibility of 3rd party applications, use the ACT forum. Sign in to vote. Thursday, May 10, AM. It started happening right after installing SP3 Cheers, Eden.
Friday, December 28, AM. Cheers Craig. Wednesday, January 23, PM. Regards, Thomas. I also traced the problem to the dhcp client. And by switching to a static IP, worked for me. It worked. I though that perhaps some dll used be the wireless could be the culpid. I then disabled to avoid IP confits the LAN connection and set the wireless network connection to the same static IP to keep things conbstant and again it worked.
No extra CPU time, or memory consumed by svchost. Saturday, May 17, AM. Tuesday, September 2, PM. Saturday, October 18, AM. Wednesday, October 22, PM. Saturday, November 1, PM.
0コメント