F5F Stay Refreshed Software Operating Systems Transfer data from an old hard drive to a fresh operating system on a new setup.

Transfer data from an old hard drive to a fresh operating system on a new setup.

Transfer data from an old hard drive to a fresh operating system on a new setup.

D
Domarus
Member
241
08-20-2016, 12:52 PM
#1
Reviewed the forum discussions and couldn't locate exact guidance for relocating an HDD on a new motherboard without reinstalling the OS. Slick mentioned successfully moving an old HDD across multiple PCs, which might be relevant. The current situation involves an aging motherboard that failed despite voltage regulator replacements, and the OS can't be reinstalled due to sensitive system files and errors in the HDD's sectors. It appears the goal is simply to run some programs on it without disrupting the existing Ubuntu setup. The old motherboard was an MSI 945M3 (MS-7267) with Intel Pentium D CPU, now being used with an ASUS M2N32WS PRO and AMD Athlon 64 X2. Any advice or steps for this process would be appreciated.
D
Domarus
08-20-2016, 12:52 PM #1

Reviewed the forum discussions and couldn't locate exact guidance for relocating an HDD on a new motherboard without reinstalling the OS. Slick mentioned successfully moving an old HDD across multiple PCs, which might be relevant. The current situation involves an aging motherboard that failed despite voltage regulator replacements, and the OS can't be reinstalled due to sensitive system files and errors in the HDD's sectors. It appears the goal is simply to run some programs on it without disrupting the existing Ubuntu setup. The old motherboard was an MSI 945M3 (MS-7267) with Intel Pentium D CPU, now being used with an ASUS M2N32WS PRO and AMD Athlon 64 X2. Any advice or steps for this process would be appreciated.

R
Redstoner137
Posting Freak
811
09-02-2016, 05:10 AM
#2
The main choices are limited. First, attempt to boot directly. If you see a BSOD, it means the device isn’t functional. Another option is to uninstall any existing drivers from the previous motherboard and then reinstall or repair the system, or try booting into the OS and installing fresh drivers. The third choice involves using a virtual machine to run the system. I’m not sure why bad sectors would stop you from installing a new operating system.
R
Redstoner137
09-02-2016, 05:10 AM #2

The main choices are limited. First, attempt to boot directly. If you see a BSOD, it means the device isn’t functional. Another option is to uninstall any existing drivers from the previous motherboard and then reinstall or repair the system, or try booting into the OS and installing fresh drivers. The third choice involves using a virtual machine to run the system. I’m not sure why bad sectors would stop you from installing a new operating system.

J
JishyCraft
Member
66
09-02-2016, 07:30 AM
#3
You misunderstood my explanation. It’s not necessary to reinstall the windows on that drive because it’s already damaged. I only saved the HDD for the operating system and applications. Otherwise, I’d just purchase a new HDD and install a fresh copy there. The OS starts until the first Windows logo appears, after which it restarts automatically. This is likely due to outdated drivers, but removing them isn’t possible without access to the original hardware. There’s a sysprep command, but it only works if you can still boot from the old system. Ideas don’t help since I have many of them. I’m looking for guidance on how to apply those ideas—what tools should I use, how to configure them, or what steps to take so the OS boots correctly on the new hardware? *Edit* I used a Hiren boot CD to fix the HDD controller and managed to boot Windows on an older machine nearby. However, when trying to run Sysprep to reinitialize Windows 7, it throws a fatal error. Does this relate to needing to reactivate Windows after moving the HDD to a new motherboard?
J
JishyCraft
09-02-2016, 07:30 AM #3

You misunderstood my explanation. It’s not necessary to reinstall the windows on that drive because it’s already damaged. I only saved the HDD for the operating system and applications. Otherwise, I’d just purchase a new HDD and install a fresh copy there. The OS starts until the first Windows logo appears, after which it restarts automatically. This is likely due to outdated drivers, but removing them isn’t possible without access to the original hardware. There’s a sysprep command, but it only works if you can still boot from the old system. Ideas don’t help since I have many of them. I’m looking for guidance on how to apply those ideas—what tools should I use, how to configure them, or what steps to take so the OS boots correctly on the new hardware? *Edit* I used a Hiren boot CD to fix the HDD controller and managed to boot Windows on an older machine nearby. However, when trying to run Sysprep to reinitialize Windows 7, it throws a fatal error. Does this relate to needing to reactivate Windows after moving the HDD to a new motherboard?

E
Empty_creeper
Member
51
09-03-2016, 05:50 PM
#4
Let's break this down in simpler terms.

I had to reinstall Windows on a brand new system. My old operating system and apps were still on an old hard drive. I thought I’d saved some registry settings by transferring them onto the new installation. However, when I tried to copy programs manually, I realized some files were stored in different places than expected.

I searched online for specific applications to see if they needed files elsewhere. Eventually, I located my license information and reinstalled the necessary apps. It turned out to be a bit of a hassle, especially if you don’t need everything right away—just back up your registry first and experiment carefully.
E
Empty_creeper
09-03-2016, 05:50 PM #4

Let's break this down in simpler terms.

I had to reinstall Windows on a brand new system. My old operating system and apps were still on an old hard drive. I thought I’d saved some registry settings by transferring them onto the new installation. However, when I tried to copy programs manually, I realized some files were stored in different places than expected.

I searched online for specific applications to see if they needed files elsewhere. Eventually, I located my license information and reinstalled the necessary apps. It turned out to be a bit of a hassle, especially if you don’t need everything right away—just back up your registry first and experiment carefully.

S
SolitudeFX
Member
131
09-18-2016, 04:01 PM
#5
I’m retaining the reinstall choice as a fallback. Right now I’m focusing on setting up Sysprep and ensuring Windows uses standard drivers, so you can reinstall them later once the new system is ready.
S
SolitudeFX
09-18-2016, 04:01 PM #5

I’m retaining the reinstall choice as a fallback. Right now I’m focusing on setting up Sysprep and ensuring Windows uses standard drivers, so you can reinstall them later once the new system is ready.

A
Aruan_Vargas
Member
233
09-18-2016, 05:10 PM
#6
This manual is intended for bootable setups only; however, some options might appear when you start from a disc. Check the link provided for more details. If it functions, feel free to share your experience—it's been a long time since I attempted something like this, and I'm open to hearing about newer methods or software updates.
A
Aruan_Vargas
09-18-2016, 05:10 PM #6

This manual is intended for bootable setups only; however, some options might appear when you start from a disc. Check the link provided for more details. If it functions, feel free to share your experience—it's been a long time since I attempted something like this, and I'm open to hearing about newer methods or software updates.