F5F Stay Refreshed Software Operating Systems Clone HDD to SSD without OS installation path

Clone HDD to SSD without OS installation path

Clone HDD to SSD without OS installation path

T
thejuanjo123
Junior Member
4
11-08-2016, 09:33 AM
#1
I tried to refresh an older 2014 Asus 2-in-1 with a 1TB HDD, 8GB RAM, and dual-core CPU. After taking out the optical drive and using a 2.5-inch SSD, I added another 1TB SSD and installed an 8GB DDR3 stick in the available slot (the other 4GB was soldered). I formatted the SSD with Macrium Free and cloned the HDD to it. Everything seemed to work until I rebooted. The PC felt sluggish, but I thought it was just the SATA connection limits. After formatting the HDD, I discovered Asus's BIOS trick—forcing a specific path if the default one failed. I spent several tries trying to redirect the boot path to the SSD and eventually deleted the alternate route. When I finally booted again, the original HDD path returned in the BIOS. In short, after a few reboots after cloning, I got a misleading sign of a working OS clone. Now I use the Command Prompt to clean the HDD overnight. When I came home, I noticed nearly 8GB of RAM was being used (usually around 3GB idle). I suspect it ran part of the OS directly from RAM after cleaning. My issue is clear: how do I create a new boot path through a very basic BIOS? Or should I manually remove the old files and data from the drive? I’m certain they’re still there—when I tried to build a custom OS path in the BIOS, it took me through hundreds of files and programs, forcing me to restart. Each dead end left me searching for something, until I finally wiped everything and installed a fresh Windows version. Any advice would be greatly appreciated—I’ve been struggling nonstop online.
T
thejuanjo123
11-08-2016, 09:33 AM #1

I tried to refresh an older 2014 Asus 2-in-1 with a 1TB HDD, 8GB RAM, and dual-core CPU. After taking out the optical drive and using a 2.5-inch SSD, I added another 1TB SSD and installed an 8GB DDR3 stick in the available slot (the other 4GB was soldered). I formatted the SSD with Macrium Free and cloned the HDD to it. Everything seemed to work until I rebooted. The PC felt sluggish, but I thought it was just the SATA connection limits. After formatting the HDD, I discovered Asus's BIOS trick—forcing a specific path if the default one failed. I spent several tries trying to redirect the boot path to the SSD and eventually deleted the alternate route. When I finally booted again, the original HDD path returned in the BIOS. In short, after a few reboots after cloning, I got a misleading sign of a working OS clone. Now I use the Command Prompt to clean the HDD overnight. When I came home, I noticed nearly 8GB of RAM was being used (usually around 3GB idle). I suspect it ran part of the OS directly from RAM after cleaning. My issue is clear: how do I create a new boot path through a very basic BIOS? Or should I manually remove the old files and data from the drive? I’m certain they’re still there—when I tried to build a custom OS path in the BIOS, it took me through hundreds of files and programs, forcing me to restart. Each dead end left me searching for something, until I finally wiped everything and installed a fresh Windows version. Any advice would be greatly appreciated—I’ve been struggling nonstop online.

F
158
11-08-2016, 10:56 AM
#2
F
FrostyPorkChop
11-08-2016, 10:56 AM #2

F
FooxyPvP
Junior Member
8
11-16-2016, 08:32 PM
#3
I was trying to boost performance by adding storage, but the HDD became the main bottleneck. I replaced it with a clone on an SSD and used the HDD less often. However, after a failed SSD boot (ASUS forced an old drive path), I lost access to the HDD and its boot settings. I’m unsure how to recover or fix this. Would it be easier to locate the correct boot folder in BIOS, or should I swap the SSD into my PC and manually transfer the necessary data before reinstalling Windows (removing everything unnecessary)? Thanks for your advice.
F
FooxyPvP
11-16-2016, 08:32 PM #3

I was trying to boost performance by adding storage, but the HDD became the main bottleneck. I replaced it with a clone on an SSD and used the HDD less often. However, after a failed SSD boot (ASUS forced an old drive path), I lost access to the HDD and its boot settings. I’m unsure how to recover or fix this. Would it be easier to locate the correct boot folder in BIOS, or should I swap the SSD into my PC and manually transfer the necessary data before reinstalling Windows (removing everything unnecessary)? Thanks for your advice.

D
djninja444
Member
173
11-16-2016, 11:47 PM
#4
Cloning the HDD onto the SSD should allow the system to start using only the SSD. If that doesn't work, you can transfer data from the HDD and reinstall a fresh Windows on the SSD. Be cautious about keeping folders intact during the installation process.
D
djninja444
11-16-2016, 11:47 PM #4

Cloning the HDD onto the SSD should allow the system to start using only the SSD. If that doesn't work, you can transfer data from the HDD and reinstall a fresh Windows on the SSD. Be cautious about keeping folders intact during the installation process.

M
Mrender3
Senior Member
412
11-18-2016, 02:51 AM
#5
If this were true, it shouldn't be causing the path issue since the HDD has been wiped. Only the SSD still has the operating system. I can attempt to extract the HDD tomorrow to check. When I said a clean install, it meant removing some picture folders, formatting the SSD, and then starting a fresh Windows setup. Thanks for your feedback.
M
Mrender3
11-18-2016, 02:51 AM #5

If this were true, it shouldn't be causing the path issue since the HDD has been wiped. Only the SSD still has the operating system. I can attempt to extract the HDD tomorrow to check. When I said a clean install, it meant removing some picture folders, formatting the SSD, and then starting a fresh Windows setup. Thanks for your feedback.

C
cfmitch
Junior Member
40
11-18-2016, 04:44 AM
#6
That's why I recommended relocating the SSD to the same port as the HDD, especially if it's tied to the boot drive. Check if it starts up; if so, try moving the HDD into the caddy and see if it still works. Possibly format the HDD from another machine to confirm nothing remains that could trick it into thinking it's the boot device. Usually, when cleaning drives, I boot into Linux, rebuild the GPT table, leave partitions empty, and then set them up in Windows once confirmed. I rarely clone drives—better safe than sorry. I always erase everything and install fresh on just the new drive before adding the old ones back. After all, it's wise to have a backup elsewhere.
C
cfmitch
11-18-2016, 04:44 AM #6

That's why I recommended relocating the SSD to the same port as the HDD, especially if it's tied to the boot drive. Check if it starts up; if so, try moving the HDD into the caddy and see if it still works. Possibly format the HDD from another machine to confirm nothing remains that could trick it into thinking it's the boot device. Usually, when cleaning drives, I boot into Linux, rebuild the GPT table, leave partitions empty, and then set them up in Windows once confirmed. I rarely clone drives—better safe than sorry. I always erase everything and install fresh on just the new drive before adding the old ones back. After all, it's wise to have a backup elsewhere.