First Boot From the Cloned SSD Disconnect the Old Drive and Fix Boot Order
The clone finished without a single error — and the PC boots exactly as slowly as before. Nine times out of ten nothing is broken: the machine quietly started from the old hard disk again, because nobody told it not to. The first boot test exists to remove that doubt completely.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 7 minute read
🎥 Watch the full cloning process in the video — every click in Macrium Reflect, live on a real PC
Two identical copies of Windows now exist, and your PC's firmware has opinions about which one to start. The first boot after cloning is therefore a test with one variable removed: the old drive comes off, so whatever boots is unquestionably the SSD. This page covers the test itself, how to prove the SSD really started, and — for the day you reconnect the old drive and the PC picks the wrong one — the boot order fix that settles it permanently.
First boot test — the only honest setup
✅ Old HDD data cable disconnected
✅ Only ONE bootable Windows in the machine — the SSD's
✅ PC boots to your desktop, visibly faster
✅ Restart once more and confirm it again
Both drives connected for the "test"PROVES NOTHING
👆 With two identical Windows copies attached, a successful boot tells you nothing about which one started (checklist panel)
1
Run the Test Properly
Shut Windows down fully — not sleep, not hibernate; hold Shift while clicking Shut down if Fast Startup is enabled, so the machine truly powers off
Desktop: pull the SATA data cable from the old HDD. Laptop: your SSD is already the only internal drive if you swapped it in
Power on. The PC has exactly one place to go — the SSD
Reach your desktop, open your main programs, browse a few files
Restart once and confirm the same fast, clean start
Passed? The clone is proven. Everything after this is housekeeping. Failed — the PC reports no bootable device or drops into recovery? The usual suspect is a missing small system partition; the partition guide in this set explains it, and the cure is a complete re-clone, not panic.
2
Prove It Really Is the SSD
Fast boot times are persuasive, but proof is better than persuasion — especially if you later reconnect the old drive and want certainty about which Windows you are running.
Open Disk Management and find the disk marked (Boot, Page File, Crash Dump) next to C — on the test boot, that disk is the SSD by elimination
Or open Task Manager, Performance tab: the disk running C should report its type as SSD
Notice the feel honestly: log-in to usable desktop, first program launch, a big folder opening — an HDD-to-SSD clone makes all three unmistakably quicker, not marginally
3
Reconnect the Old Drive Without Losing the Plot
After the proof week (the old-HDD guide in this set explains the timing), you will reconnect the old drive as storage. That is the moment boot confusion can return, because the firmware again sees two Windows Boot Manager entries that look identical. The defence is order, set once:
Reconnect the old drive and start the PC, tapping your BIOS key (Del or F2 on most boards; the boot menu is often F12, F8 or Esc)
In the Boot section, set the SSD — listed as its model name or as Windows Boot Manager on that disk — as the first boot device
Save and exit, and let it boot fully
Verify with the Disk Management check above that C is running from the SSD
4
When It Keeps Booting the Old Drive Anyway
If the PC still starts the HDD copy after you set the order, work through these in sequence — one of them is always the answer.
Identical names in the boot list: two entries both called Windows Boot Manager. Disconnect the HDD, boot the SSD once alone (which re-registers it as the working entry), then reconnect and re-check the order.
Fast Startup masking: the old Windows was hibernated, not shut down, so its session keeps resuming. Boot the SSD copy, disable Fast Startup in the old installation later — or simply wipe the old Windows partitions once the proof week ends, which removes the rival entirely.
Cable swap changed port priority: on some boards the lowest-numbered SATA port wins ties. Put the SSD on the port the HDD originally used.
You are actually booting the SSD already: doubt is not data — run the Disk Management proof before changing anything else.
🔴 Do not conclude the clone failed because the PC feels slow. Feelings cannot tell two identical systems apart — the firmware can be booting the old disk while the SSD sits perfect and unused. Run the disconnected test and the Disk Management proof; they take three minutes and they never lie.
🎥 Watch the Complete Video Guide
The end of the video is this exact moment — the first boot from the new SSD. Watch the timing on screen so you know the difference you should feel on your own machine.
The PC says no bootable device with only the SSD connected. Is the clone dead?
Almost always it means the small EFI or System Reserved partition did not come across, so the SSD holds Windows but nothing that can start it. The fix is a full re-clone with every partition selected. Your old HDD is untouched — reconnect it and the PC works as before while you redo the clone properly.
Can I just delete the old Windows from the boot menu instead of opening the BIOS?
Tools inside Windows can edit boot entries, but while two live copies exist the firmware choice is the root of the matter. Setting the boot order in the BIOS settles it at the source. Once you wipe the old Windows partitions after the proof week, the duplicate entry problem disappears on its own.
Is it safe to boot the old HDD copy again after cloning?
Yes — nothing about cloning damages the source. Booting the old drive works exactly as it did. Just remember that from the moment the two copies diverge, files saved in one do not exist in the other. Keep the divergence window short and deliberate.
This guide is based on the Technical Anshu video on cloning an HDD to SSD with Macrium Reflect. Stuck on a step? Ask in the video comments — you will get an answer there 🙏