I think it's safe to say there IS is a problem with Auto Updates installing
KB913446 which was just released as part of the Critical updates today.
After reading literally hundreds of posts on this issue and speaking directly
with MS it's a safe assumption there is a problem. Yes, I also know it's
possible to download the KB directly from MS and install the patch manually.
Sorta defeats the purpose of auto updates but that is neither here nor there.
What I DO NOT understand is why MS has not publised anything "official" on
their site (or have they)? I also DO NOT understand why have they not pulled
the update until such time they have the problem identified with KB913446
working from within Auto updates? I am guessing this would solve the obvious
frustrations many of have mentioned in this forum.
Has anyone heard any updates as to when they expect the issue to be corrected?
As Dean said earlier in this thread. How did this ever make it to Windows
Updates or better yet why has it NOT!! been pulled? Knowing there are issues.
"MAP" wrote:
> Dean wrote:
> > I have tried 6 times and fails with error code 0x80242006. If this
> > security update is failing for so many users, how did this ever make
> > it to the Windows Update site to begin with?
>
> The XP Newsletter From www.updatexp.com - by Marc Liron MVP
>
> Microsoft have released some new security patches today.
> HOWEVER, one of them seems to be causing users headaches :-(
>
> It seems that many PC's that update via the Windows Automatic
> Update service are failing to install security patch:
>
> KB913446 - Vulnerability in TCP/IP Could Allow Denial of Service
>
> If this is the case for you or a relative/friend etc... You may
> want to read this new page I have just posted.
>
> At the end of the article it lists the individual security patch
> you can download and install manually - this seems to work!
>
> It also means you will be protected from this newly discovered
> security threat :-)
>
> Read the article online here:
>
> http://www.updatexp.com/kb913446.html
>
> --
> Mike Pawlak
>
>
>