Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to upgrade a Windows 2000 Server machine to Windows 2003 Server. When I run the installer, it gets near the end of the "copying files" stage, and then complains that a file "agjh1tpp.sys" is missing.

There are no google hits whatsoever for that file name, so I have no idea what it is.

I have the option to skip this file and continue, but if I do so, then shortly after that it reboots the machine, and immediately complains about this file being missing. (Luckily I can still boot into Windows 2000 at this stage).

I've used several different ISO images from MSDN (Standard, Professional, R2, etc.), and also a Windows 2003 Server installation CD, and the same problem occurs each time.


share|improve this question
up vote 2 down vote accepted

.sys are device drivers usually. Check and see if there's some third-party drivers you need for the installer to finish (maybe RAID or SCSI cards?)

It does sound like some hardware is holding up the upgrade. Take a look at DevCon to see if you can either find the right drivers or disable the hardware.

share|improve this answer
I'm not sure I understand. If I have a disk drive of some sort that needs a device driver, then wouldn't it already be on the machine? Why would it suddenly complain about it being missing because I'm upgrading the OS? – Gary McGill Jan 11 '12 at 12:55
If it were a driver for some disk drive that I'm no longer using, is there some way I could persuade the installer that it's not required? It simply refuses to go on without this file... – Gary McGill Jan 11 '12 at 12:56
Hmmm... I went to the Device Manager, and there are two PCI devices that have no driver (they show up as a yellow triangle/question mark). I tried "un-installing" these two, but after a reboot, the "found new hardware" wizard comes up and tries (and fails) to find a driver. They get put back in the list, in the same state as before. So I'm inclined to think you're onto something. Trouble is, how I can I get rid of them? – Gary McGill Jan 11 '12 at 13:39
So, I remembered some of the history of this PC, and that it was bought as a Windows XP box which I flattened when I installed Windows Server 2000. Thus some of the drivers that came with it will have been lost in the process. Luckily it's a Dell, so I was able to use the service tag to go download all the original drivers. Having installed all but one, I've now only got one "problem" PCI device, and the Windows 2003 Server setup now complains about a different file - which makes me thing the first file it complained about is now present. Partial success! However... – Gary McGill Jan 12 '12 at 11:31
... I was unable to install one of the drivers (which I think is for the media card reader) because the installer says it's Windows XP only. This leaves me with no way to get that remaining driver in place. I did try disconnecting the cable to the card reader, but that didn't seem to help (I had hoped it would forget it ever existed). – Gary McGill Jan 12 '12 at 11:34

I've seen this type of error many times (with client OS installs), and it usually means you have a faulty memory module.

Do you have any diagnostic software bundled with the server that you can run?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.