Post by Locutus deBorg on Jul 19, 2016 18:33:58 GMT -6
Saturday:
whilst running the winders update SVCHOSED.EXE from Wed. night to Saturday day
the screen went black
shut it down with the button
no POST or BOOT after that
so I dumped the following text on one of those update KB number pages:
_ _ _ _ _
not about this particular KB,
but it's a KB number I remembered so I could get to this box (the how can we improve... comment box)
Redmond, we have a problem
apparently windows update has been intentionally broken since agent 7.6.7600.256 in vista and win 7
running SVCHOST.EXE at 100% and eating all the available RAM for up to 90hours before any updates can be installed, and also running for another up to 90 hours before the restart can proceed and another 90 hours after the restart has occurred
this has destroyed one of my laptops with overheating, it is now unbootable because either the graphics chip has died or the CPU has died or worse, both have died due to being run for extended periods at up to 96°C that's over 200°F
currently working on a factory reset HP win 7 SP1 system and it's 12 hours at a time before any updates can be installed
SVCHOST.EXE must finish and release the RAM before updates can actually be installed otherwise they fail
also MSE CANNOT do any Sig. updates while the update agent in SVCHOST.EXE is performing this ridiculous amount of CPU and RAM abuse
get the update agent back to the performance level that 7.4.7600.226 has
I did a recent rebuild of a windows 2000 system
offline installed windows installer 3.1, IE6 SP1, and the update agent 7.4.7600.226
I was done downloading and installing the updates within a couple of hours
vista and win 7 are taking days upon days to get updated
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
don't know if it will actually help or not
but I decided to dump it on them anyway
whilst running the winders update SVCHOSED.EXE from Wed. night to Saturday day
the screen went black
shut it down with the button
no POST or BOOT after that
so I dumped the following text on one of those update KB number pages:
_ _ _ _ _
not about this particular KB,
but it's a KB number I remembered so I could get to this box (the how can we improve... comment box)
Redmond, we have a problem
apparently windows update has been intentionally broken since agent 7.6.7600.256 in vista and win 7
running SVCHOST.EXE at 100% and eating all the available RAM for up to 90hours before any updates can be installed, and also running for another up to 90 hours before the restart can proceed and another 90 hours after the restart has occurred
this has destroyed one of my laptops with overheating, it is now unbootable because either the graphics chip has died or the CPU has died or worse, both have died due to being run for extended periods at up to 96°C that's over 200°F
currently working on a factory reset HP win 7 SP1 system and it's 12 hours at a time before any updates can be installed
SVCHOST.EXE must finish and release the RAM before updates can actually be installed otherwise they fail
also MSE CANNOT do any Sig. updates while the update agent in SVCHOST.EXE is performing this ridiculous amount of CPU and RAM abuse
get the update agent back to the performance level that 7.4.7600.226 has
I did a recent rebuild of a windows 2000 system
offline installed windows installer 3.1, IE6 SP1, and the update agent 7.4.7600.226
I was done downloading and installing the updates within a couple of hours
vista and win 7 are taking days upon days to get updated
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
don't know if it will actually help or not
but I decided to dump it on them anyway