WSUS and svchost.exe errors related??

[nshenry03]

I'm not sure if my software distribution folder for wsus is corrupted or what the problem is but we have ~50 computers on our network and 15+ computers have had svchost.exe errors (some 2+ times). These seem to occur after updates are installed from our wsus server. Is there a way to check if these files are corrupted? If so what do I do? Would it be a good idea to run a check disk (how long would that take on 800Gigs?)

 

[Roadki11]

I have been having the same sort of issue for the last 2 or 3 months. I have 90+ pc's assorted XP and 2K and its very random only a small percentage of pc's experience the issue, maybe 5-9 each month. My situation is the random problem pc's dont install the updates, the installer hangs and scvhost pegs the cpu at 100%. Sometimes a reboot fixes the issue sometimes just letting them run like that for 4 hours fixes it, sometimes i have to remove them from WSUS, reboot, then manually install the updates. Issue affects both XP and 2K workstations, and rarely the same machines 2 months in row.

RoadKi11

 

[Roadki11]

Think i will give this a try, dont know if it will help you or not.

http://support.microsoft.com/kb/916089

RoadKi11

 

[porkchopexpress]

I've noticed that on some PC's just turning off the AV software for a couple of mins sometimes allows the install to finish and the CPU returns to normal. Our NOD32 software seemed to prevent the install from finishing this happens expecially with Office 2003 updates.

Also stopping the service and clearing the software distribution folder seems to help sometimes.

Apparently this has been an issue lately due to the catalogue size.

http://myitforum.com/cs2/blogs/rtre...e-response-to-ITMU-updates_2E002E002E00_.aspx

 

[nshenry03]

Not so much a problem with high processor usage (although it has happened on a few) but rather it gives this error in the event log:

Faulting application svchost.exe, version 5.1.2600.2180, faulting module msi.dll, version 3.1.4000.2435, fault address 0x00012780.

and then when the dialog with the error is closed, the machine became unusable (no new executables would start). If left open machine works ok, but hangs on shutdown.

 

[Butwanna]

I think this is related to out of date or corrupt Windows Update Client. We had this on Pc's that never got the proper updated components before being put under WSUS OU's. Someone in this thread mentioned going out and manually installing. Take note when you did that, it took a long time then finally Windows update tells you you need some updated components before it can do it's thing. I did this on a machine that had these symptoms and after the updates to the update client and the Genuine advantage tool was updated, I put it back under WSUS and it all worked great after that.

Another tip: If you have one you know has good update client components and it's not working. Look for WMI corruption by opening WMI properties. If it doesn't say Successfull connection to <local host> then WMI is corrupted.