Reboot problem with updates - solution

I have had to reinstall 12 computers so far. Here's the deal...
Microsoft put out 2 bad updates, (KB890859) & (KB893066)

This is a known problem. Bad updates from Microsoft. You will have to
reinstall XP by booting from cd. Go thru the motions of installing for the
first time, you'll get to a screen (after pressing F8) that asks to hit
"enter" to install or "R" to repair, choose repair, it will go automatically
with very little user interaction. After the reinstall your system should be
right back to normal. First thing, change Auto Updates in Control Panel to
just download, not auto install. Next goto Windows update site and do a
custom install so that it shows you the updates. Uncheck (KB890859) and
(KB893066) and choose to hide these updates, install the updates and that's
it.

Note: (KB890859) causes the reboot problem & (KB893066) causes the internet
to quit, unable to obtain an ip address. (KB893066 only happened to half the
computers I reinstalled, you can install it and if the internet stops working
go to "Add/Remove Programs", click @ top to show updates and uninstall it. On
some computers after reinstall I could not goto Windows Update, gave me error

Rico did you apply those updates on XP sp2? I have a test XP station without
sp2 and I am having no problems with it after I installed those updates.


"rico" wrote:

> I have had to reinstall 12 computers so far. Here's the deal...
> Microsoft put out 2 bad updates, (KB890859) & (KB893066)
>
> This is a known problem. Bad updates from Microsoft. You will have to
> reinstall XP by booting from cd. Go thru the motions of installing for the
> first time, you'll get to a screen (after pressing F8) that asks to hit
> "enter" to install or "R" to repair, choose repair, it will go automatically
> with very little user interaction. After the reinstall your system should be
> right back to normal. First thing, change Auto Updates in Control Panel to
> just download, not auto install. Next goto Windows update site and do a
> custom install so that it shows you the updates. Uncheck (KB890859) and
> (KB893066) and choose to hide these updates, install the updates and that's
> it.
>
> Note: (KB890859) causes the reboot problem & (KB893066) causes the internet
> to quit, unable to obtain an ip address. (KB893066 only happened to half the
> computers I reinstalled, you can install it and if the internet stops working
> go to "Add/Remove Programs", click @ top to show updates and uninstall it. On
> some computers after reinstall I could not goto Windows Update, gave me error

I ran into the same problems. This was with SP2 installed. I have left
these two updates off my system and it is now running fine, again.

"Mike O." wrote:

> Rico did you apply those updates on XP sp2? I have a test XP station without
> sp2 and I am having no problems with it after I installed those updates.
>
>
> "rico" wrote:
>
> > I have had to reinstall 12 computers so far. Here's the deal...
> > Microsoft put out 2 bad updates, (KB890859) & (KB893066)
> >
> > This is a known problem. Bad updates from Microsoft. You will have to
> > reinstall XP by booting from cd. Go thru the motions of installing for the
> > first time, you'll get to a screen (after pressing F8) that asks to hit
> > "enter" to install or "R" to repair, choose repair, it will go automatically
> > with very little user interaction. After the reinstall your system should be
> > right back to normal. First thing, change Auto Updates in Control Panel to
> > just download, not auto install. Next goto Windows update site and do a
> > custom install so that it shows you the updates. Uncheck (KB890859) and
> > (KB893066) and choose to hide these updates, install the updates and that's
> > it.
> >
> > Note: (KB890859) causes the reboot problem & (KB893066) causes the internet
> > to quit, unable to obtain an ip address. (KB893066 only happened to half the
> > computers I reinstalled, you can install it and if the internet stops working
> > go to "Add/Remove Programs", click @ top to show updates and uninstall it. On
> > some computers after reinstall I could not goto Windows Update, gave me error

Oddly enough it's only happening to about 25% of my systems out there, it
didn't affect mine but it did affect my kids and can't figure out why, and
yes it was SP2, not sure if it affects SP1.

"Mike O." wrote:

> Rico did you apply those updates on XP sp2? I have a test XP station without
> sp2 and I am having no problems with it after I installed those updates.
>
>
> "rico" wrote:
>
> > I have had to reinstall 12 computers so far. Here's the deal...
> > Microsoft put out 2 bad updates, (KB890859) & (KB893066)
> >
> > This is a known problem. Bad updates from Microsoft. You will have to
> > reinstall XP by booting from cd. Go thru the motions of installing for the
> > first time, you'll get to a screen (after pressing F8) that asks to hit
> > "enter" to install or "R" to repair, choose repair, it will go automatically
> > with very little user interaction. After the reinstall your system should be
> > right back to normal. First thing, change Auto Updates in Control Panel to
> > just download, not auto install. Next goto Windows update site and do a
> > custom install so that it shows you the updates. Uncheck (KB890859) and
> > (KB893066) and choose to hide these updates, install the updates and that's
> > it.
> >
> > Note: (KB890859) causes the reboot problem & (KB893066) causes the internet
> > to quit, unable to obtain an ip address. (KB893066 only happened to half the
> > computers I reinstalled, you can install it and if the internet stops working
> > go to "Add/Remove Programs", click @ top to show updates and uninstall it. On
> > some computers after reinstall I could not goto Windows Update, gave me error

I have sp1 installed and it didn't affect it negatively.

"rico" wrote:

> Oddly enough it's only happening to about 25% of my systems out there, it
> didn't affect mine but it did affect my kids and can't figure out why, and
> yes it was SP2, not sure if it affects SP1.
>
> "Mike O." wrote:
>
> > Rico did you apply those updates on XP sp2? I have a test XP station without
> > sp2 and I am having no problems with it after I installed those updates.
> >
> >
> > "rico" wrote:
> >
> > > I have had to reinstall 12 computers so far. Here's the deal...
> > > Microsoft put out 2 bad updates, (KB890859) & (KB893066)
> > >
> > > This is a known problem. Bad updates from Microsoft. You will have to
> > > reinstall XP by booting from cd. Go thru the motions of installing for the
> > > first time, you'll get to a screen (after pressing F8) that asks to hit
> > > "enter" to install or "R" to repair, choose repair, it will go automatically
> > > with very little user interaction. After the reinstall your system should be
> > > right back to normal. First thing, change Auto Updates in Control Panel to
> > > just download, not auto install. Next goto Windows update site and do a
> > > custom install so that it shows you the updates. Uncheck (KB890859) and
> > > (KB893066) and choose to hide these updates, install the updates and that's
> > > it.
> > >
> > > Note: (KB890859) causes the reboot problem & (KB893066) causes the internet
> > > to quit, unable to obtain an ip address. (KB893066 only happened to half the
> > > computers I reinstalled, you can install it and if the internet stops working
> > > go to "Add/Remove Programs", click @ top to show updates and uninstall it. On
> > > some computers after reinstall I could not goto Windows Update, gave me error

KB893066 does cause well-documented problems with FTP (see other threads),
but since few people use FTP, few people see it. I've yet to see anyone
claim to have installed it and say FTP (make sure to test uploading) works
fine.

I encountered this problem with 4 computers out of 30 all are windows
xp SP2. KB890859 and KB893066 will remain off of my systems for
now...... By the way a complete reinstall or in place upgrade is NOT
necessary

Simply reboot to recovery console via the Windows disk and run the
batch files in the c:\windows\$NtUninstallKB890859$\spuninst directory
Change the directory for KB893066 accordingly. This solved the problem
for me.....

Thanks for the info on the batch files, I wasn't aware of it, I'll definitely
try it.

"" wrote:

> I encountered this problem with 4 computers out of 30 all are windows
> xp SP2. KB890859 and KB893066 will remain off of my systems for
> now...... By the way a complete reinstall or in place upgrade is NOT
> necessary
>
> Simply reboot to recovery console via the Windows disk and run the
> batch files in the c:\windows\$NtUninstallKB890859$\spuninst directory
> Change the directory for KB893066 accordingly. This solved the problem
> for me.....
>
>

Well, I tried it too (after figuring out how to get my forgotten password
back =
I used an msdos program to reset it to something new)
But now every time I boot up from the windows-CD and get into the recovery
console, select the crippled winXP-drive, and navigate to the
uninstal-hotfix-directory, and try to run the batch (batch spuninstal.txt)
....
I get ... "Access denied"

Any clues???
They are welcome


"rico" wrote:

> Thanks for the info on the batch files, I wasn't aware of it, I'll definitely
> try it.
>
> "" wrote:
>
> > I encountered this problem with 4 computers out of 30 all are windows
> > xp SP2. KB890859 and KB893066 will remain off of my systems for
> > now...... By the way a complete reinstall or in place upgrade is NOT
> > necessary
> >
> > Simply reboot to recovery console via the Windows disk and run the
> > batch files in the c:\windows\$NtUninstallKB890859$\spuninst directory
> > Change the directory for KB893066 accordingly. This solved the problem
> > for me.....
> >
> >

Ok I think I solved it ... (well, could be I'm still wrong, but hey still
need to test it)
The problem is not that this method doesn't work, the reason is my system
(dual-boot, one crippled winXP and one functional backup win2K)

Before breakdown the winXP was located on drive C, but since it is crippled,
I started to use the win2K, witch used to be on drive E (or something).
By booting from this second OS, drives got switched ...
The crippled winXP is now on drive E, and win2K on C ...

So obviously when booting from the winXP-CD to the recovery console,
and trying to get this spuninst.txt-batch-thing to work, the paths inside
it got messed up (they all referenced to the C drive). So when the batch
want to restore the backedup-files, it goes way out of range of the
permissions
that apply to the recovery console.

Hence the solution: ... before booting from the winXP-CD, REMOVE ALL OTHER
HARDDISKS ... boot once (failliure will be yours) to get the drives correct,
boot
a second time, this time from the winXP-CD ... and get them batches to
REMOVE those windowsupdate-patches !!!!!!!!!

PS: don't mind the writing errors, I miss my spellchecker in this
posting-thing
PSS: maybe this was a bit obvious, but hey, I searched the whole damn net
to find out what was causing this "Access denied"-thing
PSSS: ... THINK before using the "SET AllowAllPaths = true"-command in the
Recovery Console ... it could have messed up both of my OS'es

Tjierio




"Byzantrope" wrote:

> Well, I tried it too (after figuring out how to get my forgotten password
> back =
> I used an msdos program to reset it to something new)
> But now every time I boot up from the windows-CD and get into the recovery
> console, select the crippled winXP-drive, and navigate to the
> uninstal-hotfix-directory, and try to run the batch (batch spuninstal.txt)
> ...
> I get ... "Access denied"
>
> Any clues???
> They are welcome
>
>
> "rico" wrote:
>
> > Thanks for the info on the batch files, I wasn't aware of it, I'll definitely
> > try it.
> >
> > "" wrote:
> >
> > > I encountered this problem with 4 computers out of 30 all are windows
> > > xp SP2. KB890859 and KB893066 will remain off of my systems for
> > > now...... By the way a complete reinstall or in place upgrade is NOT
> > > necessary
> > >
> > > Simply reboot to recovery console via the Windows disk and run the
> > > batch files in the c:\windows\$NtUninstallKB890859$\spuninst directory
> > > Change the directory for KB893066 accordingly. This solved the problem
> > > for me.....
> > >
> > >