How to: Upgrade your motherboard without reinstalling Windows.

This article is written for Microsoft Windows XP, the information is still valid for Windows 2000 (all versions) but may vary slightly.

When swapping out motherboards it's common practice to reinstall the OS (windows), because of a chipset incompatibility, this is unnecessary. There is a time and place for OS reinstalls, but if your OS is running like a champ, and your just upgrading to a new mobo/cpu/ram, or just a new mobo you have other options.

There are two methods available, the first involves running a repair on the OS, the other uses a program called Sysprep. I strongly recommend the sysprep method over the repair method because it makes less changes to the OS and gets the job done. In fact, this tool is meant specifically for the job.

There are down sides to the repair method commonly used, other than the fact it takes 10x as long. Here are the potential problems to the repair method (also called an in-place upgrade).
Loss of program settings.
Data loss.
And you must reinstall ALL windows updates and service packs, since the files copied from the CD are not patched.


Sysprep
First let me describe what Sysprep is, and why it's useful to us. Sysprep is a tool used in creating HDD images for mass deployment, where the hardware can vary from machine to machine. The general idea is, you setup a PC, install all the software you want, make all the setting changes to the OS and applications. Then run Sysprep, which will remove all hardware IDs from the OS. At this point, you would want to create an image of the machine, but we are not creating images for mass deployment. I am just outlining what the tool does, we will be using it differently.

The next time the PC boots it will run a Mini-Setup Wizard and re-detect your hardware just like the first time Windows was installed. You can setup the image to have drivers ready for your different hardware, but that ins't necessary for what we are doing. We are only deploying this to a single PC, yours, and you can download the drivers by hand yourself.

Now lets go into the actual process.

1. Download drivers for your motherboard and especially your network card. When you blow away your current setup it's nice to have these ready to install. The network card is essential, you mush have this driver handy in case XP doesn't. Otherwise you will be downloading from another PC just so you can get on the internet.

2. Extract the Sysprep 2.0 files from your XP CD (\support\tools\deploy.cab) to c:\sysprep. The deploy.cab can be downloaded here.
I'm not sure if Sysprep 2.0 works on Windows 2K, I assume so (have not tested this). I know Sysprep 1.1 does work, that can be downloaded here.

3. Run Sysprep.exe

4. Select Mini-Setup, PnP, and then Reseal. Your PC should shut down when complete.

5. Install the new motherboard and or other hardware.

6. Boot the machine, it will show screens similar to when XP was first installed, this is the Mini-Setup Wizard.

7. At this point the instructions will vary depending on your hardware, you will be prompted for drivers that Windows does not already have.

8. Once you have installed the drivers you are ready to go.

EDIT: Possible issues with Sysprep.

Unsupported Scenarios

STOP 0x0000007B or INACCESSABLE_BOOT_DEVICE

EDIT2: Adding 3rd party OEM drivers.

Add OEM Drivers

EDIT3: Sysprep REQUIRES SP1, or password in recovery console will not work. generating a 'The Password Is Not Valid' error message. (thanks Poopy)

'The Password Is Not Valid' error in recovery console.

<Reserved>

TTT

Only a handfull of views, lets give it a second spin.

how is this not a sticky? I've been other other forums, and many of these had this at the top (ppl switching from nf2 to a nf3 would love to have this, or even nf2 to 875 or 925, etc. etc.)

I agree. I went from an nf2 to nf3 with a very similar method, but this one looks even easier.

Meh, I just wrote it, I don't sticky it. If anyone notices something that a bit off, or needs to be added let me know.

I'm putting in a few 'warning' links in a bit.

If they are seriously changing mobo's this is also a problem, since the hals might change. I recommend the winnt32 upgrade solution since it's easier, and less chance of the user getting screwed on a mobo upgrade. (But I would recommend using a slipstreamed CD of SP2.)

Sysprep is also a good solution, this isn't what sysprep was designed for, but it works quite well at this.

Note, Sysprep in 2K isn't as forgiving as the sysprep for XP. I would definatly use the in place upgrade for 2K.

This process is no different than creating a syspreped system for OEMs, except it's not being used on several machines, just one. The 1 image I have created at work, works on every piece of hardware in the company except really old laptops, P-IIs that we don't even use for XP (API-ACPI/HAL issue, don't beat me up if I got the acronyms wrong, it's been a long day ).

Anyways, I guess I'm saying that compatibility issues are few and far between in my experience.

Why do you say 2k is less forgiving? I haven't had anymore issues with it than XP.

I know that in 2K there were issues with sysprep switching from an AMD system to an Intel system, and that it wasn't supported. In XP it was fine, what changes were made to the kernel, boot loader, and sysprep to fix that situation I don't remember. (And this might be no longer an issue in SP4, I haven't tested 2000 since SP1 of 2k)

The reason I mention the Hal issue is it's very possible someone is upgrading from a PIII to a P4 with hyperthreading which would definatly cause the HAL issue.

I agree with your article fully, don't get me wrong, sysprep is an awesome tool for this, I use it for this myself, (Since I am a sysprep tester, it would be bad if I didn't use it myself...) But I just want people to be clear there are some caveats to this tool.

This is some cool info and I sure will use it.


However, I did a motherboard switch a while back with a KT133a going to a NF2 Ultra 400, and all I did is change the motherboard and hit the powerswitch. WinXP loaded up and detected and installed all the drivers that it had for the new devices. I also had a good experience with upgrading a old BX board to a KT133 (non-a) with similar success.

just last weekend i bought a new mobo and processor and simply booted up, no issues yet

Originally Posted by jawsh77

just last weekend i bought a new mobo and processor and simply booted up, no issues yet

This absolutely needs to be stickied.

How does this work if you require a 3rd party SATA drive or SCSI driver? Will it give an option to put in a floppy?

FWIW I used this method to,temporarily during an RMA, move my main gaming system's drive over to my dualie and back, and it figured out the correct HALs and everything, detecting the duals and then going back to single with ease.

I used this on my workstation so that I could move my ATA133 card up one pci slot to make room for a cnr card. I boot off of this card. Mini-Setup/PnP/ReSeal is what I used. Slicker than sno_

Originally Posted by Barnaby

How does this work if you require a 3rd party SATA drive or SCSI driver? Will it give an option to put in a floppy?

I don't have direct experience, but I believe it's fully supported. Look at the sysprep.inf. There is a section for mass storage and 3rd party OEM drivers.

Add OEM Drivers
Mass storage

Like the guy with the SATA driver question, I'm getting ready to switch from a K8VT800 to an nForce 3 250 mobo. I was really dreading that SCSI/SATA F6 crap. Gigabyte hid the SATA SCSI drivers on their damned website instead of on a floppy. The ones on the CD-rom were not even correct. That was one serious PITA to get done. Hopefully, the switchover to the nForce will be less painful with the Sysprep method.
Thanks again!

I do this all the time at work.

That looks very handy, I will look into it! Thanks!

Dumb question, whats a HAL? ANother dumb question, what if you modified your temp and swap files to diff physical drives, would these just be reset to default?