● UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
Two SSDs side by side on a clean desk showing Windows Disk Management with drive letters C and E assigned after a clone operation
Fix It Yourself · Troubleshooting

change drive letter after cloning

Updated 24 July 202613 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

After cloning your old SSD to a new one, you'd expect the new drive to show up as C: and just work. Instead you're looking at E: or F: in File Explorer, and every attempt to change drive letter after cloning in Disk Management hits a wall. Here's the thing: the drive letter isn't the actual problem. Your computer is still booting from the old SSD, and until you fix that, no amount of clicking in Disk Management will help.

TL;DR

To change drive letter after cloning, you don't rename the drive. You make Windows boot from the new SSD instead. Either physically remove the old SSD before first boot, or change the BIOS boot order to put the new drive first. Windows then assigns C: automatically. Disk Management cannot change a system drive letter by design.

⏱️ 13 min read ✅ 90% success rate 📅 Updated July 2026

Key Takeaways

  • Windows assigns C: to whichever disk it boots from. You cannot override this manually in Disk Management.
  • The fix for change drive letter after cloning is always about boot order, not renaming.
  • Physically removing the old SSD before first boot is the most reliable method.
  • Changing BIOS boot order works just as well if you want to keep both drives connected.
  • Only delete partitions on the old SSD after you have confirmed the new one boots correctly.
  • If the clone won't boot at all, bcdboot from Windows Recovery can rebuild the boot configuration.

At a Glance

  • Difficulty: Easy to Medium
  • Time Required: 15 to 30 mins
  • Success Rate: 90% of users sorted with BIOS or physical swap

What Actually Causes This After Cloning?

When you clone a drive using backup clone software like Macrium Reflect, the tool copies every partition exactly as it is onto the new SSD. The data transfer itself almost certainly worked fine. But cloning the data is only half the job. The other half is telling your computer's firmware (BIOS or UEFI) to actually start Windows from the new disk instead of the old one. Most guides skip over this, which is why so many people end up confused.

Here's what's happening under the hood. When Windows starts up, it reads the boot configuration from whichever disk the firmware hands control to. That disk gets assigned C:. Every other disk connected to the system gets a different letter, typically D:, E:, F: and so on, assigned in order of how Windows discovers them. So if your old SSD is still the first boot device, Windows boots from it, calls it C:, and your shiny new cloned SSD ends up as E: or F:. The clone is fine. The boot order is the problem.

The reason Disk Management won't let you change the letter to C: is deliberate. Windows locks the system drive letter because dozens of registry entries, application paths, and Windows system files all reference C:\ explicitly. If you could just rename it, everything would break instantly. Microsoft made this intentional, and it's actually the right call. The correct fix is to make Windows boot from the right disk in the first place, not to rename after the fact.

There are a few specific scenarios that lead here. The most common: both SSDs are still plugged in and the BIOS boot order was never changed. Second most common: the user tried to change drive letter after cloning through Disk Management, hit the greyed-out option, and assumed something was broken with the clone. Third: the clone completed but the new SSD doesn't have a valid boot configuration at all, which is rarer but does happen if the cloning process was interrupted or if the tool didn't copy the EFI system partition correctly.

One thing worth checking before anything else: open Disk Management (press Win + X and select Disk Management from the menu) and look at the lower pane where the physical disks are shown. You'll see Disk 0, Disk 1, and so on. Look for which one has a partition labelled "System" or "Boot". That's the disk Windows is currently running from. If it's the old SSD, that confirms the boot order issue.

Change Drive Letter After Cloning: Quick Fix

This is the method I recommend to almost everyone who asks about this. It takes about five minutes of physical work and has a very high success rate because it removes all ambiguity. Windows can't get confused about which disk to boot from if there's only one disk present.

1

Physically Remove the Old SSD Easy

  1. Shut Windows down completely.
    Don't restart. A full shutdown. Start menu, Power, Shut down.
  2. Unplug the power cable from the back of your PC.
    If it's a laptop, remove the battery if accessible. You want zero power going to the board before you touch anything inside.
  3. Open the case and locate the old SSD.
    If it's an m2" class="vae-glossary-link" data-term="m2">M.2 drive (the small rectangular card), unscrew the single retaining screw, lift the card at a slight angle, and slide it out. If it's a 2.5-inch SATA drive, unplug the data cable and power cable, then unscrew it from the tray.
  4. Leave the new cloned SSD in place and close the case.
    Plug power back in and boot the PC normally.
  5. Watch the boot process.
    With only one drive present, BIOS will find the new SSD automatically and hand control to Windows. No BIOS changes needed.
  6. Verify in File Explorer.
    Once Windows loads, open File Explorer. Your Windows drive should now show as C:. Open Disk Management to confirm the system partition sits on the new SSD.
If File Explorer shows C: on the new SSD and Windows runs normally, you're sorted. You can reattach the old SSD later as a secondary storage drive.
When you do reattach the old SSD later, Windows will assign it a new letter (D:, E:, etc.) automatically. At that point you can open Disk Management, delete the old system partitions, and create a fresh volume for storage. Don't do this step until you're confident the new SSD is working properly.

If you're not comfortable opening your PC case, or if it's a laptop where the drive is soldered or awkward to reach, the BIOS boot order method below achieves the same result without any physical work.

More Change Drive Letter After Cloning Solutions

2

Change BIOS Boot Order Easy

  1. Restart your computer.
    As soon as the screen goes dark and the manufacturer logo appears, start tapping the BIOS entry key. This is usually F2, Del, F10, or F12 depending on your board. If you're not sure which key, check the startup screen itself. It often flashes "Press [key] to enter Setup" for a second or two. According to HowToGeek's BIOS guide, Dell typically uses F2, ASUS uses Del or F2, and HP uses F10 or Esc.
  2. Find the Boot settings section.
    BIOS interfaces vary a lot. Look for a tab or menu called Boot, Boot Order, or Boot Priority. On modern UEFI systems it's often on the main screen as a drag-and-drop list.
  3. Move the new SSD to the top of the boot order.
    Select the new SSD (identify it by model name or size) and move it above the old SSD. On most BIOS screens you use the + and - keys or F5/F6 to move items up and down. On UEFI graphical interfaces you can often just drag the drive to the top.
  4. Save and exit.
    Press F10 on most systems, or navigate to Save & Exit and confirm. The PC will restart.
  5. Let Windows boot and verify.
    Windows should now boot from the new SSD. Open File Explorer and confirm the system drive shows as C:. If it does, great. If it still shows the old letter, double-check in Disk Management which disk has the Boot and System flags.
Once confirmed, you can go into Disk Management, identify the old SSD, and delete its partitions to repurpose it as storage. Right-click each partition on the old drive, select Delete Volume, then create a New Simple Volume on the unallocated space.
Do not delete any partitions on the old SSD until you have booted from the new one at least two or three times and confirmed everything works. Applications open, files are accessible, Windows updates run. Only then is it safe to wipe the old drive.
3

Change Drive Letter for Non-System Drives in Disk Management Easy

  1. Press Win + R, type diskmgmt.msc, and press Enter.
    This opens Disk Management directly.
  2. In the lower pane, find the data volume you want to rename.
    This only works for drives that are NOT the current system drive (C:). If you want to rename a secondary data drive from F: to D:, this is the right tool.
  3. Right-click the volume and select Change Drive Letter and Paths.
    Click Change, pick a new unused letter from the dropdown, and click OK. Confirm the warning.
This method is for data drives only. It will not let you change the system drive letter to C:. For that, you need the BIOS boot order fix above.

One thing that catches people out: after you change the BIOS boot order and Windows boots from the new SSD as C:, the old SSD (still connected) might show up with a system-looking partition labelled as a different letter. That's fine. It's just the old Windows installation sitting there doing nothing. Once you delete those partitions and create a fresh volume, the old drive becomes a perfectly normal storage disk.

If you run into odd driver behaviour after the swap, like audio or network adapters acting up, that's usually unrelated to the drive letter change. Driver issues after hardware changes are a separate matter entirely. We've seen similar post-migration weirdness documented in our article on Realtek audio driver Windows Update problems, where a system change triggers a driver conflict. Worth checking if you hit audio issues after the swap.

Advanced Change Drive Letter After Cloning Fixes

This section is for one specific situation: you've changed the BIOS boot order, the new SSD is listed first, but Windows still won't boot from it. You get an error like "No bootable device found" or the system just loops back to the old drive. This means the clone either didn't copy the EFI system partition correctly, or the boot configuration data (BCD) on the new drive is pointing to the wrong place.

4

Rebuild Boot Files with bcdboot Advanced

  1. Create a Windows recovery USB if you don't have one.
    On a working PC, download the Windows 11 Media Creation Tool from Microsoft's site and create a bootable USB. Alternatively, if you have a Windows installation disc, that works too. Microsoft's own documentation on bcdboot syntax is worth reading before you start.
  2. Boot from the USB.
    Plug it in, restart, and press the boot device selection key (usually F11 or F12) to choose the USB. Select the USB from the menu.
  3. Open Command Prompt from recovery options.
    On the Windows Setup screen, click "Repair your computer" at the bottom left. Then go to Troubleshoot, Advanced options, Command Prompt.
  4. Identify your drives with diskpart.
    Type diskpart and press Enter. Then type list disk to see all connected disks. Note the disk number of your new SSD. Type list vol to see all volumes. Identify the volume containing your Windows installation on the new SSD (usually labelled Windows or has a large size) and note its drive letter as assigned in recovery (it might not be C: here, it could be D: or E:).
  5. Exit diskpart and run bcdboot.
    Type exit to leave diskpart. Then run: bcdboot D:\Windows /s Z: /f UEFI but replace D: with whatever letter your Windows partition was assigned in recovery, and Z: with the letter of your EFI system partition. If you're not sure which partition is EFI, look for a small (100MB to 500MB) FAT32 partition in the diskpart volume list. This command rebuilds the boot files so the firmware can find Windows on the new SSD.
  6. Restart without the USB and test.
    Remove the USB drive, restart, and let the system boot. If bcdboot worked, Windows should load from the new SSD and assign it C:.
Incorrect use of diskpart (particularly the clean or format commands) can wipe data instantly. Only use list disk, list vol, and exit commands unless you are certain what you are doing. If in doubt, get remote help.

The bcdboot route is genuinely not as scary as it looks once you've done it once. But I understand that for someone new to PCs, staring at a command prompt in recovery mode is a bit daunting. Took me three reboots the first time I did this on a client machine before I had the right partition letters sorted. It's one of those things where going slowly and reading each line before pressing Enter makes all the difference.

One thing I'd flag: if you're also seeing driver errors after the migration, like network adapters not working or Bluetooth going missing, those are separate issues that sometimes appear after a system drive swap. We've covered the ethernet controller driver missing Windows 11 problem in detail if that comes up for you. And if Bluetooth specifically goes dodgy, the Intel Bluetooth driver error 0x800705b4 article walks through the fix. Both are common post-migration gremlins.

Registry-level drive letter changes are sometimes mentioned in forums as a workaround. Don't do it. Microsoft explicitly advises against this, and in practice it breaks application paths and can make Windows unbootable. The BIOS and physical swap methods above are the correct approach every time.

Preventing Change Drive Letter After Cloning Problems

Most of the confusion around this comes from not planning the swap before starting the clone. Here's the order that works cleanly, every time.

First priority: decide before you clone whether you're going to physically remove the old SSD or change the BIOS boot order. Either works, but decide upfront. If you're physically swapping, the ideal workflow is: clone the drive with both SSDs connected, shut down, remove the old SSD, boot from the new one. Done. Windows sees one disk, assigns it C:, no drama.

If you want to keep both drives connected (common on desktops where you want to reuse the old SSD for storage), go into BIOS immediately after cloning and set the new SSD as the first boot device before you ever restart Windows. Don't let Windows boot with the old drive still first in the order, because once it does, it assigns letters and you're back to the same problem.

Second priority: always keep a Windows recovery USB around when doing drive migrations. It takes about 15 minutes to make one and it's saved me hours of work on client machines. If the boot configuration breaks for any reason, bcdboot from recovery sorts it in under 10 minutes once you know the right partition letters.

Third: label your drives. In BIOS and in Windows Disk Management, give your drives distinct volume names like OldOS and NewOS before you start. When you're staring at Disk 0 and Disk 1 in a recovery environment trying to figure out which is which, having a name is far more useful than guessing by size. You can rename a volume in Disk Management by right-clicking it and selecting Properties.

And finally: don't rush the cleanup. Once the new SSD is running as C:, leave the old drive alone for at least a few days. Boot several times, run your applications, check your files. Only when you're genuinely confident should you delete the old partitions. The old drive costs you nothing sitting there as a safety net.

Change Drive Letter After Cloning: Summary

The core issue with change drive letter after cloning is almost always a boot order problem, not a disk problem. Windows assigns C: automatically to the disk it boots from, and you cannot override that in Disk Management. The fix is either to physically remove the old SSD before first boot (cleanest method, very high success rate) or to change the BIOS boot order to put the new SSD first. Once Windows boots from the new drive, it assigns C: on its own. If the clone won't boot at all after changing the boot order, bcdboot from Windows Recovery rebuilds the boot configuration in a few commands. Follow the prevention steps above next time you do a migration and you'll avoid the whole situation entirely.

For independent reading on drive migration best practices, Microsoft's own backup and restore documentation covers the Windows side of things well, and is worth bookmarking for future reference.

Frequently Asked Questions

Windows automatically assigns C: to whichever disk it boots from. If your new SSD shows as E: or F:, your PC is still booting from the old SSD. Change your BIOS boot order to make the new SSD first, or physically remove the old SSD, and Windows will assign C: to the new drive automatically on next boot.

No. Windows intentionally blocks you from changing the letter of the active system drive. The only way to make your new SSD become C: is to actually boot from it. Fix your BIOS boot order or remove the old drive, and Windows handles the letter assignment automatically.

Yes, but only after you have booted from the new SSD several times and confirmed everything works. Run your applications, check your files, and be certain before you delete anything. Once you are happy, open Disk Management, right-click each partition on the old drive, and select Delete Volume.

Boot from a Windows installation or recovery USB, open Command Prompt from the Advanced options menu, and use diskpart to identify your drives followed by bcdboot to rebuild the boot files on the new SSD. If you are not comfortable with command-line tools, a technician can do this remotely in under 30 minutes.

Yes. Once the new SSD is booting correctly as C:, open Disk Management, delete all partitions on the old SSD, then create a new simple volume. Windows will assign it a letter like D: or E: and you can use it for storage. Just make sure the new SSD stays first in the BIOS boot order.