Is Win7-64 smart enough to work with a new/different MoBo install?

[BillW]

I currently have a PC with a failed MoBo/PSU (on another Seven forum thread).

I know in the past with older OS versions, they didn't like it if you changed/upgraded the MoBo to a different type (i.e. chipset, etc.), because the MoBo (Windows OS) drivers that were in place when it was originally installed was not compatible with a new MoBo. This usually caused the OS to get trashed when booting up and self-attempting to fix itself due to new hardware.

Has anyone had experience upgrading their MoBo with an existing Win7-64 install on their HD?

I'd really rather not have to do a fresh install, and then wait (days) to load and install the 100's of updates, then reinstall all my programs. Arg!

Thanks,
Bill

 

[derekimo]

I think this will be helpful if you are doing that,

http://www.sevenforums.com/tutorials/292068-make-windows-7-bootable-after-motherboard-swap.html

 

[ignatzatsonic]

I just did something similar in the last couple of weeks on a backup PC, but with a Vista 32 bit install.

I went from a Intel motherboard with a G965 chipset and Core 2 Duo E6600 CPU from 2006 to a Gigabyte board with an H67 chipset and an i5-2500 CPU from 2011.

All I changed was the board, CPU, and RAM. The hard drives and Windows installation were identical. I didn't know how well it would work, but I figured it was worth a shot as I didn't want to reinstall a bunch of applications.

It took several hours after the first boot attempt to get it straightened out. It did boot on the first attempt, but looked ugly.

I think there were 4 or 5 bangs in Device Manager, but I got that fairly well sobered up by getting new Vista 32 drivers from Gigabyte.

The worst of it was getting the display tolerable. I thought I had it in an acceptable state and was about to shut it down, when suddenly the screen turned into a kaleidoscope-like pattern, with the icons and menus at the lowest level of legibility--almost unreadable.

I fought that for probably an hour and was about to accept the kaleidoscope as OK because, after all, this is a backup PC that I likely would not use for more than 2 or 3 days per decade---when just as suddenly the screen started behaving. Even though I hadn't done anything I hadn't tried a half dozen times previously.

I can't explain that, but overall it was worthwhile, satisfied my curiosity, and saved me some time.

I'd imagine 64-bit Windows 7 might be even less of a hassle.

 

[BillW]

I think this will be helpful if you are doing that,

http://www.sevenforums.com/tutorials/292068-make-windows-7-bootable-after-motherboard-swap.html

I checked this out, and it seems like the most viable option out there. Funny, I was planning (like most of us) to do a clone backup of C: drive, so just in case the drive died, I'd have a near current plug-n-play backup.

Thanks for the tip!

 

[BillW]

I just did something similar in the last couple of weeks on a backup PC, but with a Vista 32 bit install.

I went from a Intel motherboard with a G965 chipset and Core 2 Duo E6600 CPU from 2006 to a Gigabyte board with an H67 chipset and an i5-2500 CPU from 2011.

I suppose success on this shotgun approach really depends on having enough core commonality between MoBo's so you can at least boot up. Windows in general has become fairly good at fixing itself, starting with XP.

I can't explain that, but overall it was worthwhile, satisfied my curiosity, and saved me some time.

I'd imagine 64-bit Windows 7 might be even less of a hassle.

Again, this is probably the case of Windows update getting the correct drivers loaded. Just when you think it's hopeless, there's still light. I just with I had that cloned drive available ahead of time, so I have a way to go back if things go south.

 

[Mellon Head]

Keep in mind that swapping the motherboard will require reactivation of Windows. If you have a retail license, this is not a problem, however if you have an OEM license you will need to call Microsoft. You may have to talk to a representative to reactivate. If you explain clearly enough that your mobo died and that you can't get the exact replacement, they may allow you to reactivate your copy of Win 7. I was fortunate in that they allowed me to reactivate, but that was before they were ramming Win 10 down our throats. Things may be different now.

Just something to keep in mind.

 

[torchwood]

Very true MH,
they'll more than likely give you a W10 key only

Roy

 

[BillW]

Keep in mind that swapping the motherboard will require reactivation of Windows. If you have a retail license, this is not a problem, however if you have an OEM license you will need to call Microsoft. You may have to talk to a representative to reactivate. If you explain clearly enough that your mobo died and that you can't get the exact replacement, they may allow you to reactivate your copy of Win 7. I was fortunate in that they allowed me to reactivate, but that was before they were ramming Win 10 down our throats. Things may be different now.

Just something to keep in mind.

Thanks for the heads up. Some time ago, I bought a Win7 OS disk for MoBo upgrades, build for just this purpose. I have a Gateway so it's an OEM license. I'm in the process of trying to get a replacement Acer MoBo that close to the original (can't find the original type). If the new MoBo works as-is works, that's great, otherwise, I may have to go the MS-CS route. I really, really, really don't want to be forced to go to Win10!

To paraphrase C3PO, "Why Microsoft has to fix what ain't broke, is quite beyond my capacity."