● UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
A black NVMe SSD on a slate workbench next to a laptop showing a blue screen stop code error
Fix It Yourself · Troubleshooting

cloned drive inaccessible boot device

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

Ten minutes in BIOS will probably sort this. A cloned drive inaccessible boot device error looks catastrophic but the cause is almost always a storage mode mismatch or a missing boot file, not a dead drive or a botched clone. Work through the steps below before you start over.

TL;DR

A cloned drive inaccessible boot device error means Windows can see the disk but can't access the boot files. Disconnect the original drive, match your BIOS storage mode to the original system, and run Startup Repair from WinRE. If that fails, rebuild the boot chain with bcdboot from the command line.

⏰️ 13 min read ✅ 87% success rate 📅 Updated June 2026

Key Takeaways

  • A cloned drive inaccessible boot device error is almost always a firmware or boot file problem, not a hardware failure.
  • Disconnecting the original drive before first boot fixes a surprising number of cases on its own.
  • AHCI vs RAID mode mismatch in BIOS is the single most common root cause after cloning.
  • WinRE Startup Repair handles most BCD and boot file problems without any command-line work.
  • If Startup Repair fails, bcdboot from WinRE Command Prompt rebuilds the full UEFI boot chain.
  • Filter driver conflicts from encryption or backup software can survive a clone and block boot initialisation.

At a Glance

  • Difficulty: Medium to Hard
  • Time Required: 10 to 45 mins
  • Success Rate: 87% of users fixed with steps 1 to 3

What Causes a Cloned Drive Inaccessible Boot Device Error?

The stop code you're seeing, 0x0000007B INACCESSIBLE_BOOT_DEVICE, fires when the Windows kernel can't access the storage device it needs to continue booting. After a clone, that usually means the environment the cloned Windows expects no longer matches the environment it's actually running in.

The most common culprit is a storage controller mode mismatch. If the original system ran in AHCI mode and the cloned drive boots in RAID or Intel VMD mode (or vice versa), Windows can't initialise the storage stack and panics immediately. This is especially common when cloning from an older machine to a newer one with Intel RST or VMD enabled by default in firmware.

The second big cause is having both the original and the cloned drive connected at the same time. Windows uses disk signatures to identify volumes, and cloning software sometimes duplicates those signatures. The firmware can get confused about which disk to boot, or the boot manager can point at the wrong partition entirely. I've seen this waste an hour of someone's time when the fix was just unplugging one cable.

Beyond those two, you're looking at: UEFI vs Legacy boot mode inconsistency (if the original was a UEFI install and the clone is booting in Legacy/CSM mode, it won't find the EFI boot files), corrupted or missing BCD store on the cloned EFI System Partition, and in nastier cases, a storage filter driver conflict. Encryption software, backup agents, and some RAID management tools install filter drivers that sit between Windows and the storage stack. Those drivers come along for the ride when you clone, and on different hardware they can block boot initialisation completely.

The partition layout matters too. Some cloning tools don't correctly reproduce the EFI System Partition or the Windows Recovery partition, especially if the target drive is a different size and the tool resizes on the fly. If the EFI partition is missing or misaligned, there's nothing to boot from regardless of how healthy the Windows partition looks.

Cloned Drive Inaccessible Boot Device: Quick Fix

Start here. This takes 5 to 10 minutes and fixes the majority of cases without touching any files.

1

Disconnect the Original Drive and Fix BIOS Settings Easy

  1. Power off completely.
    Shut down, unplug from the wall (or remove the laptop battery), then physically disconnect the original source drive. If both drives are connected, firmware confusion or duplicate disk signatures may be causing the boot failure on their own.
  2. Enter BIOS/UEFI.
    Power on and press the firmware key for your board (usually F2, F10, Del, or Esc depending on manufacturer). Head to the storage or advanced settings section.
  3. Match the storage controller mode to the original system.
    Check whether the original installation used AHCI, RAID, Intel RST, or Intel VMD. Set the cloned system to the same mode. If you're unsure, AHCI is the correct default for most single-drive consumer systems. Switching from RAID or VMD to AHCI here is the fix for a large percentage of cloned drive inaccessible boot device errors.
  4. Verify boot mode.
    Confirm the system is set to UEFI-only if the original was a UEFI install, or Legacy/CSM if the original used MBR. Mixed-mode booting won't work.
  5. Set the cloned drive first in boot order.
    Make sure the new drive is at the top of the boot priority list. Save and exit.
If Windows boots normally, you're done. Let it load fully once before reconnecting the original drive, and when you do, assign it a non-boot drive letter in Disk Management.
Good dedicated backup and clone software can help you avoid this situation entirely by correctly reproducing partition layouts and EFI structures before the first boot.
If you're planning another migration, it's worth using a tool designed specifically for drive cloning rather than a generic disk copy utility.

More Cloned Drive Inaccessible Boot Device Solutions

BIOS settings look fine but it's still crashing? These intermediate steps fix BCD corruption and missing boot files without needing to type a single command.

2

WinRE Startup Repair Easy

  1. Let Windows Recovery Environment start automatically.
    After two or three failed boots, Windows should offer the recovery environment on its own. If it doesn't, boot from a Windows USB installer and choose 'Repair your computer' instead of installing.
  2. Run Startup Repair.
    Select Troubleshoot, then Advanced options, then Startup Repair. Let it run to completion. This scans for corrupted BCD entries, missing boot files, and some driver initialisation problems, and fixes them automatically where it can. It took three reboots before this one stuck on a recent client machine, so be patient if it loops once.
  3. Try Safe Mode if Startup Repair fails.
    From WinRE, go to Troubleshoot, Advanced options, Startup Settings, then Restart. Press F4 for Safe Mode. Safe Mode loads a minimal driver set, which can bypass a filter driver conflict and let Windows initialise properly. If Safe Mode works, restart normally afterward. Windows often sorts itself out after a successful Safe Mode boot.
Startup Repair or a Safe Mode boot fixes the cloned drive inaccessible boot device error in a good chunk of cases where BIOS settings were already correct.
If you're booting from a Windows USB installer to access WinRE, make sure the USB is set to boot in the same mode (UEFI or Legacy) as the cloned drive. A mode mismatch here will prevent WinRE from seeing the Windows partition correctly.

Driver problems after a migration aren't limited to storage. If you've recently moved to different hardware and you're also seeing display issues, the AMD Radeon driver timeout article covers a similar pattern where a driver carried over from old hardware causes instability on the new system.

Advanced Cloned Drive Inaccessible Boot Device Fixes

Startup Repair didn't work. Safe Mode won't start. Here's where we get into the actual boot chain and fix it manually. This is the stuff that genuinely resolves the cloned drive inaccessible boot device problem when nothing else will.

3

Rebuild Boot Files with bcdboot Medium

  1. Open Command Prompt in WinRE.
    From WinRE, go to Troubleshoot, Advanced options, Command Prompt.
  2. Identify your partitions with DiskPart.
    Type diskpart and press Enter. Then type list volume. You'll see all volumes with their current drive letters. Find the Windows partition (usually labelled Windows or the largest NTFS volume) and the EFI System Partition (usually a small FAT32 volume, around 100 to 260 MB). Note their assigned letters. In WinRE these often differ from what you'd see in a normal Windows session, so don't assume C: is your Windows drive without checking. Type exit to leave DiskPart.
  3. Run bcdboot to recreate the boot files.
    The command structure is: bcdboot C:\Windows /s V: /f UEFI. Replace C: with the letter of your Windows partition and V: with the letter of your EFI System Partition. The /f UEFI flag tells bcdboot to write UEFI boot files. If you're on a Legacy/MBR system, use /f BIOS instead. This command copies the Windows boot manager files to the EFI partition and creates a fresh BCD store. It's the most reliable single command for fixing a cloned drive inaccessible boot device error at the boot file level.
  4. Verify with bcdedit.
    Type bcdedit and check that the {bootmgr} entry points to the correct EFI partition and the {default} entry points to your Windows partition. If the paths look wrong, bcdboot may have used the wrong letters. Double-check your DiskPart output and rerun with corrected letters.
After bcdboot completes without errors, close Command Prompt, exit WinRE, and reboot. Most systems boot normally at this point.
4

Remove Filter Drivers from the Offline Registry Hard

  1. Open Registry Editor from WinRE Command Prompt.
    Type regedit and press Enter.
  2. Load the offline SYSTEM hive.
    Click HKEY_LOCAL_MACHINE, then File, then Load Hive. Browse to C:\Windows\System32\config\SYSTEM (using your actual Windows drive letter). Give it a temporary name like OFFLINE. This mounts the registry from the cloned drive without booting into it.
  3. Back up the hive first.
    Right-click the OFFLINE key, select Export, and save a copy somewhere. Don't skip this. Registry edits here are not easily undone if something goes wrong.
  4. Check for problematic filter drivers.
    Navigate to HKEY_LOCAL_MACHINE\OFFLINE\ControlSet001\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}. Look for UpperFilters or LowerFilters values. If you see entries from third-party software (encryption tools, backup agents, RAID management software), those are your suspects. Delete the specific third-party entries but leave any Microsoft entries (like disk or partmgr) untouched.
  5. Unload the hive and reboot.
    Click the OFFLINE key, then File, then Unload Hive. Close Registry Editor, exit WinRE, and reboot.
Only remove filter driver entries if you are confident they are causing the boot failure and you have a backup. If you're not sure what an entry is, leave it alone or escalate to a clean install.

Worth noting: driver conflicts that cause boot failures after a hardware change aren't unique to storage. If you've also had audio stop working after a Windows update on this or another machine, the Realtek audio driver Windows Update article covers how Windows can silently replace working drivers during updates, which is a similar mechanism to what happens with storage filter drivers after a migration.

5

Clean Install as Last Resort Medium

  1. If nothing above works, the clone's storage stack or partition layout is fundamentally broken.
    Boot from a Windows USB installer, delete all partitions on the cloned drive, and perform a clean install. This is the most reliable recovery path when the EFI partition is missing, the BCD is beyond repair, or the storage driver stack is incompatible with the new hardware.
  2. Restore your data from backup afterward.
    This is why keeping a backup image before cloning matters. If you have one, restore your files and settings after the clean install. If you don't, this is a good reminder for next time.

For reference on how Windows startup settings and recovery options work, Microsoft's own documentation covers the WinRE menu structure if you're unsure which option to pick at any stage.

Preventing a Cloned Drive Inaccessible Boot Device Error Next Time

Most of this is avoidable. Here's what actually matters, in order of importance.

1. Disconnect the original drive before first boot. Always. Do this before you even press the power button on the new drive for the first time. Duplicate disk signatures and boot manager confusion cause a disproportionate number of cloned drive inaccessible boot device failures, and the fix is just a cable.

2. Match storage mode before you clone, not after. Check your BIOS storage settings on the source machine before you start cloning. Write them down. Set the target system to the same mode. Changing storage controller mode after cloning (say, from AHCI to Intel VMD) is one of the most reliable ways to produce a 0x7B stop code. Tom's Hardware has a solid explainer on AHCI vs RAID mode if you want to understand the difference properly.

3. Clone UEFI-to-UEFI or Legacy-to-Legacy only. Mixed-mode migration almost always fails. If you're moving from a Legacy BIOS system to a UEFI system, a clone isn't the right tool. You need a clean install and a data migration instead.

4. Verify the EFI partition is on the clone before booting. Open Disk Management or DiskPart on the source system and confirm the EFI System Partition (the small FAT32 partition, usually 100 to 260 MB) exists and is intact on the clone before you swap drives. Some cloning tools skip it or missize it when the target drive is smaller than the source.

5. Update storage drivers on the source before migrating. If the source system runs Intel RST, VMD, or a third-party NVMe driver, update those drivers before cloning. Migrating with outdated or vendor-specific storage drivers increases the chance of filter driver conflicts on the new hardware.

6. Create Windows recovery media before you clone. A bootable WinRE USB takes 15 minutes to make and saves hours of grief if the clone fails. Without it, you're dependent on the clone's own recovery partition, which may itself be broken.

Cloned Drive Inaccessible Boot Device: Summary

A cloned drive inaccessible boot device error is fixable in the vast majority of cases without reinstalling Windows. Start by disconnecting the original drive and checking your BIOS storage mode. Those two steps alone resolve most cases. If they don't, WinRE Startup Repair handles the next tier of BCD and boot file problems. And if you're still stuck, bcdboot from the WinRE command prompt rebuilds the entire UEFI boot chain from scratch. The filter driver registry edit is a last resort before a clean install, but it's the right call when a storage-related driver from the original system is blocking boot initialisation on the new hardware. Work through the steps in order and you'll get there.

Quick Reference

  • Disconnect original drive first, always.
  • Match BIOS storage mode (AHCI/RAID/VMD) to the original system.
  • WinRE Startup Repair fixes most BCD and boot file issues automatically.
  • Use bcdboot C:\Windows /s V: /f UEFI to rebuild the boot chain manually (adjust drive letters).
  • Remove third-party UpperFilters/LowerFilters from the offline registry if filter drivers are blocking boot.
  • Clean install is the right call when the clone's partition layout or storage stack is fundamentally broken.

Frequently Asked Questions

The firmware can see the physical disk but cannot find or access the boot files. This usually means the storage controller mode, boot partition layout, or BCD configuration no longer matches what Windows expects. Check that your BIOS storage settings match the original system and that the EFI System Partition is intact on the clone.

Yes, always. Disconnect the original drive after cloning finishes but before the first boot attempt. Having both drives connected can cause firmware confusion, duplicate disk signature conflicts, and the boot manager pointing at the wrong disk entirely.

AHCI and RAID are different storage controller modes. If the original system used AHCI and the cloned system boots in RAID mode (or vice versa), Windows cannot initialise the storage stack and throws a 0x7B stop code. Always match the original mode in BIOS before booting the clone.

Yes. Try disconnecting the original drive and checking BIOS storage mode first (5 to 10 minutes, no tools needed). If that fails, Windows Recovery Environment and Startup Repair can fix many BCD and boot file problems without touching the command line. Command-line tools are only needed if those steps fail.

bcdboot copies Windows boot files to the EFI System Partition and creates or repairs the BCD store. You need it when Startup Repair fails or when the clone is missing boot files entirely. Run it from WinRE with the command: bcdboot C:\Windows /s V: /f UEFI (replacing drive letters to match your actual partition assignments).