!!Fix!! Blue Screen after W2K Update Rollup

for this problem someone in this NG knew the solution. It worked for some
other guy as well.


problem:
--------
I just attempted to update a Windows 2000 Server SP4 through Windows Update
including the Update Rollup. After reboot it shows a Blue Screen.

Stop: 0x0000001E (0x0000005,0x804A6467,0x00000000,0x00000000)
KMode_Exception_not_handled
Adress 804A6467 base at 80400000, DateStamp 427b58bb - ntoskrnl.exe


All F8 options don't work. There have never been any problems with the
server which is a file and DHCP Server in an W2K domain.

Does anybody know a solution? Should I run a repair installation from CD? Is
there a known problem with the update rollup?
---------


solution:
---------
Try uninstalling the Rollup Pack

reboot in recovery console
cd to your windows directory
cd $NtUpdateRollupPackUninstall$
cd spuninst
do a dir and make sure there is spuninst.txt file in there
use the command "batch spuninst.txt"
exit the recovery console

----------

thanks again, Fritz,

Axel

Thanks Axel, uninstalling the Rollup Pack is perfect solution:

The problem is KB891861

If you have win2K Server with automatical updates or SUS server, check the
updates apliyed/approval, and the history of recent updates installed in your
Win2K server machine or machines, uninstall KB891861 before restart by any
cause, if is too late for this, uninstall the rollup Pack from recovery
console as Axel instructions .

"Axel Voigt" wrote:

> for this problem someone in this NG knew the solution. It worked for some
> other guy as well.
>
>
> problem:
> --------
> I just attempted to update a Windows 2000 Server SP4 through Windows Update
> including the Update Rollup. After reboot it shows a Blue Screen.
>
> Stop: 0x0000001E (0x0000005,0x804A6467,0x00000000,0x00000000)
> KMode_Exception_not_handled
> Adress 804A6467 base at 80400000, DateStamp 427b58bb - ntoskrnl.exe
>
>
> All F8 options don't work. There have never been any problems with the
> server which is a file and DHCP Server in an W2K domain.
>
> Does anybody know a solution? Should I run a repair installation from CD? Is
> there a known problem with the update rollup?
> ---------
>
>
> solution:
> ---------
> Try uninstalling the Rollup Pack
>
> reboot in recovery console
> cd to your windows directory
> cd $NtUpdateRollupPackUninstall$
> cd spuninst
> do a dir and make sure there is spuninst.txt file in there
> use the command "batch spuninst.txt"
> exit the recovery console
>
> ----------
>
> thanks again, Fritz,
>
> Axel

Worked for me too. So why is the only solution to this messed up MSFT
pacth in Google and not on MSDN?

All,

The fix described in this Email thread worked for me as well. But, there may
be a slightly easier and/or more preferable way. See Article ID 891861
"Update Rollup 1 for Windows 2000 SP4" dated today 7/30/2005 (revison 8.0).
Apparently it may be sufficient to replace just Scsiport.sys from the
uninstall backup directory rather than running the 'spuninst.txt' batch file
as this Email thread recommends. This may apply only to folks with "an older
non-Plug-and-Play ISA, EISA, or Micro Channel Architecture (MCA) SCSI
controller" as per the article. I haven't actually tried it, as I saw this
new posting of KB891861 just after I backed out the whole SVP4 rollup 1 per
instructions later in this Email thread.

One other thought. I'm an IT guy, not a Windows sys admin. But, after I got
my machine back and fully booted up (after running the batch file
'spuninst.txt' per this Email thread), I went to "Add/Remove" programs to
uninstall the Update Rollup 1 for Windows 2000 SP4. This performs a bunch of
file copies (presumably same as 'spuninst.txt'- perhaps actually using the
same script), but also synchronizes the registry and does some cleanup. This
may be a useful/important step after performing the manual rollback using
'spuninst.txt'? Those of you who know are encouraged to advise.

Thanks to all of you who posted and helped guys like me save our machines.

One other contribution: In this thread Fritz posted that he might try
applying the MS05-18 Hotfix (which is part of the rollup in question). While
my machine was KO'd by the full rollup, it seems to tolerate the KB890859
hotfix (MS05-18: Vulnerabilities in Windows kernel could allow elevation of
privilege and denial of Service).

Don

"Axel Voigt" wrote:

> for this problem someone in this NG knew the solution. It worked for some
> other guy as well.
>
>
> problem:
> --------
> I just attempted to update a Windows 2000 Server SP4 through Windows Update
> including the Update Rollup. After reboot it shows a Blue Screen.
>
> Stop: 0x0000001E (0x0000005,0x804A6467,0x00000000,0x00000000)
> KMode_Exception_not_handled
> Adress 804A6467 base at 80400000, DateStamp 427b58bb - ntoskrnl.exe
>
>
> All F8 options don't work. There have never been any problems with the
> server which is a file and DHCP Server in an W2K domain.
>
> Does anybody know a solution? Should I run a repair installation from CD? Is
> there a known problem with the update rollup?
> ---------
>
>
> solution:
> ---------
> Try uninstalling the Rollup Pack
>
> reboot in recovery console
> cd to your windows directory
> cd $NtUpdateRollupPackUninstall$
> cd spuninst
> do a dir and make sure there is spuninst.txt file in there
> use the command "batch spuninst.txt"
> exit the recovery console
>
> ----------
>
> thanks again, Fritz,
>
> Axel

I had the same problem Stop: 0x0000001E
(0x0000005,0x804A6467,0x000000*00,0x00000000)
KMode_Exception_not_handled
Adress 804A6467 base at 80400000, DateStamp 427b58bb - ntoskrnl.exe
but it on a brand new install Asus A8N-SLI, Athlon 64 3700 and SATA
raid WD Raptors mirrored. Had to start over and leave off the Rollup