Make Windows 7 bootable after motherboard swap

Make Windows 7 bootable after motherboard swap, or bootable after swapping hard drive to new machine. Software described Paragon P2P Adjust OS.


This procedure describes how to do it. Procedure can be used in case of:

• Windows 7 Installation - Transfer to a New Computer doesn't work.
• You forgot to SYSPREP.
• You can't SYSPREP because your motherboard died.
• You simply don't want to use SYSPREP.

1. Download "Paragon Adaptive Restore 2010" from Paragon Adaptive Restore 2010 on my DROPBOX.
2. Burn the ISO to CD/DVD using Windows Disc Image Burner or ImgBurn.
3. Set CD/DVD as first boot device in BIOS.

Do the following:

1. Boot the computer from Paragon Windows PE 3.0 based CD/DVD.
2. Accept the end user license agreement, otherwise you are not able to use the tool.
   
3. Launch P2P Adjust OS.
   
4. Select the operating system you need to adjust to your new hardware.
   
5. Choose whether you want to add third-party drivers or not, and the way to do it.
   
6. If you chose "Adjust the OS to the new hardware automatically", the P2P Adjust OS Wizard will automatically accomplish all the necessary actions.
   
7. The only thing that might need your interaction is to specify additional driver repository.
   
8. At last, choose "Yes, apply the changes physically" and then restart your computer after operations are done. Do remember, you cannot interrupt the process or undo the changes.
   

Compelete pdf manual: Paragon Adaptive Restore 2010 on my DROPBOX.

Just before the OS adjustment, you can additionally:

   Warning

Sometimes the internal hard drive is not recognized in Paragon P2P Adjust OS due to missing SATA or RAID driver. In that case add specific drivers to Windows PE based Paragon Recovery Environment.

1. Click to open Add Drivers dialog.
   
2. Browse for an .INF file of the required driver, then click the Open button to initiate the process.
   
3. Click Yes to confirm the operation.
   

   Information

You can only add third-party drivers in INF file. If they are zipped, you need to unpack them before processing the steps. The Windows PE environment is 32bit-based, so you need to use 32-bit drivers for injection.

After procedure has finished succesfully and system boots fine, first check if Enable hardware auto-updating via Windows Update (Set to Automatic) is on so it will query Windows Update. After that:

1. Uninstall Device and Device Driver for devices no longer attached to system. Uninstall associated software as well.
2. Install all of your device drivers, then Windows Updates.
3. Refresh your Windows Experience Index (WEI) score.
4. When done, all you will need to do is to activate Windows 7.

After rebooting from disk, drivers should start swapping out in a cascade you can monitor by clicking on the system tray animation. Wait until all are finished before doing the requested restart. After reboot, go immediately to Check for Updates and install all Important and Optional Updates which may include critical drivers and patches for the OS to run on that hardware.

You must reactivate at the Change Product Key link on System page. If it's not present you can insert Product Key and then Activate using SLMgr Commands

On some systems you see "setup is preparing your computer for first use" on every reboot. Read this to fix that issue: Fix "Setup is Preparing Your Computer for First Use" on Every Reboot

Related Tutorials

---

• http://www.sevenforums.com/tutorials/135077-windows-7-installation-transfer-new-computer.html
• http://www.sevenforums.com/tutorials/681-startup-repair.html
• http://www.sevenforums.com/tutorials/96442-device-manager-finding-unknown-devices.html

 

[gregrocker]

C isn't System yet, Wolfgang.

Will EasyBCD do the job even though the existing BootMgr is XP?

 

[whs]

Yeah right - I missed that System part. But EasyBCD should copy the bootmgr from XP also - although I have never actually done that but I see no reason why not. It's worth a try.

 

[gregrocker]

That would be a problem then since it's a different bootmgr and boot code for XP, which a Win7 install only updates on the XP System partition to configure a Dual Boot. It would need to write a fresh Win7 boot manager to C which I believe Easy does.

If not confirm C remains Partition Marked Active then run Startup Repair - Run 3 Separate Times.

But if it messes up XP partition it might not boot without repairs. So beware.

 

[whs]

I don't think it will mess up XP. All EasyBCD does is copy.

 

[RoyInForest]

Almost worked - starts to boot then hangs

This looked like exactly what I needed to go from a DELL XPS 8100 to a Dell Inspiron. Both with Windows 7 Pro. XPS mother board died so I put hard drive into the Inspiron and followed the instructions for the PAR process. (which are REALLY well done, right down to the screen shots)

When I boot the end result it starts to load, shows the initial Windows 7 started graphic with the 4 circling dots, then the screen goes black as it reboots. I've run Windows Startup Repair multiple times from the Windows 7 Install disk with no luck. Repair says it can't fix it and the cause could be a configuration change (ya think?) I didn't get any messages during the PAR processes beside what you documented. No prompts for extra drivers, etc. I did see the messages scroll by as it injected drivers.

any suggestions about what I've missed. I really need this to succeed as I have software on the hard drive that is no longer available and my install CD is not readable for some reason (too many scratches??)

Thanks,
Roy

 

[gregrocker]

In the case of XP, what works to adjust it to start on new hardware is also an XP Repair Install.

It may actually be preferable since PAR was developed under Vista and Win7.
http://www.sevenforums.com/tutorial...lation-transfer-new-computer.html#post1161038

 

[Kaktussoft]

This looked like exactly what I needed to go from a DELL XPS 8100 to a Dell Inspiron. Both with Windows 7 Pro. XPS mother board died so I put hard drive into the Inspiron and followed the instructions for the PAR process. (which are REALLY well done, right down to the screen shots)

When I boot the end result it starts to load, shows the initial Windows 7 started graphic with the 4 circling dots, then the screen goes black as it reboots. I've run Windows Startup Repair multiple times from the Windows 7 Install disk with no luck. Repair says it can't fix it and the cause could be a configuration change (ya think?) I didn't get any messages during the PAR processes beside what you documented. No prompts for extra drivers, etc. I did see the messages scroll by as it injected drivers.

any suggestions about what I've missed. I really need this to succeed as I have software on the hard drive that is no longer available and my install CD is not readable for some reason (too many scratches??)

Thanks,
Roy

Safe mode works fine? Uninstall GPU driver.

 

[RoyInForest]

Unfortunately I can't boot into SAFE mode either. All options act the same, go part way then reboots.
I tried turning on bootlog but there was none produced so it may be ending before the log wold start, or (more likely) the boot fails without closing the log

 

[Kaktussoft]

Unfortunately I can't boot into SAFE mode either. All options act the same, go part way then reboots.
I tried turning on bootlog but there was none produced so it may be ending before the log wold start, or (more likely) the boot fails without closing the log

When exactly does it reboot?
Disable the automatic restart! How To Disable Automatic Restart on System Failure From the Advanced Boot Options Menu in Windows 7
What is the BSOD error? Stopcode and which DLL for example

 

[Tanu]

Created an accout an register just to thank you!! , this worked like a charm for me! .. Woohoo!!. Okay, lol but yeah pretty happy about it , cause I switched a motherboard yes an forgot (more like didnt think about it at all ) the sysprep. But naturally I wanted to keep everything etc, but yeah would always crash an the other solutions an ways I tried didnt really do much for me like the repair tool. And im perhaps not the greatest with computers, but since I reached my desktop thanks to this gem, Im pretty sure ill be able to fix any issue that might occur, and am working on uninstalling and installing my drivers at the moment, might take a bit, but so far no prompt about any w7 key or anything, even still had my background image . Either way, this was exactly what I wanted and needed. Also well explained and easy to follow .

Either way again, just again wanted to say thank you!!! ). You rock, and you are awesome, period! .

THANK YOU!!!!!!

 

[betaupsilon]

I actually used this tool to resolve some quirks when restoring an XP image onto another computer. I did the restoration twice one using the XP REPAIR install to resolve driver issues, & the 2nd time using this tool. The REPAIR install did not resolve everything, but it appears this tool nearly did.

 

[gregrocker]

Do we know if PAR works with UEFI? Can we test it soon to report back here and will you if necessary update the thread since BIOS is going away?

Also appreciate you commenting if you feel like it in http://www.sevenforums.com/installation-setup/367466-uefi-legacy.html#post3048874

 

[JoePublic]

Hi,

I'm about to attempt a motherboard/cpu upgrade, and plan on using Paragon to try and do it without needing to reinstall Win 7.

I'll be upgrading from my current Phenom II X6 setup (detailed in my profile) to a GA-78lmt-usb3 motherboard, with a AMD FX 6300 cpu on it.

I've made 3 back ups of all my important files, via 3 different methods, just to make damn sure I don't lose anything, and I'll also disconnect that second HDD for the duration of the upgrade process.

Now... there's just one element to all this that's confusing me, and that's the storage interface setup...

This PC, although coming to me with just one HDD in it, seems to have RAID set as the 'onboard SATA mode' when I look in the bios set up.

I've read of a few problems with the whole process of upgrading the motherboard, related to problems recognising the hard drives when the computer attempts to boot after the new hardware has been dropped in.

So... is there anything I need to do in advance to avoid such problems, or will Paragon take care of it automatically?

I'm not even sure why that setting is on RAID??? Although I've added a secondary hard drive since I got the PC, I haven't set up any RAID options, and basically... don't need it. I back up my work regularly.

So... should I just change to IDE or AHCI before I get started with the upgrade?

Any advice greatly appreciated.

EDIT: Just to note that I did see the instructions in the tutorial for adding drivers, but... having downloaded all the drivers from the Gigabyte site and unpacked them... they come with an installer and no sign of any .inf files???

 

[JoePublic]

OK... I found the .inf files, but... just so I understand this correctly... it's the 32bit versions that Paragon needs, despite the OS be a 64bit version... yes?

 

[gregrocker]

Some mobos have RAID as a generic SATA setting but it's strange yours has the preferred AHCI choice as an alternative.

If you're sure you don't' have two hard drives in an array then I think I would do a Clean Reinstall Windows 7
with only the target HD plugged in, deleting all partitions during the booted install.

You can try PAR to see if it will work. But to be sure I think I'd SysPrep to move HD to another computer
which is the preferred IT method that if followed carefully may be more of a sure thing.

 

[JoePublic]

Yep, the PC ony came with one hard drive in when I got it, however... I did buy it from someone else, not from a store. So, I guess it's possible the previous owner had a second drive and they set up RAID and removed the second drive before selling the PC to me.

I added my own second drive a couple of months ago, but didn't do any RAID configuration.

The options in the bios set up, under integrated peripherals > onboard SATA mode' are: RAID, Native IDE and AHCI, with it currently set on RAID.

Boot priority points to RAID ready, so... that means it's set on RAID, but not configured as such, right?

I'd like to avoid a clean install if possible, because that means I'd have to reinstall everything else, Adobe CS6, Sony Vegas and a host of other programs, plus all the accompanying MS updates... it'll take an age.

 

[JoePublic]

Well, anyway... having triple saved all my important stuff... I'll try and run with the PAR option. I guess worst case scenario is that it doesn't work and I just do a full reinstall of everything.

Considering the warnings associated with RAID and sysprep failures, etc, etc... I think this is the way to go... for my circumstances, anyway.

If I can get away without reinstalling windows and/or needing to reactivate windows and all my other software that needs activation... great.

If not... hours of tedium await.

 

[gregrocker]

If this is still the factory install then I would most certainly choose the Clean Reinstall Windows 7
which is a vastly superior install to the factory junk install. Over 1.3+ consumers have used that tutorial without a single problem or complaint. They have the best Win7 installs in the world, and they stay that way as long as one sticks with only the tools and methods in the tutorial.

Be sure to reset BIOS to defaults and SATA controller to AHCI, install with only one hard drive present.

 

[JoePublic]

Had already started the PAR option when I came back to read your reply.

If I decide to do a clean install... there's no downside to doing so after I've let PAR do it's job, if I want the clean install experience, is there?

It's just that I have a very small window for this right now... got work deadlines, and I probably shouldn't have even tried doing this upgrade at all right now, but... it could be a few weeks before I get another 1 day window.

 

[gregrocker]

No can't think of any downside. Just be sure to follow Clean Reinstall Windows 7