New behavior by machine at shutdown after MS updates

On a Windows XP, SP2, machine I administer Microsoft Updates (9) were
successfully downloaded and installed on April 24, 2009. After completion of
these updates I was advised the machine had to be shut down and restarted.

On invoking shutdown the Windows interface directed me to turn the machine
OFF instead of doing a shutdown and restart. When I did as directed, the
machine then indicated it was "installing updates" - a process that took a
few minutes. Then the machine shut down completely.

After restarting the machine it froze completely during user sign on, after
reboot. Even the system tray clock froze - for 15 minutes, until I did a hard
- count to 5 seconds - shutdown.

The next startup sequence seemed normal - however I have had two periods of
temoprary virtual stops - mouse responsive, clock normal, nothing else moving
- which lasted more than 5 minutes. (Task manager would not load during these
periods, so I cannot report on system resource utilization.)

I regard this as a low priority "issue" but would like to know if other
users have experienced similar system responses? Can anyone tell me what
causes the need for a complete shutdown, and install of updates during this
shutdown process?

Is this behavior by Windows after an MS update expected and "normal"? I've
never seen it before.
--
Sig under construction

Jim Pivonka wrote:
> On a Windows XP, SP2, machine I administer Microsoft Updates (9)
> were successfully downloaded and installed on April 24, 2009. After
> completion of these updates I was advised the machine had to be
> shut down and restarted.
>
> On invoking shutdown the Windows interface directed me to turn the
> machine OFF instead of doing a shutdown and restart. When I did as
> directed, the machine then indicated it was "installing updates" -
> a process that took a few minutes. Then the machine shut down
> completely.
>
> After restarting the machine it froze completely during user sign
> on, after reboot. Even the system tray clock froze - for 15
> minutes, until I did a hard - count to 5 seconds - shutdown.
>
> The next startup sequence seemed normal - however I have had two
> periods of temoprary virtual stops - mouse responsive, clock
> normal, nothing else moving - which lasted more than 5 minutes.
> (Task manager would not load during these periods, so I cannot
> report on system resource utilization.)
>
> I regard this as a low priority "issue" but would like to know if
> other users have experienced similar system responses? Can anyone
> tell me what causes the need for a complete shutdown, and install
> of updates during this shutdown process?
>
> Is this behavior by Windows after an MS update expected and
> "normal"? I've never seen it before.

Some updates are 'received better' with multiple reboots. However - no - on
the few thousand machines I have updated lately - I have not seen that.

Is there some possible software and/or possible hardware issues that have
kept you from upgrading said machine(s) to SP3?

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

Is Automatic Updates (AU) set to the Automatic, the Download but Notify, or
the Notify Only option (cf. http://support.microsoft.com/kb/306525)?

Did the AU prompt include an "Install updates and restart" option?

What are the nine (9) KB numbers for the updates which were installed (see
Update History section of http://windowsupdate.microsoft.com)?

Are you certain that WinXP SP3 hasn't been installedd yet?
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002


Jim Pivonka wrote:
> On a Windows XP, SP2, machine I administer Microsoft Updates (9) were
> successfully downloaded and installed on April 24, 2009. After completion
> of
> these updates I was advised the machine had to be shut down and restarted.
>
> On invoking shutdown the Windows interface directed me to turn the machine
> OFF instead of doing a shutdown and restart. When I did as directed, the
> machine then indicated it was "installing updates" - a process that took a
> few minutes. Then the machine shut down completely.
>
> After restarting the machine it froze completely during user sign on,
> after
> reboot. Even the system tray clock froze - for 15 minutes, until I did a
> hard - count to 5 seconds - shutdown.
>
> The next startup sequence seemed normal - however I have had two periods
> of
> temoprary virtual stops - mouse responsive, clock normal, nothing else
> moving - which lasted more than 5 minutes. (Task manager would not load
> during these periods, so I cannot report on system resource utilization.)
>
> I regard this as a low priority "issue" but would like to know if other
> users have experienced similar system responses? Can anyone tell me what
> causes the need for a complete shutdown, and install of updates during
> this
> shutdown process?
>
> Is this behavior by Windows after an MS update expected and "normal"? I've
> never seen it before.

With respect to SP3 - I have not updated with SP3 because of reports that
the machine will need extensive "pre-update" work to avoid unanticipated post
update behaviors - such as applications not working, incompatibilities
between installed programs and new SP3 features, incompatibilities between my
stystem settings (such as services allowed to run) and settings required to
run in SP3, etc.

I've not had the time, yet, to validate those reports and do any necessary
backups and preupdate preparation that is actually needed.

I am somewhat concerned that you have not seen this behavior before -
assuming that you are referring to updates occurring during the total
shutdown of the machine, and after Automatic Update reported successful
installation of updates. I have actually seen this "special" post update
total shutdown instruction on two machines recently, but in the first case
did not pay much attention.

Though I have not received "" email for your response
I have on another issue - and the links within that email returned blank
pages, no error messages. Ill have to track responses manually, I suspect.


--
Sig under construction


"Shenan Stanley" wrote:

> Jim Pivonka wrote:
> > On a Windows XP, SP2, machine I administer . . .
.. . .

> >
> > Is this behavior by Windows after an MS update expected and
> > "normal"? I've never seen it before.
>
> Some updates are 'received better' with multiple reboots. However - no - on
> the few thousand machines I have updated lately - I have not seen that.
>
> Is there some possible software and/or possible hardware issues that have
> kept you from upgrading said machine(s) to SP3?
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>
>
>

My Automatic Updates routine: I have AU set to notify only. Upon
notification, after closing down what I am working on, I open Services and
set Automatic

Updates, BITS, and Workstation to startup type Automatic. (Event log always
runs; I do not recall why I started enabling Workstation during WU sessions.)
I

then reboot the machine, verify that all three services have started, and
open Control Panel > Automatic Updates. I select the option "Install updates
from

the Windows Update Web site, and download and install the updates.

I do not recall the AU prompt including an "Install updates and restart"
option.

The updates installed list I was able to retrieve includes only 7 updates;
the count of 9 may have included the two install actions which occurred
during the

shutdown, but at any rate this is what I have retrieved:
KB923561 Security Update XP kbid=923561 4/24/2009 7:13:54 PM
KB961373 Security Update XP kbid=961373 4/24/2009 7:14:06 PM
KB956572 Security Update XP kbid=956572 4/24/2009 7:14:30 PM
KB952004 Security Update XP kbid=952004 4/24/2009 7:14:43 PM
KB960803 Security Update XP kbid=960803 4/24/2009 7:14:52 PM
KB959426 Security Update XP kbid=959426 4/24/2009 7:15:02 PM
KB963027-IE7 Security U I E 7 kbid=963027-IE7 4/24/2009 7:15:33 PM

If I get a different result from the Update History section of
http://windowsupdate.microsoft.com I will post that.

Thanks very much for your help.
--
Sig under construction


"PA Bear [MS MVP]" wrote:

> Is Automatic Updates (AU) set to the Automatic, the Download but Notify, or
> the Notify Only option (cf. http://support.microsoft.com/kb/306525)?
>
> Did the AU prompt include an "Install updates and restart" option?
>
> What are the nine (9) KB numbers for the updates which were installed (see
> Update History section of http://windowsupdate.microsoft.com)?
>
> Are you certain that WinXP SP3 hasn't been installedd yet?
> --
> ~Robear Dyer (PA Bear)
> MS MVP-IE, Mail, Security, Windows Client - since 2002
>
>
> Jim Pivonka wrote:
> > On a Windows XP, SP2, machine I administer Microsoft Updates (9) were
> > successfully downloaded and installed on April 24, 2009. After completion
> > of
> > these updates I was advised the machine had to be shut down and restarted.
> >
> > On invoking shutdown the Windows interface directed me to turn the machine
> > OFF instead of doing a shutdown and restart. When I did as directed, the
> > machine then indicated it was "installing updates" - a process that took a
> > few minutes. Then the machine shut down completely.
> >
> > After restarting the machine it froze completely during user sign on,
> > after
> > reboot. Even the system tray clock froze - for 15 minutes, until I did a
> > hard - count to 5 seconds - shutdown.
> >
> > The next startup sequence seemed normal - however I have had two periods
> > of
> > temoprary virtual stops - mouse responsive, clock normal, nothing else
> > moving - which lasted more than 5 minutes. (Task manager would not load
> > during these periods, so I cannot report on system resource utilization.)
> >
> > I regard this as a low priority "issue" but would like to know if other
> > users have experienced similar system responses? Can anyone tell me what
> > causes the need for a complete shutdown, and install of updates during
> > this
> > shutdown process?
> >
> > Is this behavior by Windows after an MS update expected and "normal"? I've
> > never seen it before.
>
>

Why are the Automatic Updates and BITS services set to anything other than
Automatic at all times?

As only seven (7) of the nine (9) approved updates installed, one would
assume that you'd see "Update is not allowed to download due to regulation"
entries in windowsupdate.log for the other two (2) updates. See
http://support.microsoft.com/kb/910340

You should be able to install the remaining updates via Windows/Microsoft
Update (WinXP) or running Windows Update manually (Vista) instead:
Understand that by doing so, you're pushing all other Automatic Updates
users further back in the queue (which may explain, at least in part, why
Automatic Updates hasn't brought them in for you yet).

If you feel one or more of the updates you've installed have caused
problems:

Start a free Windows Update support incident request:
https://support.microsoft.com/oas/de...spx?gprid=6527

For home users, no-charge support is available by calling 1-866-PCSAFETY in
the United States and in Canada or by contacting your local Microsoft
subsidiary. There is no-charge for support calls that are associated with
security updates. When you call, clearly state that your problem is related
to a Security Update and cite the update's KB number (e.g., KB999999).

If your problem relates to a Cumulative Security Update for IE (e.g.,
KB963027), call the above number and ask to be transferred to the "Consumer
IE queue" (which is 47830).

Support for Windows Update:
http://support.microsoft.com/gp/wusupport

For more information about how to contact your local Microsoft subsidiary
for security update support issues, visit the International Support Web
site: http://support.microsoft.com/common/international.aspx

For enterprise customers, support for security updates is available through
your usual support contacts.
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin; DTS-L.net


Jim Pivonka wrote:
> My Automatic Updates routine: I have AU set to notify only. Upon
> notification, after closing down what I am working on, I open Services and
> set Automatic
> Updates, BITS, and Workstation to startup type Automatic. (Event log
> always
> runs; I do not recall why I started enabling Workstation during WU
> sessions.)
>
> I then reboot the machine, verify that all three services have started,
> and
> open Control Panel > Automatic Updates. I select the option "Install
> updates from the Windows Update Web site, and download and install the
> updates.
>
> I do not recall the AU prompt including an "Install updates and restart"
> option.
>
> The updates installed list I was able to retrieve includes only 7 updates;
> the count of 9 may have included the two install actions which occurred
> during the shutdown, but at any rate this is what I have retrieved:
>
> KB923561 Security Update XP kbid=923561 4/24/2009 7:13:54 PM
> KB961373 Security Update XP kbid=961373 4/24/2009 7:14:06 PM
> KB956572 Security Update XP kbid=956572 4/24/2009 7:14:30 PM
> KB952004 Security Update XP kbid=952004 4/24/2009 7:14:43 PM
> KB960803 Security Update XP kbid=960803 4/24/2009 7:14:52 PM
> KB959426 Security Update XP kbid=959426 4/24/2009 7:15:02 PM
> KB963027-IE7 Security U I E 7 kbid=963027-IE7 4/24/2009 7:15:33 PM
>
> If I get a different result from the Update History section of
> http://windowsupdate.microsoft.com I will post that.
>
> Thanks very much for your help.
>
> PA Bear wrote:
>> Is Automatic Updates (AU) set to the Automatic, the Download but Notify,
>> or
>> the Notify Only option (cf. http://support.microsoft.com/kb/306525)?
>>
>> Did the AU prompt include an "Install updates and restart" option?
>>
>> What are the nine (9) KB numbers for the updates which were installed
>> (see
>> Update History section of http://windowsupdate.microsoft.com)?
>>
>> Are you certain that WinXP SP3 hasn't been [installed] yet?
>> --
>> ~Robear Dyer (PA Bear)
>> MS MVP-IE, Mail, Security, Windows Client - since 2002
>>
>>
>> Jim Pivonka wrote:
>>> On a Windows XP, SP2, machine I administer Microsoft Updates (9) were
>>> successfully downloaded and installed on April 24, 2009. After
>>> completion
>>> of
>>> these updates I was advised the machine had to be shut down and
>>> restarted.
>>>
>>> On invoking shutdown the Windows interface directed me to turn the
>>> machine
>>> OFF instead of doing a shutdown and restart. When I did as directed, the
>>> machine then indicated it was "installing updates" - a process that took
>>> a
>>> few minutes. Then the machine shut down completely.
>>>
>>> After restarting the machine it froze completely during user sign on,
>>> after
>>> reboot. Even the system tray clock froze - for 15 minutes, until I did a
>>> hard - count to 5 seconds - shutdown.
>>>
>>> The next startup sequence seemed normal - however I have had two periods
>>> of
>>> temoprary virtual stops - mouse responsive, clock normal, nothing else
>>> moving - which lasted more than 5 minutes. (Task manager would not load
>>> during these periods, so I cannot report on system resource
>>> utilization.)
>>>
>>> I regard this as a low priority "issue" but would like to know if other
>>> users have experienced similar system responses? Can anyone tell me what
>>> causes the need for a complete shutdown, and install of updates during
>>> this
>>> shutdown process?
>>>
>>> Is this behavior by Windows after an MS update expected and "normal"?
>>> I've
>>> never seen it before.

Apologies for the long delay in responding. We had difficulties that made it
impossible to access and analyze the automatic update history and
windowsupdate.log until the last couple of hours.

When I was able to restart the system to check those records I was offered
the IE8 update and Power Point Update. Both downloaded and installed
successfully.

Inspection of both the windowsupdate.log and the Microsoft History disclosed
that 9, not 7 updates were successful on April 24. The two which were not
listed earlier are the Windows Genuine Advantage Notification (KB905474) and
the Windows Malicious Software Removal Tool - April 2009 (KB890830)

The earlier indication that only 7 updates had been successful was
apparently a false result from the tool I used to check updates until I was
unable to shut down the machine and do it right (due to work in progress that
could not be suspended).

Thanks for helping me out with this. I'm learning how to read that log -
it's not all that simple. Jim P.
--
Sig under construction


"PA Bear [MS MVP]" wrote:

> Why are the Automatic Updates and BITS services set to anything other than
> Automatic at all times?
>
> As only seven (7) of the nine (9) approved updates installed, one would
> assume that you'd see "Update is not allowed to download due to regulation"
> entries in windowsupdate.log for the other two (2) updates. See
> http://support.microsoft.com/kb/910340
>
> You should be able to install the remaining updates via Windows/Microsoft
> Update (WinXP) or running Windows Update manually (Vista) instead:
> Understand that by doing so, you're pushing all other Automatic Updates
> users further back in the queue (which may explain, at least in part, why
> Automatic Updates hasn't brought them in for you yet).
>
> If you feel one or more of the updates you've installed have caused
> problems:
>
> Start a free Windows Update support incident request:
> https://support.microsoft.com/oas/de...spx?gprid=6527
>
> For home users, no-charge support is available by calling 1-866-PCSAFETY in
> the United States and in Canada or by contacting your local Microsoft
> subsidiary. There is no-charge for support calls that are associated with
> security updates. When you call, clearly state that your problem is related
> to a Security Update and cite the update's KB number (e.g., KB999999).
>
> If your problem relates to a Cumulative Security Update for IE (e.g.,
> KB963027), call the above number and ask to be transferred to the "Consumer
> IE queue" (which is 47830).
>
> Support for Windows Update:
> http://support.microsoft.com/gp/wusupport
>
> For more information about how to contact your local Microsoft subsidiary
> for security update support issues, visit the International Support Web
> site: http://support.microsoft.com/common/international.aspx
>
> For enterprise customers, support for security updates is available through
> your usual support contacts.
> --
> ~Robear Dyer (PA Bear)
> MS MVP-Windows (IE, OE, Security, Shell/User)
> AumHa VSOP & Admin; DTS-L.net
>
>
> Jim Pivonka wrote:
> > My Automatic Updates routine: I have AU set to notify only. Upon
> > notification, after closing down what I am working on, I open Services and
> > set Automatic
> > Updates, BITS, and Workstation to startup type Automatic. (Event log
> > always
> > runs; I do not recall why I started enabling Workstation during WU
> > sessions.)
> >
> > I then reboot the machine, verify that all three services have started,
> > and
> > open Control Panel > Automatic Updates. I select the option "Install
> > updates from the Windows Update Web site, and download and install the
> > updates.
> >
> > I do not recall the AU prompt including an "Install updates and restart"
> > option.
> >
> > The updates installed list I was able to retrieve includes only 7 updates;
> > the count of 9 may have included the two install actions which occurred
> > during the shutdown, but at any rate this is what I have retrieved:
> >
> > KB923561 Security Update XP kbid=923561 4/24/2009 7:13:54 PM
> > KB961373 Security Update XP kbid=961373 4/24/2009 7:14:06 PM
> > KB956572 Security Update XP kbid=956572 4/24/2009 7:14:30 PM
> > KB952004 Security Update XP kbid=952004 4/24/2009 7:14:43 PM
> > KB960803 Security Update XP kbid=960803 4/24/2009 7:14:52 PM
> > KB959426 Security Update XP kbid=959426 4/24/2009 7:15:02 PM
> > KB963027-IE7 Security U I E 7 kbid=963027-IE7 4/24/2009 7:15:33 PM
> >
> > If I get a different result from the Update History section of
> > http://windowsupdate.microsoft.com I will post that.
> >
> > Thanks very much for your help.
> >
> > PA Bear wrote:
> >> Is Automatic Updates (AU) set to the Automatic, the Download but Notify,
> >> or
> >> the Notify Only option (cf. http://support.microsoft.com/kb/306525)?
> >>
> >> Did the AU prompt include an "Install updates and restart" option?
> >>
> >> What are the nine (9) KB numbers for the updates which were installed
> >> (see
> >> Update History section of http://windowsupdate.microsoft.com)?
> >>
> >> Are you certain that WinXP SP3 hasn't been [installed] yet?
> >> --
> >> ~Robear Dyer (PA Bear)
> >> MS MVP-IE, Mail, Security, Windows Client - since 2002
> >>
> >>
> >> Jim Pivonka wrote:
> >>> On a Windows XP, SP2, machine I administer Microsoft Updates (9) were
> >>> successfully downloaded and installed on April 24, 2009. After
> >>> completion
> >>> of
> >>> these updates I was advised the machine had to be shut down and
> >>> restarted.
> >>>
> >>> On invoking shutdown the Windows interface directed me to turn the
> >>> machine
> >>> OFF instead of doing a shutdown and restart. When I did as directed, the
> >>> machine then indicated it was "installing updates" - a process that took
> >>> a
> >>> few minutes. Then the machine shut down completely.
> >>>
> >>> After restarting the machine it froze completely during user sign on,
> >>> after
> >>> reboot. Even the system tray clock froze - for 15 minutes, until I did a
> >>> hard - count to 5 seconds - shutdown.
> >>>
> >>> The next startup sequence seemed normal - however I have had two periods
> >>> of
> >>> temoprary virtual stops - mouse responsive, clock normal, nothing else
> >>> moving - which lasted more than 5 minutes. (Task manager would not load
> >>> during these periods, so I cannot report on system resource
> >>> utilization.)
> >>>
> >>> I regard this as a low priority "issue" but would like to know if other
> >>> users have experienced similar system responses? Can anyone tell me what
> >>> causes the need for a complete shutdown, and install of updates during
> >>> this
> >>> shutdown process?
> >>>
> >>> Is this behavior by Windows after an MS update expected and "normal"?
> >>> I've
> >>> never seen it before.
>
>

YW & thanks for this follow-up, Jim.

Jim Pivonka wrote:
> Apologies for the long delay in responding. We had difficulties that made
> it
> impossible to access and analyze the automatic update history and
> windowsupdate.log until the last couple of hours.
>
> When I was able to restart the system to check those records I was offered
> the IE8 update and Power Point Update. Both downloaded and installed
> successfully.
>
> Inspection of both the windowsupdate.log and the Microsoft History
> disclosed
> that 9, not 7 updates were successful on April 24. The two which were not
> listed earlier are the Windows Genuine Advantage Notification (KB905474)
> and
> the Windows Malicious Software Removal Tool - April 2009 (KB890830)
>
> The earlier indication that only 7 updates had been successful was
> apparently a false result from the tool I used to check updates until I
> was
> unable to shut down the machine and do it right (due to work in progress
> that could not be suspended).
>
> Thanks for helping me out with this. I'm learning how to read that log -
> it's not all that simple. Jim P.
>
>> Why are the Automatic Updates and BITS services set to anything other
>> than
>> Automatic at all times?
>>
>> As only seven (7) of the nine (9) approved updates installed, one would
>> assume that you'd see "Update is not allowed to download due to
>> regulation"
>> entries in windowsupdate.log for the other two (2) updates. See
>> http://support.microsoft.com/kb/910340
>>
>> You should be able to install the remaining updates via Windows/Microsoft
>> Update (WinXP) or running Windows Update manually (Vista) instead:
>> Understand that by doing so, you're pushing all other Automatic Updates
>> users further back in the queue (which may explain, at least in part, why
>> Automatic Updates hasn't brought them in for you yet).
>>
>> If you feel one or more of the updates you've installed have caused
>> problems:
>>
>> Start a free Windows Update support incident request:
>> https://support.microsoft.com/oas/de...spx?gprid=6527
>>
>> For home users, no-charge support is available by calling 1-866-PCSAFETY
>> in
>> the United States and in Canada or by contacting your local Microsoft
>> subsidiary. There is no-charge for support calls that are associated
>> with
>> security updates. When you call, clearly state that your problem is
>> related to a Security Update and cite the update's KB number (e.g.,
>> KB999999).
>>
>> If your problem relates to a Cumulative Security Update for IE (e.g.,
>> KB963027), call the above number and ask to be transferred to the
>> "Consumer
>> IE queue" (which is 47830).
>>
>> Support for Windows Update:
>> http://support.microsoft.com/gp/wusupport
>>
>> For more information about how to contact your local Microsoft subsidiary
>> for security update support issues, visit the International Support Web
>> site: http://support.microsoft.com/common/international.aspx
>>
>> For enterprise customers, support for security updates is available
>> through
>> your usual support contacts.
>> --
>> ~Robear Dyer (PA Bear)
>> MS MVP-Windows (IE, OE, Security, Shell/User)
>> AumHa VSOP & Admin; DTS-L.net
>>
>>
>> Jim Pivonka wrote:
>>> My Automatic Updates routine: I have AU set to notify only. Upon
>>> notification, after closing down what I am working on, I open Services
>>> and
>>> set Automatic
>>> Updates, BITS, and Workstation to startup type Automatic. (Event log
>>> always
>>> runs; I do not recall why I started enabling Workstation during WU
>>> sessions.)
>>>
>>> I then reboot the machine, verify that all three services have started,
>>> and
>>> open Control Panel > Automatic Updates. I select the option "Install
>>> updates from the Windows Update Web site, and download and install the
>>> updates.
>>>
>>> I do not recall the AU prompt including an "Install updates and restart"
>>> option.
>>>
>>> The updates installed list I was able to retrieve includes only 7
>>> updates;
>>> the count of 9 may have included the two install actions which occurred
>>> during the shutdown, but at any rate this is what I have retrieved:
>>>
>>> KB923561 Security Update XP kbid=923561 4/24/2009 7:13:54 PM
>>> KB961373 Security Update XP kbid=961373 4/24/2009 7:14:06 PM
>>> KB956572 Security Update XP kbid=956572 4/24/2009 7:14:30 PM
>>> KB952004 Security Update XP kbid=952004 4/24/2009 7:14:43 PM
>>> KB960803 Security Update XP kbid=960803 4/24/2009 7:14:52 PM
>>> KB959426 Security Update XP kbid=959426 4/24/2009 7:15:02 PM
>>> KB963027-IE7 Security U I E 7 kbid=963027-IE7 4/24/2009 7:15:33 PM
>>>
>>> If I get a different result from the Update History section of
>>> http://windowsupdate.microsoft.com I will post that.
>>>
>>> Thanks very much for your help.
>>>
>>> PA Bear wrote:
>>>> Is Automatic Updates (AU) set to the Automatic, the Download but
>>>> Notify,
>>>> or
>>>> the Notify Only option (cf. http://support.microsoft.com/kb/306525)?
>>>>
>>>> Did the AU prompt include an "Install updates and restart" option?
>>>>
>>>> What are the nine (9) KB numbers for the updates which were installed
>>>> (see
>>>> Update History section of http://windowsupdate.microsoft.com)?
>>>>
>>>> Are you certain that WinXP SP3 hasn't been [installed] yet?
>>>> --
>>>> ~Robear Dyer (PA Bear)
>>>> MS MVP-IE, Mail, Security, Windows Client - since 2002
>>>>
>>>>
>>>> Jim Pivonka wrote:
>>>>> On a Windows XP, SP2, machine I administer Microsoft Updates (9) were
>>>>> successfully downloaded and installed on April 24, 2009. After
>>>>> completion
>>>>> of
>>>>> these updates I was advised the machine had to be shut down and
>>>>> restarted.
>>>>>
>>>>> On invoking shutdown the Windows interface directed me to turn the
>>>>> machine
>>>>> OFF instead of doing a shutdown and restart. When I did as directed,
>>>>> the
>>>>> machine then indicated it was "installing updates" - a process that
>>>>> took
>>>>> a
>>>>> few minutes. Then the machine shut down completely.
>>>>>
>>>>> After restarting the machine it froze completely during user sign on,
>>>>> after
>>>>> reboot. Even the system tray clock froze - for 15 minutes, until I did
>>>>> a
>>>>> hard - count to 5 seconds - shutdown.
>>>>>
>>>>> The next startup sequence seemed normal - however I have had two
>>>>> periods
>>>>> of
>>>>> temoprary virtual stops - mouse responsive, clock normal, nothing else
>>>>> moving - which lasted more than 5 minutes. (Task manager would not
>>>>> load
>>>>> during these periods, so I cannot report on system resource
>>>>> utilization.)
>>>>>
>>>>> I regard this as a low priority "issue" but would like to know if
>>>>> other
>>>>> users have experienced similar system responses? Can anyone tell me
>>>>> what
>>>>> causes the need for a complete shutdown, and install of updates during
>>>>> this
>>>>> shutdown process?
>>>>>
>>>>> Is this behavior by Windows after an MS update expected and "normal"?
>>>>> I've
>>>>> never seen it before.