microsoft.public.windowsupdate - Microsoft Windows Update
It takes several minutes for my older machines to check for updates. In some instances this causes a "hang" in which mouse and keyboard control is lost for up to 15 seconds. With process monitor, I see svchost and wuauclt in the process activity monitor both use over 40 seconds of file time. The workstation disks have been defragmented and I've run the server cleanup wizard on the WSUS (3.0) server. I've also re-indexed the database. Does anyone have suggestions for speeding up the client scans or ideas as to what would cause this symptom? Thanks, -Mike
Been running Vista Enterprise for almost a year, with no issues. This problem just began last night. When booting my computer, I have about 1 minute after I reach the desktop before my CPU utilization goes way up. I have a Intel Core2Duo, so the rogue process takes up only 50% (appears to only use 1 core). Even so, I am unable to do just about anything (open windows, close windows, click start menu, ctrl+alt+del). The task manager (if I had it open already) will still update though. I see that *svchost.exe* is using exactly 50% of my CPU, and roughly 42MB ram. Using process explorer, it would appear that the child process of that *svchost.exe* instance is *dwm.exe*. I've disable the Aero interface, and have disabled the *Desktop Window Manager Session Manager service*, so it won't start. The CPU still goes up, only now, there is no child process under *svchost.exe*, and it still goes to 50%. I have left the computer running over 10 minutes, with no change. No hardware or software changes have been made. Antivirus is NOD32 (up-to-date, and even disable for troubleshooting). I am at a loss as to what is the issue. Any ideas? -- duucfho -*windows vista enterprise 32-bit intel core2duo e6400 @ 3.2ghz 2gb pc2-6400 patriot extreme performance 4-4-4-12 @1000 mhz nvidia 8800 gts 320mb @ 640mhz core ocz gamexstream 700w psu antec nine hundred *-
Recently, Automatic Updates has caused 100% CPU utilization. When willther be a fix for this? This is clearly already known throughout other boards and even here.
Has anyone else experienced a memory leak caused by the Windows Management Instrumentation service? I have a seperate copy of svchost.exe (svchostwmi.exe) running only the Windows Management Instrumentation service. Usually this service is lumped in with a lot of other services that you can't just restart (Server, Workstation, etc.). This svchostwmi.exe, if allowed, will use all of the memory in the system and make the system unresponsive. This only occurs on some of my Windows 2003 Enterprise 64-Bit servers (about 6 of them). I currently have a kill script that runs every 4 hours to kill the runaway service. This has been occuring for over a year. My systems are current on patches. Any ideas?