Server 2003 SP1 Install (File is corrupt)?

[mplutodh1]

I have attempted to install SP1 on my Windows 2003 Server box about a half dozen times now. A few times using Windows Update, downloaded the .exe file, downloaded the .exe on a seperate PC and burned to CD and still the same problem. The files are corrupt.

Any ideas? Anyone had this problem? I'd like to be able to install SP1 but it doesn't look like it will happen at this rate.

I don't get much support for this copy either as it is through our CS department at school and not a paid version of the OS. Thanks!

 

[Thor86]

Nope, downloaded from MS directly and no problems installing either. So far so good.

 

[mplutodh1]

eh.. maybe ill do a fresh install of server.. haven't really changed much that id have to reset anyways, just not really what I wanted to do!

 

[Yellow Dog]

Nope, Installed SP1 on 2K3 Server without issue

 

[SilentZero]

Nope..worked fine for me

 

[jfreeth]

Yup, same problem.
The common thread appears to be the Athlon 64 processor, mine is 3000+
Failed on first attempt, working server, domain controller, Oracle server etc..., all my stuff installed. It attempted to roll back, and failed. Wouldn't reboot, couldn't find ...
Tried again... same failure.
Installed from scratch new copy of w2003, with nothing extra. Then without adding anything tried to apply SP1, fails at installing XPSP2RES.DLL, says can't copy sprb0c0a.dl_
I would like to roll it back to pre SP1 on original install so I can get back all my stuff but not having much success. Any suggestions that are printable?
On trolling tech reports found reference to problems with XPSP2RES and XP on Athlon, could this be the common thread 64.:|

 

[jfreeth]

On further analysis I seem to have two problems with 2003 sp1, both probably related to hardware. The original attempt at applying the service patch to an active environment(backup domain controller, oracle server, visual studio .net, all my development and test stuff) failed, rolled back and now fails on reboot due to a "non-dll file included in knowndll list". I have a backup of the registry files from several months ago which I tried to reboot from, after installing a plain vanilla copy of 2003 enabling me to play with the ntfs volume, but still have the same problem. I surmise that the sp1 even though it didn't complete the install has tightened up the rules for the knowndlls in the registry.
My current problem is that I do not yet know how to edit the registry of an install that won't boot. I have a parallel install of w2003 on the same box, so I can access the files, but how do I edit them? Catch 22, can't edit without loading, can't load without OS failing.

The second problem is with the plain vanilla 2003 install, that does not accept the patch, fails with can't find/copy file as described above. And when reboots forces chkdsk, sounds like a disk driver problem with this particular hardware setup. Abit KV8-Max3 with sata drives etc..

Server Spec