Thank you all! A lot of reading and waiting pointed me to a(?) fix.
My two XP machines are now repaired and up to date.
Odd fix, but, who cares now about XP............... :)
Again, thanks all!
Duncan
On 05/16/2012 13:12, DSinc wrote:
Greg,
Normally, I know how to figure out the how/why a given WinUpdate fails.
This one is frustrating because 'it' chose to fail on 2 of my six XP
clients.
One is an Intel C2D; the other is an AMD Barton 2500+. Odd because my
other two Intel C2D's accepted and installed this 488KB file. As did
my 2K3
Server; and, my pre-historic Intel Pentium Pro 200.
The C2D client is my 'TEST' PC where I try stuff out before migrating
to the
family. OK. This client could be somewhat dorked up; though it shows no
visible signs of distress; except that it often fails to
close/disconnect from other
clients in Net Neighborhood. Yes, another long term research project.
The AMD Barton 2500+ client is a completely plain vanilla XPpro
install. It gets
powered on once a month just to do WinUpdates. It did serve as my LAN
file
storage, but, now that I use a NAS for this, this old client is living
toward full
retirement. Besides, its' ASUS A7N8X-E Delux m/b now fails to keep time
correctly. I've read that this is a known failure for this m/b. LOL!
I got steered to MS Security Bulletin MS12-034 - Critical.
Interestingly, all the
other KBs I should (also) have were installed and opsnorml at this
time. And, as
I read the WinUpdate.log file, I see that every morning at 0300 this
missing KB
tries to re-install to failure. Strange? I am putting this into my MS
Patience file.
Today when I checked the MS KB files I find that I am no longer alone!
Many XP
users are having the same trouble with KB2686509. I believe this
glitch will be
solved in due time. Apologies to the Digest Folks!
Thank you Collective,
Duncan
On 05/15/2012 19:16, DSinc wrote:
Thanks Greg,
I'll go look/see.
Yes, I got the zip file!
Amazing how ornery this update is for us [file in the brackets].
LMAO! I know. I so know!
Duncan
On 05/15/2012 18:41, Greg Sevart wrote:
b2686509-repeatedly-fails-with-error-code/0deeacb6-115c-419d-ac37-03ff8927b7
9c
