Changing out the motherboard without reinstalling OS...

desura

Diamond Member
Mar 22, 2013
4,627
129
101
There is a very good chance I'm going to have to replace my motherboard.

Really dreading this.

Is there any way to can save my windows install? Or will I likely have to do a clean install?
 

QueBert

Lifer
Jan 6, 2002
22,460
775
126
A lot of people will recommend a clean install, I've upgraded my computer a crap-load of times over the years and the only time I had to do a clean install was due to a bad MB which corrupted my HD. I uninstall any drivers that came with my MB, and when I reboot with the new MB I install the drivers like normal. I haven't done this for Windows 7 or 8, but I've done it for every other version of Windows without any issues.

I've also gone from AMD to Intel without any troubles. Sysprep sounds interesting, I've honestly never heard about it until reading this post, but I'm going to go read up on it.
 

jkauff

Senior member
Oct 4, 2012
583
13
81
It'll cost you some money, but if you buy Acronis True Image they will also sell you a Plus Pack that allows you to restore an Acronis backup to different hardware. It apparently creates a HAL for the new hardware with generic drivers, which you can then update with the real drivers after you restore your backup.

Probably an $80 total investment, but True Image is an excellent backup program worth paying for on its own and you'll save hours of work.
 
Last edited:

RFC Rudel

Member
Oct 19, 2005
49
1
66
I have do that, even if the cpu where diferent (amd/intel)

but HD controller configuration and os configuration are the ones that will give trouble.


windows will require reactivation also.


before any attempt. a full backup to another hd.


If you want want to play safe and not have have any problems a clean install is the best.

For Microsoft OS normaly you spend more time troubleshooting that reinstalling.....
 

saberasus007

Junior Member
Oct 26, 2013
15
0
66
I have heard about Acronis True Image having a feature that will allow you to simply move over to another motherboard/hardware without a reinstall. However I have never tried it.

Some time Lloyd Case, I believe, wrote an in depth article on being able to keep your current install of Windows while changing motherboards. http://www.pcworld.com/article/200827/how_to_upgrade_your_motherboard_the_easy_way.html

Now thing have changed slightly since that article was first published.

NOTICE: I take no responsibility and I assume no liability if anything happens to your data, hardware or anything involved in this strictly user experienced, uncertified, method of changing out motherboards with different chipsets. You assume all risk, all liabilities. If you can't, then please do not attempt. If you can, clone your drive you are going to be using before you start any changes. Test that clone drive to make sure it works like your current drive. Then to test out the procedures below, use this cloned drive so you can see if you are going to run into any problems and if so what to do to fix it. I did this and cloned it two more times and tested my method two more times before I committed to it. If you have the money or spare hard drive, you can clone your drive that you are using with your old motherboard and keep it just in case you need to revert back to that motherboard, because you new mobo is DOA or other issues and you need to have access to a computer.

First step after reading Lloyd's article, is to make sure you feel comfortable in the registry, device manager and a file browser (to delete folders) and understand how each step will affect your computer. If you are uncertain, then doing a clean install might be a better direction to go. However if you have the time and the spare hard drive, it can't hurt to try.

Be aware that your system will not be operating at its best using this method. Simply because despite all the steps below, the registry is touchy as is Windows (I can only say this works on XP and Windows 7 32 bit ONLY - I have not tested it on Vista, or a 64bit OS) and there is almost certainly something left behind somewhere that will hinder performance. How much? When I did this, I really didn't notice any major lags, drops in fps, slow down in uncompressing/compressing files/videos, etc. It will simply vary by system. Now switching Intel chipset to Intel chipset or AMD chipset to AMD chipset have the great chance for success. Going Intel/AMD to AMD/Intel or even Nvidia to Intel/AMD you could encounter problems. Simply because of the motherboard chipset drivers.

Now go into your bios and undo any tweaking (aka overclocking) you did. You need to bring the bios and your install into a state of default configuration, meaning all items working and not being tweaked in any manner.

Once you get into windows first thing is to remove all the drivers for things that aren't needed to continue to work in your install of Windows. Firewire, sound, optical drives, etc. you will want to go ahead and uninstall. Once you have remove the obvious, you will want to make sure you search the registry and usually (C drive) for any folders or entries with information on those items you just removed. You will then want to

Then you need to open a cmd prompt via admin priv. If unsure how to do, simply find your command prompt link/shortcut in your start menu, right click on it and tell it to run/open as admin. Now type the next set of commands exactly as they are typed:

set devmgr_show_nonpresent_devices=1
start devmgmt.msc

This will bring up the device manager. I will only say this once, okay twice or more, do not leave device manager during this process or you will have to go back to starting up a command prompt.

Now go into the VIEW menu and select who hidden devices. You will then go through and find any left over entries for any devices you have uninstalled, like your firewire, sound, etc. Make sure they are deleted/uninstalled.

Now before you reboot, be aware that you will need to enter your bios, BEFORE, the OS loads up. If you have lets say a Soundblaster card in one of your pci/pcie slots that you uninstalled the drivers for, make sure you shut your system down, unplug it, dischage any power left by pressing the power button and then making sure you are grounded and either on an anti-static mat, gloves or other anti-esd damaging devices, remove those/that card from the system and set it aside. Same thing for optical drives, hard drives, etc (you can simply unplug the cables from the mobo and the drive itself, without having to actually remove the device (but NOTE: it is advisable to do remove these devices as they don't take kindly to all the banging around that might occur while you are installing your new mobo). Make sure when you reboot you go straight into your bios. The reason, all those devices you just uninstalled like firewire, you are going to disable them in the bios so the computer doesn't try to create registry/device manager entries for them. Once you have done that, go ahead and go back into windows.

Now this is the confusing part. You will need to remember all those programs that required some sort of activation/authorization that has limits on installs. Programs like Omnipage, Paperport, Adobe, Corel, just to name a few will require a reactivation/authorization when you move to the new motherboard and in most cases that will require you to have to wait on hold for tech support or worse wait for an email response, to get them to allow you to reactivate your product (so also make sure you know the email address, passwords and serials used for those products). Now in terms of games, I really didn't encounter any that had issues. Since you are allowed more than 1 install in most games, you will simply just need to activate them on the new system.

If you have Steam with games you bought from them, you can re-download them with no issues if you have to. Just make sure that you never-ever-ever double login or give your old drive with the Steam games on it, as you could cost yourself your account and your games. Hence the reason to clone/back up everything before trying any of this.

Now you are into the hardest part and most difficult, the purging of your old motherboard and its devices and other devices that you added to your motherboard (like graphic cards, gaming keyboards, special configured mice/mouse, etc.).

You will once again want to take the approach of what can I uninstall now that won't affect my ability to use windows. You don't want to touch the chipset drivers or the controllers for your SATA just yet. Once again eliminate all those devices/drivers that are for items that will not affect your access to your system. I would leave your network devices alone until you have downloaded every single driver for your new motherboard and for all the parts you will be moving over to the new motherboard, have them unzipped/unrared and ready to be installed. If you don't, especially with the chipset drivers, you risk BSOD.

Once you have got yourself down to just the chipset, video, controller (SATA) drivers, CPU, Intel or AMD specific drivers, go ahead and go through the command prompt stage again where you type those commands in the dos prompt and clear the device manager, the registry and any folders on your computer. Do not reboot, shut down system instead. Remove any devices you just removed, like you did earlier. Then when you do reboot, go straight to the bios, not the OS, and continue the process of disabling any items you have uninstalled in the OS, so they don't get re-detected when you do get back into windows.

Now I can't find my instructions on how to deal with AHCI. I will search for them, however you can bring AHCI into your new system, even if you didn't have it enabled/installed on your current motherboard (ask around just in case I can't find my step by step guide I used for my change over).

Note, you should go into device manager via your command prompt as shown above before the final purge. Make sure any remaining duplicate entries that are greyed/blued out are removed and only those that have a solid color still remain as you might not get a chance to remove any duplicate entries after starting the final purge.

Now the final step of the purge, uninstall your graphic drivers and finally your chipset drivers. You might encounter a lock-up/bsod or an unstable windows. Don't worry. Once again remove any folders, registry entries and go into device manager via the command prompt and remove any remaining entries for the items you have uninstalled, if you forgot to do it before this step. DO NOT REBOOT, no matter what the software says. Make sure you are disconnected from the internet, even if you have uninstalled the network drivers.

Shut your system down. Now follow proper handling of ESD sensitive devices and remove your old mobo and insert your new mobo in the case (won't go over the install of a mobo, that is covered elsewhere by others in forums, videos and the instructions that came with your new mobo).

Now when you first power up, go straight into the bios, not the OS. What you will want to do is disable all devices like firewire, sound, raid, etc. Essentially your bios should be bare bones, the controller that the hard drive is on, maybe the 1 but not both if you them, network devices, leave off usb3.0, etc. Think of it this way, you want to have the least number of devices that the OS will need to detect and install drivers for. The more you have, the risker the switch will be and the chance of failure is greater.

Once you have disabled those, do not try any tweaks or overclock. Do not change anything that would be consider a way to get more performance (using X.M.P. memory profiles instead of the default detected by the new motherboard). Now boot into the OS.

If everything worked out right, the OS will begin to identify the devices. Do not allow it to (since you should still have your network cable unplugged and/or no network devices enabled in the bios). Allow the OS to go through all the identification. Don't worry about installing any drivers on this pass. Windows will be essentially installing just what it needs to work. Once it has done all (be careful as Windows will sometimes have a delay between detection of devices where it will say reboot, so be patient and wait). Once done, reboot and hopefully you will get back into your OS. If you are in your OS, then you have probably succedded in the swap. You will want to go into your device manager one last time via the command prompt instructions listed above to verify nothing from your old system is present. If that is okay, then you can begin the install of drivers, starting with the chipset.

Now I am more cautious than others, I believe in installing one driver at a time and rebooting after each. Don't try to intall all your hardware drivers in one install session, that creates a chance of problems. Next probably get your vga driver up and running. Beyond this you should follow how the process for installing a new motherboard goes. When you are at a point, you should then go into your bios, and enable one device per install session (session being from the OS loading, you install a driver, and are being asked, hopefully to restart the computer) till you have it all up. Then you should try some of your software, games, etc. to make sure the system is working properly. Reinstall your anti-virus/malware/firewall, adobe/corel/etc. Then you should find something you can run overnight, heck go find a huge torrent, even if you don't want it, and have it download or do a virus scan of your entire system with all the detection settings set to their most harsh or sensitive. Run a game that has a looping demo, etc.

At first do not overstress your system. Remember it is always good to allow the bonding of your cpu and its cooling device, just like how you treat a new car when you first drive it off the lot (you don't go to Le Mans speedway and start racing, so the same with the cpu and mobo). You can also run memtest86 which will test your memory features. Try not to shut down your computer for up to 72 hours (some will debate this but you want a good burn-in time to see if the motherboard is stable and works).

I hope this helps.

I have done this on the following configurations:
Nvidia to Intel
Intel to Nvidia
Nvidia to Nvidia to Intel

All worked. When I had time I would do a clean install on a brand new hard drive, and work on it during my free time, while having my other install avaialable for my day to day uses.

Post any follow-up ?'s you might have. I will look for the step by step I created for myself to get the AHCI drivers into the swap of motherboards, especially if you did not have it enabled on your old motherboard, if you did have it, then make sure it is enabled, before you boot into the OS with your new motherboard. Be aware also that if you did RAID, I am not sure if this procedure will work it, as I have never used RAID in any of my install/setups.
 

flexy

Diamond Member
Sep 28, 2001
8,464
155
106
This is an AWFUL amount of work (above post)..seriously I'd rather do a new install instead.

I have to admit too, I never heard of the "sysprep" method either.

The last time I changed my motherboard it was VERY simple, I only deleted some registry entries (based on some article I found, sorry, forgot....), booted, and it installed all my drivers and everything was great.

BUT: This was with a board VERY similar (same chipset!) to the one I had in before after my board crapped out so things didn't really change a lot.

So...I'd say if a major upgrade is being made, changing CPU, chipset etc. I'd probably say install new...not even "sysprep" because it can make sense to really start clean with new registry and no leftovers.
 

KentState

Diamond Member
Oct 19, 2001
8,397
393
126
Like flexy said, it comes down to how many of the components are changing. I just swapped one Z87 board for another and didn't have any problems. I just uninstalled as many device specific pieces of software before doing the swap.
 

Engineer

Elite Member
Oct 9, 1999
39,234
701
126
I tend to agree on the re-install but if I have many, many apps already installed, then I would be tempted to just swap. Some apps are a pain to install and take quite a bit of time (especially older apps that I would need to call in on to reactivate - UGH). I would, as others say, back up EVERYTHING before doing anything though.
 

KentState

Diamond Member
Oct 19, 2001
8,397
393
126
I tend to agree on the re-install but if I have many, many apps already installed, then I would be tempted to just swap. Some apps are a pain to install and take quite a bit of time (especially older apps that I would need to call in on to reactivate - UGH). I would, as others say, back up EVERYTHING before doing anything though.

I guess the way to look at it is, try it out and if things don't work out then reinstall.
 

QuietDad

Senior member
Dec 18, 2005
523
79
91
Install the drivers for the NEW motherboard to Windows before you swap the OLD one out. That way when booting, Windows finds the drivers for the NEW motherboard without really having to go look for it. I do this all the time and I'm 99% successful. If this doesn't work, I to a repair install of windows that fixes the drivers while retaining everything else good enough to get it booted and cleanup driver issues by installing the drivers provided by the NEW motherboard or where there are better alternatives to the default drivers. Or
 

RFC Rudel

Member
Oct 19, 2005
49
1
66
Install the drivers for the NEW motherboard to Windows before you swap the OLD one out. That way when booting, Windows finds the drivers for the NEW motherboard without really having to go look for it. I do this all the time and I'm 99% successful. If this doesn't work, I to a repair install of windows that fixes the drivers while retaining everything else good enough to get it booted and cleanup driver issues by installing the drivers provided by the NEW motherboard or where there are better alternatives to the default drivers. Or

in XP you uninstall the hal from the device manager and that force the os to redetect all hardware on the next reboot.
 

Fred B

Member
Sep 4, 2013
103
0
0
Done it a few times with W7/XP and no problems , just connect the os hd/ssd to the mobo in the same mode as before AHCI/raid . Boot the os disk and let it replace drivers from the driver cd rom, the only thing needs to be done is windows activation .
 

AkumaX

Lifer
Apr 20, 2000
12,642
3
81
OP, what are you migrating to?

With Windows 8, I went from a 3570K + Z77 to 4670K + Z87, and everything was flawless. No prepping whatsover!

Only thing was Windows Activation (which MS support handled pretty well)
 

jkauff

Senior member
Oct 4, 2012
583
13
81
OP, what are you migrating to?

With Windows 8, I went from a 3570K + Z77 to 4670K + Z87, and everything was flawless. No prepping whatsover!

Only thing was Windows Activation (which MS support handled pretty well)
That's a major change that would have spelled trouble with older versions of Windows. I wonder if Microsoft has finally relaxed the HAL rules. Corporate IT and DIY folks like us have been complaining for so many years about this, maybe they're finally starting to listen (like providing a "Builder" version of Win 8) now that consumer PC sales are in the toilet.
 

Subyman

Moderator <br> VC&G Forum
Mar 18, 2005
7,876
32
86
That's the worst part about tinkering, having to install windows. I was hoping they would tie the license to your MSN account so you could just log in and be fine, but they still require calling and punching in a huge string of numbers. Installing Mavericks on my Mac Pro was the way its meant to be
 

RU482

Lifer
Apr 9, 2000
12,689
3
81
Win7 is very resilient, as long as the disk mode (IDE vs AHCI) is the same, you shouldn't have any problems short of maybe having to re-enter the product key for the OS

Even XP can handle a swap pretty well
 

RU482

Lifer
Apr 9, 2000
12,689
3
81
That's a major change that would have spelled trouble with older versions of Windows. I wonder if Microsoft has finally relaxed the HAL rules. Corporate IT and DIY folks like us have been complaining for so many years about this, maybe they're finally starting to listen (like providing a "Builder" version of Win 8) now that consumer PC sales are in the toilet.

Bah, I've taken an XP image from a 945GME chipset, put it on an Atom, and then taken that image and put it on to a Q77 Ivy Bridge platform, and not had any major problems. Just have to make sure to install and update ALL the device drivers, and clean up afterwards
 

Meghan54

Lifer
Oct 18, 2009
11,573
5,096
136
That's a major change that would have spelled trouble with older versions of Windows. I wonder if Microsoft has finally relaxed the HAL rules. Corporate IT and DIY folks like us have been complaining for so many years about this, maybe they're finally starting to listen (like providing a "Builder" version of Win 8) now that consumer PC sales are in the toilet.


BS. I've moved my Win 7 build across at least 5 motherboard/cpu combos and have yet to have to reinstall. Just did what QBert and RU482 have done, just build the new computer, install hd/ssd from old into new, boot---making sure the BIOS is set as it was on the old, ACHI/RAID---and let Windows load the appropriate drivers. Windows will even tell you what it's missing and that's when you use the driver disc that came with the motherboard, typically the LAN driver and specific chipset driver.

Good to go after that.


And I was doing that back on XP without major problems, albeit an occasional hiccup. Win Vista and 7 are even smoother and rarely cause even the slightest hiccup.

I wonder why everyone's suggesting all that crazy work? It's not like Windows isn't a resilient OS...it is. And doing it the "easy" way won't cost you anything but a few minutes of your time. If it doesn't work, you're exactly where you were in the beginning, anyway, so you really have nothing to lose to try. Of course, this assumes you back up your data prior.
 
Last edited:

john3850

Golden Member
Oct 19, 2002
1,436
21
81
The old way that always worked for me was to remove all the drivers and replace them with genetic windows drivers before switching out the mb.
Many people went from intel to amd and back to intel without any proplems with xp and win7.

When there were system changes like double memory, L3 or a IMC people claimed you most do a clean install to get more speed so I did a clean install and I never saw any difference.
The only time I ever saw a difference with a clean install was before the pci was locked you would get much more data corruption .
 
Last edited:

QueBert

Lifer
Jan 6, 2002
22,460
775
126
I picked up a new MB last week, I decided to try using Sysprep, instructions were dead simple (Windows 8 here) It was doing it's thing, and after about I dunno 3 minutes it errored out. I rebooted to see what the hell, and Windows came up at VGA resolution and a few programs popped up asking for user name and password. I shrugged and tried running it again, it errored out right away this time. I decided I'd do what I always have done and would just swap the MB for the new one and see what happens. I'm not exactly sure why Sysprep crapped out, it just gave me a generic error message. Probably just my bad luck lol.

I then learned that Z87 boards don't use the same CPU's as Z77's. When I get a Haswell or whatever the new Intel chips are I'll report back how the straight swap goes. Done swaps dozens of times without ever having a problem. So I'm confused at how damn many people online claim you have to do a clean install

*shrug*
 

RonAKA

Member
Feb 18, 2007
165
0
0
There is a very good chance I'm going to have to replace my motherboard. Really dreading this. Is there any way to can save my windows install? Or will I likely have to do a clean install?

I have done it. I used a replacement but identical motherboard. As I recall the only changes needed were to reset the BIOS to the custom settings I had made. The operating system (XP in that case) was ok with it.
 

Namtaru

Senior member
Feb 25, 2003
556
0
76
I just swapped out my mobo/cpu from an Asus p6t/i7 920 (like 5 or 6 years old) to an MSI Z87-GD65/4770k.
I was/am running windows 8.

All I did was shut down the computer, swap the parts, turn it back on, uninstall any software related to the old motherboard, install new drivers for new motherboard, re-activate windows.

Been running for a few days now with zero issue.
 
sale-70-410-exam    | Exam-200-125-pdf    | we-sale-70-410-exam    | hot-sale-70-410-exam    | Latest-exam-700-603-Dumps    | Dumps-98-363-exams-date    | Certs-200-125-date    | Dumps-300-075-exams-date    | hot-sale-book-C8010-726-book    | Hot-Sale-200-310-Exam    | Exam-Description-200-310-dumps?    | hot-sale-book-200-125-book    | Latest-Updated-300-209-Exam    | Dumps-210-260-exams-date    | Download-200-125-Exam-PDF    | Exam-Description-300-101-dumps    | Certs-300-101-date    | Hot-Sale-300-075-Exam    | Latest-exam-200-125-Dumps    | Exam-Description-200-125-dumps    | Latest-Updated-300-075-Exam    | hot-sale-book-210-260-book    | Dumps-200-901-exams-date    | Certs-200-901-date    | Latest-exam-1Z0-062-Dumps    | Hot-Sale-1Z0-062-Exam    | Certs-CSSLP-date    | 100%-Pass-70-383-Exams    | Latest-JN0-360-real-exam-questions    | 100%-Pass-4A0-100-Real-Exam-Questions    | Dumps-300-135-exams-date    | Passed-200-105-Tech-Exams    | Latest-Updated-200-310-Exam    | Download-300-070-Exam-PDF    | Hot-Sale-JN0-360-Exam    | 100%-Pass-JN0-360-Exams    | 100%-Pass-JN0-360-Real-Exam-Questions    | Dumps-JN0-360-exams-date    | Exam-Description-1Z0-876-dumps    | Latest-exam-1Z0-876-Dumps    | Dumps-HPE0-Y53-exams-date    | 2017-Latest-HPE0-Y53-Exam    | 100%-Pass-HPE0-Y53-Real-Exam-Questions    | Pass-4A0-100-Exam    | Latest-4A0-100-Questions    | Dumps-98-365-exams-date    | 2017-Latest-98-365-Exam    | 100%-Pass-VCS-254-Exams    | 2017-Latest-VCS-273-Exam    | Dumps-200-355-exams-date    | 2017-Latest-300-320-Exam    | Pass-300-101-Exam    | 100%-Pass-300-115-Exams    |
http://www.portvapes.co.uk/    | http://www.portvapes.co.uk/    |