5 day lag autoupdate

at ms website, i noticed the november ms06-### are dated november 14.
only today (nov 20) did systray update icon appear. (winxp xp2 home)

i've noticed days of lag at previous updates.

most of the time, this computer is left connected & unused for partial days. Is there a way for the "are you busy?" check
to occur a little more often?




actually the computer is doing an "am *i* busy?" check :-)

though there are advantages to waiting.
http://www.microsoft.com/technet/sec.../MS06-071.mspx

[scroll down]

Revisions:
•V1.0 (November 14, 2006): Bulletin published.

•V1.1 (November 15, 2006): Bulletin updated: executable name for msxml6 has been updated with correct name and log file
has been updated with correct KB number. Additional clarification has also been added to clarify which components of
the previous Bulletin this update replaces.

Absent any errors from your Windowsupdate.log, I'll suggest that, like many
around the world, you are seeing a delay caused by excessive demand on the
servers. It can take up to 7 days for the hundreds of millions of Automatic
Update users to get new updates.

You can try downloading/installing 'em via Windows/Microsoft Update page
(and for best results, try it during off-peak hours, e.g., 11:00 PM-7:00AM
PDT). Understand that by doing so, you're pushing all the 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).
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)


MsOsWin.8lCK9hAAAADE7lhLsRStjiFks8uO...valid.n omail wrote:
> at ms website, i noticed the november ms06-### are dated november 14.
> only today (nov 20) did systray update icon appear. (winxp xp2 home)
>
> i've noticed days of lag at previous updates.
>
> most of the time, this computer is left connected & unused for partial
> days. Is there a way for the "are you busy?" check to occur a little more
> often?
>
> actually the computer is doing an "am *i* busy?" check :-)

"MsOsWin.8lCK9hAAAADE7lhLsRStjiFks8uO85PU@invalid. nomail"
<MsOsWin.8lCK9hAAAADE7lhLsRStjiFks8uO85PU@invalid. nomail> in
news:Xns9881A9921CC91Na5m@207.46.248.16:

> though there are advantages to waiting.

or??


an older update that's been updated????

http://www.microsoft.com/technet/sec.../MS06-061.mspx
Vulnerabilities in Microsoft XML Core Services Could Allow Remote Code Execution (924191)
Updated: November 8, 2006
Version: 2.1
November 8, 2006


notice [snips]
•Microsoft XML Parser 2.6 (all versions) and Microsoft XML Core Services 3.0 (all versions) on Microsoft Windows XP
Service Pack 1 - Download the update (KB924191)

•Microsoft XML Parser 2.6 (all versions) and Microsoft XML Core Services 3.0 (all versions) on Microsoft Windows XP
Service Pack 2 – Download the update (KB924191)


---------

meanwhile, one of november's (this month's) "completely new" updates deal with xml 4, xml6 (ms06-071)
maybe they replace the same files that this updated older update (ms06-061 v 2.1) replaces? if so, then ms06-061 v 2.1 is
made redundant *if* do november's "completely new" update?

"PA Bear" <> in
news::

> Absent any errors from your Windowsupdate.log,

hmm, at least one line looks undesirable.
"FATAL ... "
But the item may have succeeded in a subsequent line.
I may need to find a Windowsupdate.log translation guide.


>I'll suggest that,
> like many around the world, you are seeing a delay caused by
> excessive demand on the servers. It can take up to 7 days for the
> hundreds of millions of Automatic Update users to get new updates.
>
> You can try downloading/installing 'em via Windows/Microsoft
> Update page (and for best results, try it during off-peak hours,
> e.g., 11:00 PM-7:00AM PDT). Understand that by doing so, you're
> pushing all

(except me)

>the Automatic Updates users further back

(by one)

>in the queue
> (which may explain, at least in part, why Automatic Updates hasn't
> brought them in for you yet).

i hate crowds :-)

i suppose update scheduling could return to "release when fixed" mode, instead of all at mid month? ("release when
fixed" adds complication?)
or continue with midmonth releases, but prioritize downloading of the "critical" updates (though "criticality" is possibly
dependent upon each users' usage.)