By the way in the corporate world, it is considered a best practice to reboot
before applying a patch and then afterwards if requested. This is to assure
that the system has no booting problems and verifies that there aren't any
preexisting issues before introducing another potential factor should a post
update environment have an issue (I know it may seem a stretch but it does
happen :P).
If you want to stretch out that notification time beyond 10 minutes you can
adjust that by looking at the local Group Policy on a WinXP Pro machine (not
on Home). Look under the Machine-Administrative Templates for the Windows
Update tree and you'll see it amonst the dozen or so settings branched under
it. For me I just found forcing the restart within 5 minutes works best.
There is always one procrastinator in the crowd and that system just hangs in
this in-between kinda twighlight zone state. This is a nightmare for an
administrator to support BTW.
Regards
"Jack_II" wrote:
> Do not laugh, it is painful.
> After WU download, I ask WU to install updates. It work correctly. Fine.
> If reboot is needed, it ask me if I want to restart now Or to close.
> I choose Close.
> Then, 5 minutes later, the same question is asked to me until ... I yield.
> No respite.
>
> Why do WU impose its law ?
> May it not be so easy to simply close WU and ask it to wait for next natural
> restart ?
> It is really annoying (aggravating)
>
> The average threshold to be quiet is no more launching the updates. Too bad !
>
> My previous post about the same nuisance :
> http://www.microsoft.com/communities...a-1998692d0795
>