You know as much as we do about this, Richard. Apparently MS decided to push 900485 to everyone. -- ~Robear Dyer (PA Bear) MS MVP-Windows (IE/OE, Shell/User, Security), Aumha.org VSOP, DTS-L.org
Not only that, it appears for some anyway this "fix" overrides your AutoUpdate settings. Did for me, twice. I did a System Restore, searched the Update Log and was horrified to see the stuff they loaded. I'm still trying to clean this out, THEN, and ONLY then, will I decide to install it.
Curmudgeon wrote: > Not only that, it appears for some anyway this "fix" overrides your > AutoUpdate settings. > Did for me, twice. > I did a System Restore, searched the Update Log and was horrified to see the > stuff they loaded. > I'm still trying to clean this out, THEN, and ONLY then, will I decide to > install it.
I had Auto Update turned off before installing and, after installing, still do. I prefer that my system does auto nothing. I like to watch.
After the autoinstallation of KB900485,my laptop(xp pro sp2) restart with stop error 1000007e and 4 parameters.I have uninstalled the update but the problem is still there. Can someone please help?
"Alias" wrote: > Curmudgeon wrote: > > Not only that, it appears for some anyway this "fix" overrides your > > AutoUpdate settings. > > Did for me, twice. > > I did a System Restore, searched the Update Log and was horrified to see the > > stuff they loaded. > > I'm still trying to clean this out, THEN, and ONLY then, will I decide to > > install it.
> I had Auto Update turned off before installing and, after installing, > still do. I prefer that my system does auto nothing. I like to watch.
> Alias
> > "Richard Schafer" wrote:
> >> I am set up to be notified of critial updates...
> >> Today I have been offered hotfix 980485...
> >> When I read the linked KB900485 article is does not appear the be a > >> scurity issue... but a stop error bug fix
> >> Most interesting is, that that artical reports: "Release Date: > >> December 20, 2005"...
> >> and and original file date of May 27, 2005...
> >> Why is this suddenly offered as a critical update NOW (April 26, > >> 2006)?