I've read posts all over the internet about (mostly Vista & Win7) high CPU use - searching updates & it hanging forever.
Never read any attempt at explaining actual cause of high CPU use for svchost & wuauserv service.
I read the post on manually d/l Vista kernel updates & installing 1st, then running update - not tried it yet. Before I do that, have couple of questions.
But, the update hanging problem only affects my 32 bit CPU, 32 bit OS Vista laptop - not my Vista x-64, Quad core machine.
I tried everything, including all the MS update Fixit (2 diff ones) & System Update Readiness tools., ran SFC a few times, manual resetting of update components, renaming Software Distribution & Catroot2 folders, re-registering dll's, stopping / starting services - BITS, Cryptoserv, Windows Update; reinstalling Windows Update Agent (already had latest ver) - no joy.
FYI, the WindowsUpdateAgent-7.6-x86.exe (in 32 bit OS), didn't change any dates on update files in System 32. Unless it just "checked if they existed," & skipped them, didn't appear to change anything.
I'm curious why the 32 bit Vista, 2 core machine - needs 50 - 60% CPU - for 12, 18, 24 hrs & still never finishes.
But my Quad core, Vista x64 box, barely uses any CPU & finishes finding updates in a tiny fraction of the time. Spiking a few sec. to 13% on one core, then way less most the time is normal on it. Often drops to 0 CPU for several sec. It might use 2 - 6% and is not constant, like the dual core laptop is. If MS limiting BW on Vista, W7 updates is the problem, a quad core wouldn't finish searching a lot faster that a dual core. I don't think it takes much resources just to search?
My quad core's got more CPU power, but not where the dual core should use 50 - 60% CPU for 18 to 24 hrs straight & still never finish, where the quad core barely uses any..
One recent update attempt on the laptop, control panel UI said no updates found (there were some) - Event Viewer said 31 updates detected, but none installed. No errors on failed installations - anywhere I found. This lead me to suspect corrupted update downloader or installer dll files.
?? Not sure if I should BU & delete the 8 or so WU dll files in system 32, then re-run the update agent installer?