Windows · Windows Server · high · Recovery, imaging & repair

A cloned or imaged drive will not boot, or has the wrong drive letter

The clone is intact but the machine cannot start from it — usually a storage controller mode mismatch, or two disks claiming the same signature.

What you see

The cloned drive bluescreens with 0x7B, or Windows boots from the clone but the system drive has become D: and nothing works properly.

What is actually wrong

A disk signature collision when both the source and the clone are attached, a storage controller mode the cloned Windows has no driver for, or the boot configuration still pointing at the original disk.

Codes and articles

0x0000007B cloneINACCESSIBLE_BOOT_DEVICEdrive letter changedMountedDevicessignature collision

Fixes (2)

Boot with only one of the two disks attached

The machine20 minuteslow riskreversible

Both disks are present. This is the first thing to try and it resolves most of these.

Disconnect the original drive entirely and boot from the clone alone.
Two disks with the same signature is an ambiguous state, and Windows resolves it by taking one offline — often the one you are trying to boot from. Removing the doubt is faster than any repair.
Once it boots cleanly, shut down and reconnect the original as a secondary disk. Windows will assign it a new signature and letters.

Confirm the letters are as expected.

PowerShell

Get-Partition | Format-Table DiskNumber,PartitionNumber,DriveLetter,Size,TypeGet-Disk | Format-Table Number,FriendlyName,Signature,IsOffline,IsBoot,IsSystem

If the system drive has become the wrong letter, fix it in the registry from a second install or WinRE rather than in Disk Management, which will refuse to change the boot volume.

Confirm it workedThe machine boots with C: as the system drive.

PowerShell

Get-Volume | Format-Table DriveLetter,FileSystemLabel,FileSystemType,Size

If you need to undo itReconnecting drives is not destructive.

Give the clone the storage driver it needs

WinRE, or the firmware45 minutesmedium riskreversible

0x7B on the clone, particularly when moving between machines or from SATA to NVMe.

Check the firmware's storage mode first — switching between AHCI, RAID and Intel VMD is the usual cause and switching it back is free.
Windows only loads the storage driver it was installed with. A machine moved from AHCI to RAID has no driver for the controller it now has, and it stops at 0x7B before anything can be logged.
If the mode must change, pre-enable the driver before switching. From a working boot, put Windows into safe mode once so it loads the alternative drivers.
Command Prompt
```
bcdedit /set {current} safeboot minimalshutdown /r /t 0
```
Change the firmware mode while it is in safe mode, boot once, then remove the flag.
Command Prompt
```
bcdedit /deletevalue {current} safebootshutdown /r /t 0
```
If the machine is already at 0x7B, inject the storage driver offline from WinRE.
Command Prompt
```
DISM /Image:D:\ /Add-Driver /Driver:E:\storagedriver\iaStorVD.inf
```
For a clone moving to different hardware entirely, run sysprep generalize on the source before imaging, which removes the hardware-specific configuration.

Confirm it workedThe clone boots and the storage controller appears correctly in Device Manager.

PowerShell

Get-PnpDevice -Class SCSIAdapter | Format-Table Status,FriendlyName

If you need to undo itFirmware modes can be switched back; always clear the safeboot flag.

Where this stops. This write-up was written and checked by hand. It says what each step changes, how to confirm it worked and how to reverse it, and anything destructive is flagged before you reach it. If it does not match what your machine is doing, search the Support Centre for the exact code or message — and when something needs a person, get in touch.