Update available to install at every shutdown

[Tom]

I'm having a problem with our Windows XP x64 edition computers. We are
currently using WSUS 3 to distribute updates to our systems. The x64 systems,
after installing 50 plus updates, will repeatedly invite users to install
updates at shutdown. While shutting down it indicates that it is in the
process of installing 1 of 1 updates each time. I’ve checked the
WindowsUpdate.log file and tried to follow several solutions found in
Microsoft support (msiexec /u, then /regserver; install update; etc.) to no
avail.

I'm also experiencing a problem trying to install required updates for the
System Center Configuration Manager 2007 console. When I run the prerequisite
scan, it detects the need to install updates to .NET Framework 2 and MMC.
I've installed .NET Framework 3.5 (the latest available) and I've tried to
update MMC (the installer says I have a more recent version already
installed) but the prerequisite checker still reports the same issues.

Specifics: Windows XP Pro x64 edition with SP2 and with Internet Explorer 7
installed. My particular system is a Dell Precision 490 with 8G but the
problem occurs on other platforms as well.

Has anyone else experienced this or am I alone?

Tom

 

[Mark L. Ferguson]

The updates installed by WSUS are chosen by you. I would assume you are
trying to install some update that fails because it is not finding a
requisite driver, probably some 32 bit driver for a 32 bit update. In update
history you can see a list of failed installs, and a rightcl;ick may let you
follow the error and identify that.

--
Please use the Communities guidelines when posting.
http://www.microsoft.com/wn3/locales/help/help_en-us.htm
Use the "Ratings" feature. It helps the new users.
Mark L. Ferguson MS-MVP
https://mvp.support.microsoft.com/profile/Mark.Ferguson

 

[Tom]

Thanks for you input Mark. I've just replaced someone who left our company
for greener pastures and I haven't gotten up to speed yet (I've been at it
for only 2 days . The suggestion about the configuration of the WSUS site
may well be the reason for the repeating cycle of update availability, I'll
have to look into it. Perhaps the issue with the SCCM prerequisites is
unrelated?