Re: windows update won't stop

YW. We win some, we lose some.

MedRxman wrote:
After trying all the suggestions and even having to do a force (second)
installation of the new installer I gave up and and opted for the "WORK
AROUND"

Thanks for the info!


"PA Bear" <PABearMVP@xxxxxxxxx> wrote in message
news:uhdQ7oJoHHA.1244@xxxxxxxxxxxxxxxxxxxxxxx
Courtesy of MVP Emeritus Ottmar Freudenberger:

1. First install the newly released 'standalone' version of Windows Update
Agent 3.0, v7.0.6000.374
http://support.microsoft.com/kb/932494

Direct Download links:

x86-based versions of Windows (most users)
http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/windowsupdateagent30-x86.exe

x64-based versions of Windows
http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/windowsupdateagent30-x64.exe

Itanium-based versions of Windows
http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/windowsupdateagent30-ia64.exe

2. Now (re)install this (updated) fix:
http://support.microsoft.com/kb/927891

NB: Windows Update/Automatic Updates started offering 927891 on 22 May-07.
If "Update for [Windows XP] (KB927891)" is listed in Add/Remove Programs
(make sure Show Updates box is checked), it's already installed. cf.
http://www.microsoft.com/technet/security/advisory/927891.mspx

3. Reboot.

The MS update team believes that this solves all three svchost problems
that folks have been experiencing. See
http://blogs.technet.com/wsus/archive/2007/05/15/srvhost-msi-issue-follow-up.aspx
and http://blogs.technet.com/wsus/archive/2007/04/28/update-on.aspx

<QP>
It’s important to note that with the MSI fix and the new client installed,
the CPU may still go near 100%, but the system should still be responsive
and not lock up. If another task requires CPU cycles they will be shared,
but if the system is idle, MSI will use the full cycles available. If a
task is running at the same time as MSI, the system may be slightly
slower, but should still be responsive during this time. Key to remember
the MSI fix and the new client address unresponsive or locked systems.
CPU spikes during some scans are expected, machine unresponsiveness is
not. If your watching the process monitor, you will still see 100% CPU
during some scans and this is expected behavior.
</QP>
Source:
http://blogs.technet.com/wsus/archive/2007/05/15/srvhost-msi-issue-follow-up.aspx

Also see
http://www.bleepingcomputer.com/blogs/mowgreen/index.php?showentry=1071
(First try the steps posted May 4th at the beginning of the article.)

Workaround: Change the default from Microsoft Update to Windows Update: Go
to Microsoft Update > Click on Change Settings in left pane > Scroll to
bottom of page > To Stop Using Microsoft Update > Disable Microsoft Update
software and let me use Windows Update only (check). cf.
http://support.microsoft.com/kb/901037

With Windows Update as your default, you will need to check in at Office
Update to keep your Office applications fully patched:
http://office.microsoft.com/en-us/downloads/maincatalog.aspx
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin; DTS-L.org


Richard wrote:
i'm trying to use the windowsupdate website to update my computer.
However
when i click the update button, it tells me it is checking for updates.
the
green bar keeps going across my screen but it never stops. In the past it
would stop and allow me to update my computer. Has anyone else run into
this
problem.

Many thanks,

.