SP4 installation failed - server won't boot

[Foxyshadis]

(Cross-posted to adv. server, only just noticed this
group.)

I installed the mini-client version of SP4 on my
SP3+updates Win2kAS install. It downloaded fine, I decided
not to back up the old files, and it seemingly installed
fine, right up to the end. Then it gave me a few useless
error messages (see end of log; that's what told me what
happened) and ended. I rebooted, and it now restarts on he
lo-res DOS graphical loading screen, right at the very
end after the blue bar has filled. I have no idea why, and
the bootlog shows all needed
drivers loading.

It's running on a fresh install right now, and I really
don't have the time or desire to reinstall and reconfigure
almost _everything_. Last backup was too long ago and
emergency disk was corrupted.

Possibly relevant extract from SP4 install log:
(Mine doesn't have a repair folder, and hasn't for some
time. Backups are kept elsewhere; I didn't know it would
log into that folder.)

Copied file: C:\WINNTSRV\System32\DRIVERS\irenum.sys
***

Copied file (delayed): C:\WINNTSRV\System32
\DRIVERS\SET40A.tmp
***

FFileFound: FindFirstFile failed :0x2
***

IsThisAnOEMFile: FFileFound failed for
c:\winntsrv\repair\setup.log :STATUS_SETUP_LOG_NOT_FOUND
***

Copied file: C:\WINNTSRV\System32\DRIVERS\msircomm.sys
***

Copied file (delayed): C:\WINNTSRV\System32
\DRIVERS\SET40B.tmp
***

Copied file: C:\WINNTSRV\System32\DRIVERS\ndisuio.sys
***

Copied file: C:\WINNTSRV\System32\DRIVERS\usbehci.sys
***

Copied file: C:\WINNTSRV\System32\DRIVERS\usbhub20.sys
***

Copied file: C:\WINNTSRV\System32\DRIVERS\usbport.sys
***

Copied file: C:\WINNTSRV\Driver Cache\i386\sp4.CAB
***

VerifySize: Unable to verify size: Source = NULL:
C:\WINNTSRV\Driver Cache\i386\sp4.CAB

***

DoInstllation: SetupCommitFileQueue for FileQueue failed:
0x3
***

Failed Deleting C:\WINNTSRV\system32\msiinst.tmp 2
***

VerifySize: Unable to verify size: Source = NULL:
c:\winntsrv\oem0.cat

***

The system cannot find the path specified.

***

Message displayed to the user: The system cannot find the
path specified.

***

User Input: OK
***

Service Pack 4 installation did not complete.

Windows 2000 has been partially updated and may not work
properly. It is recommended that you use your Emergency
Repair disk to repair your system. To do this, insert the
Windows 2000 Setup Boot Disk into the floppy drive,
restart your computer, and then select the Emergency
Repair option.
***

Message displayed to the user: Service Pack 4 installation
did not complete.

Windows 2000 has been partially updated and may not work
properly. It is recommended that you use your Emergency
Repair disk to repair your system. To do this, insert the
Window
***

User Input: OK
***

 

[Foxyshadis]

I fixed most of it. I restored the repair folder and
reinstalled the system; now I have to reinstall a few
programs, but not as bad as it was.

While fighting with the services after reinstall (half of
them are enabled but not installed, somehow, and a few have
incorrect attributes), I discovered a way to replicate the
problem -- I changed the service group that netbt (netbios
over tcp/ip) belonged to, and from then it would reset
every time it finished the splash screen.

It's possible SP4 did something similar, only with a
service that was still started in safe mode. But I have no
idea how that could be tested. ^^;

 

[Mark Van]

I fixed most of it. I restored the repair folder and
reinstalled the system; now I have to reinstall a few
programs, but not as bad as it was.

While fighting with the services after reinstall (half of
them are enabled but not installed, somehow, and a few have
incorrect attributes), I discovered a way to replicate the
problem -- I changed the service group that netbt (netbios
over tcp/ip) belonged to, and from then it would reset
every time it finished the splash screen.

It's possible SP4 did something similar, only with a
service that was still started in safe mode. But I have no
idea how that could be tested. ^^;

I know someone who just updated to SP4 on Win2k who apparently can't
reboot now. I will have to look at it tomorrow, but I am not
optimistic

This one did not even get past the windows logo screen on the initial
restart.