Cannot boot Windows server 2003


Recommended Posts

I use to have XP SP1 on my old machine, I thought id put Windows Server 2003 onto it and link it up to my new computer. I wiped the hard drive using Drive Scrubber. Then I inserted the Windows server 2003 SP1 disk into the drive and select boot from CD-ROM in the bios settings. It begins pre-installation and for some weird reason XP SP2 Boot screen appears, after that it goes into the Windows Server set up, command prompt opens and "Factory-PE.exe" runs. Then command prompt remains open and nothing happens. Please not this is a OEM CD :(

Link to comment
https://www.neowin.net/forum/topic/451954-cannot-boot-windows-server-2003/
Share on other sites

  bobbba said:

Why not just go back to XP?

I dont have clue how to reformat the drive. When it stays on Command Prompt it says:

"X:\I386\system32>factory -winpe"

"X:\I386\system32>"

The reason I wanted Windows Server onto it was just to mess around since I am hoping to get a job in IT later in life. :o

Get through to the partitioning stage of Win 2003 setup cd-rom. Select the partition you want to install to and press d. Follow the instructions until you have got rid of the partition and got "Unallocated Space". Select the large amount of allocated space and press enter, then choose NTFS Quick. hopefully it will then work

  simsie said:

Get through to the partitioning stage of Win 2003 setup cd-rom. Select the partition you want to install to and press d. Follow the instructions until you have got rid of the partition and got "Unallocated Space". Select the large amount of allocated space and press enter, then choose NTFS Quick. hopefully it will then work

The installation doesnt get that far. Here is the order and what happens:

1. Bios boots

2. Press any key to boot from CD-ROM

3. Pre-installation of Windows environment

4. XP Boot screen

5. Command prompt opens

6. "X:\I386\system32>factory -winpe" automatically runs

6. Factory -winpe finishes and command prompt remains open

7. "X:\I386\system32>" stays on the command prompt

That is all what happens.

where did you get this CD? Is it some kind of trial CD? Are you sure there is not another CD in your machine in another CD/DVD drive?

I can tell you this - No 2k3 server CD from MS boots with "Factory -winpe" anything..

Either your not booting what you think your booting.. ie some other CD or some kind of recovery partition on the hard drive.. Or that is not a CD from MS.

  Viper101 said:

The installation doesnt get that far. Here is the order and what happens:

1. Bios boots

2. Press any key to boot from CD-ROM

3. Pre-installation of Windows environment

4. XP Boot screen

5. Command prompt opens

6. "X:\I386\system32>factory -winpe" automatically runs

6. Factory -winpe finishes and command prompt remains open

7. "X:\I386\system32>" stays on the command prompt

That is all what happens.

it sounds like you have an OEM version of Windows 2003.

OEM companies add stuff to the Windows CDs to better fit their needs and their customers needs.

sounds like this OEM CD that you have is using other parameters and scripts that the OEM company has put in place. These scripts and parameters are designed for specific hardware. If you are not using the original OEM computer/server with this OEM CD, then it will most likely fail.

At my organization, I have created an "OEM" windows xp dvd that is designed to work only with our hardware.

OEM Companies (like Dell, IBM, etc), use their own OEM CDs (even for Windows 2003 server) that work with certain hardware configurations. The CDs look official but are designed only for their computer systems.

hope this isnt too confusing.

  metalguy90 said:

it sounds like you have an OEM version of Windows 2003.

OEM companies add stuff to the Windows CDs to better fit their needs and their customers needs.

sounds like this OEM CD that you have is using other parameters and scripts that the OEM company has put in place. These scripts and parameters are designed for specific hardware. If you are not using the original OEM computer/server with this OEM CD, then it will most likely fail.

At my organization, I have created an "OEM" windows xp dvd that is designed to work only with our hardware.

OEM Companies (like Dell, IBM, etc), use their own OEM CDs (even for Windows 2003 server) that work with certain hardware configurations. The CDs look official but are designed only for their computer systems.

hope this isnt too confusing.

Thanks for making it a lot clearer. It is a OEM disk. Came in a seal Microsoft box with security seals.

It worked fine on VMWare. Ive digged out an old 98 recovery disk and restored the Boot record and partition table. Im going try to format the hard drive and see if that makes any different.

Cheers

  Viper101 said:

Thanks for making it a lot clearer. It is a OEM disk. Came in a seal Microsoft box with security seals.

that sounds odd?

most OEMs CDs dont have much Microsoft branding on it, but their own.

ie. Dell would make the OEM CD look like a Dell CD.

the last company i worked for bought Dell servers and all their disks were blue & white.

the company i work for now uses IBM servers, and their disks are white & black; even though both OEM CDs are Microsoft Windows 2003 server, they both looked like IBM or Dell CDs

hmmm reading your post after mine reminded me of a problem i once had installing server 2003 on a client machine. If the 2003 is booting ok but its not loading the files or appears to be stuck it indicates a hardware problem. In my case i solved it by replacing the cd drive and the PATA cable but it also could be due to faulty ram. Download microsoft memory tester from another pc and save it to floppy and run the floppy disk. If the ram is fine then more than likely its the cd drive or the hard drive. You just have to elimante each component until you find the problem. :) also as mentioned already it could be because its an oem cd. Try downloading the 120 day trial from Microsoft and burn it to a cd and see if that installs.

  andy2004 said:

hmmm reading your post after mine reminded me of a problem i once had installing server 2003 on a client machine. If the 2003 is booting ok but its not loading the files or appears to be stuck it indicates a hardware problem. In my case i solved it by replacing the cd drive and the PATA cable but it also could be due to faulty ram. Download microsoft memory tester from another pc and save it to floppy and run the floppy disk. If the ram is fine then more than likely its the cd drive or the hard drive. You just have to elimante each component until you find the problem. :) also as mentioned already it could be because its an oem cd. Try downloading the 120 day trial from Microsoft and burn it to a cd and see if that installs.

I downloaded the trial version of Windows Server 2003. I burned it onto a CD-ROM, inserted it into the CD-ROM drive and error messege occured "Invalid System Disk". I dont think that RAM is damaged as XP was working fine before. The only thing I can think of is the Hard drive. I think im going buy a 80GB hard drive, to see if that will work. Il let you know how it goes.

Cheers

  Viper101 said:

I brought a new 80GB Hard drive, fitted it and tried installing Server 2003, however still no luck. This is just one big headache! :blink:

Yeah cuz installing a OS is just so hard.. How does a CD not booting point you to a hard drive issue? The CDrom could boot without a Hard Drive in the system..

When you say you burned the trial download to a CD? I'm guessing you have a CD with trial2003.iso on it - and can not figure out why id doesn't boot ;)

If you can not figure out how to burn a ISO.. have them send you a trial..

  • 2 weeks later...

:cool:

He's not using a real Microsoft WIN 2003 disk. I've installed many OS's and W2K3 never acts like that...

I've heard of some of these "so-called good deal" disks and most simply do not work...

Recommend he get his money back...if he can!

Ozz~ :alien:

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Mozilla shuts down even more Firefox services you might still be using by David Uzondu A few weeks ago, Mozilla announced that its Pocket and Fakespot services were getting the axe as the company focuses more on Firefox. It is a complete shutdown. Pocket, the read-it-later service Mozilla bought in 2017, will stop working on July 8, 2025. You have until October 8 to get your saved articles out before they are deleted forever. Fakespot, which helped you spot garbage product reviews, is also being sunsetted. But the house cleaning does not stop with those two. Neowin has spotted a shutdown notice dated June 26, 2025 for Deep Fake Detector, the Firefox extension that was supposed to tell you if a piece of text was written by a human or an AI chatbot. That tool used a combination of Mozilla's own proprietary ApolloDFT engine and open-source models like ZipPy to give you a verdict on what you were reading. The notice says: This brings us to the AI tools. Following the pattern, the Orbit website was updated with a banner that announced the service would shut down by June 26. Orbit was Mozilla's big privacy-first experiment in AI. It was a Firefox add-on that could summarize articles and answer questions about a webpage's content without sending your data to a third party. This is not an AI exit. Mozilla is simply changing how it delivers AI features. Orbit's private, self-contained setup can be replaced with the new sidebar built directly into Firefox, letting you connect to third-party chatbots like ChatGPT and Gemini. But, for Orbit users, this is still a huge loss, as a key feature of the service was privacy. Your prompts were handled by Mistral LLM (Mistral 7B) within Mozilla's GCP instance and were not shared with other companies for model training, which was a huge selling point for people tired of being the product. Mozilla keeps saying these cuts are necessary. As the only major browser not owned by a tech giant, its resources are limited; hence, the need to focus its cash and engineering talent on the core Firefox browser to compete.
    • Too close to the Ultra, I have and love an Ultra but have held onto my watch 6 classic because it is nicer when wearing a suit to work.
    • Intel v32.0.101.6881 graphics driver fixes a popular multiplayer hero shooter by Taras Buria Intel is rolling out a new graphics driver under version 32.0.101.6881. This WHQL release does not contain much. In fact, there is only a single fix for a popular multiplayer hero shooter. The new driver fixes crashes when launching Overwatch 2 (DirectX 12) on High or Ultra graphics settings on Intel Arc A-Series graphics cards. From the changelog: Overwatch 2 (DX12) may experience an application crash while launching the game with High or Ultra graphics quality settings. Known bugs in the drive include the following: Intel Arc B-Series Graphics Products: Fortnite may experience an application crash when “Performance - Lower Graphical Fidelity” is selected as Rendering Mode. Recommendation is to use default Rendering Mode – DX12. Visual corruptions may appear in certain scenarios with multiple application interactions. Call of Duty: Black Ops 6 (DX12) may exhibit flickering corruption in certain scenes during gameplay. Returnal (DX12) may experience an application crash during gameplay with Ray-Tracing settings turned on. Call of Duty: Warzone 2.0 (DX12) may exhibit corruptions on water areas in certain scenarios. SPECapc for Maya 2024 may experience intermittent application freeze during benchmark. PugetBench for Davinci Resolve Studio V19 may experience an application crash while running the benchmark. HWiNFO may incorrectly report number of Xe Cores for certain Intel Arc B-Series Graphics Products. Intel Arc A-Series Graphics Products: Returnal (DX12) may experience an application crash during gameplay with Ray-Tracing settings turned on. Marvel’s Spider-Man 2 (DX12) may experience an application crash with Ray-Tracing and XeSS enabled. PugetBench for Davinci Resolve Studio V19 may experience an application crash while running the benchmark. Intel Core Ultra Series 1 with built-in Intel Arc GPUs: Adobe Premiere Pro may fail to import video. Mitigation is to use Intel NPU Driver version 32.0.100.3717 or lower. PugetBench for Davinci Resolve Studio V19 may experience errors intermittently with benchmark preset set to Extended. Intel Core Ultra Series 2 with built-in Intel Arc GPUs: Valorant (DX11) may fail to enumerate supported resolutions in game settings. Adobe Premiere Pro may experience an intermittent application crash. Adobe Premiere Pro may fail to import video. Mitigation is to use Intel® NPU Driver version 32.0.100.3717 or lower. PugetBench for Davinci Resolve Studio V19 may experience errors intermittently with benchmark preset set to Extended. You can install Intel 32.0.101.6881 WHQL driver on PCs with 64-bit Windows 10 and Windows 11 with the following graphics products from Intel: Discrete GPUs Integrated GPUs Intel Arc A-Series (Alchemist) Intel Arc B-Series (Battlemage) Intel Iris Xe Discrete Graphics (DG1) Intel Core Ultra Series 2 (Lunar Lake and Arrow Lake) Intel Core Ultra (Meteor Lake) Intel Core 14th Gen (Raptor Lake Refresh) Intel Core 13th Gen (Raptor Lake) Intel Core 12th Gen (Alder Lake) Intel Core 11th Gen (Tiger Lake) You can download the driver from the official website here. Full release notes are available here (PDF).
    • Just look at the shiney shiney Vista clone, ignore the fact that they are a disaster in anything AI related. Roll on the class actions for all iPhone 16 owners.
  • Recent Achievements

    • Collaborator
      Carltonbar earned a badge
      Collaborator
    • Explorer
      MusicLover2112 went up a rank
      Explorer
    • Dedicated
      MadMung0 earned a badge
      Dedicated
    • Rookie
      CHUNWEI went up a rank
      Rookie
    • Enthusiast
      the420kid went up a rank
      Enthusiast
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      ATLien_0
      268
    3. 3
      +FloatingFatMan
      248
    4. 4
      +Edouard
      201
    5. 5
      snowy owl
      168
  • Tell a friend

    Love Neowin? Tell a friend!