Confirm the drive before running boot commands
Do not initialise, format or repartition the system drive when recovery cannot see Windows. Do not change AHCI, RAID, VMD or storage-controller mode by guesswork. If BitLocker appears, obtain the correct recovery key before repairs. Back up accessible data before disk or boot-configuration work.
First determine whether the system drive is detected
| Observation | Likely direction |
|---|---|
| Drive missing in BIOS/UEFI | Connection, SSD, controller, firmware or hardware failure. |
| Drive visible in BIOS but not recovery | Storage driver, VMD/RAID mode, encryption or severe disk trouble. |
| Error started after Windows update | Update rollback, storage driver or servicing failure. |
| Error started after BIOS reset/change | Storage-controller mode no longer matches the installed configuration. |
| Recovery sees Windows and files | Software repair and update recovery are reasonable. |
1. Check BIOS/UEFI detection without changing settings
Open the manufacturer’s firmware interface and confirm whether the SSD or Windows Boot Manager appears. Photograph the storage and boot settings before touching them.
If the drive is absent, power the device off and follow the manufacturer’s storage diagnostics or service instructions. Repeated software commands cannot communicate with undetected hardware.
2. Restore the previously working storage mode
If the error began immediately after a BIOS update, reset or manual change, compare the current AHCI, RAID, VMD or controller setting with the documented previous configuration. Restore only the known working setting.
Do not cycle through modes experimentally. Changing modes can create new boot failures and may affect encrypted or managed systems.
3. Open Windows Recovery Environment
Use automatic recovery or official Windows 11 installation media and choose Repair your computer → Troubleshoot → Advanced options. Startup Repair can be attempted once. If it cannot see Windows or repeats the same failure, continue with targeted checks.
4. Remove the update that triggered the failure
Select Uninstall Updates → Uninstall latest quality update when the timing matches. Use feature-update rollback only after a version upgrade and when recovery offers it. System Restore is another option when a suitable point exists.
Record any removal failure rather than repeatedly forcing the same action.
5. Handle storage drivers carefully
Systems using Intel VMD/RST, AMD RAID or vendor storage controllers may need the matching driver before recovery or installation media can see the disk. Obtain the exact package from the PC or motherboard manufacturer.
Do not install a generic driver because its name looks similar. Model, controller mode and Windows version must match.
6. Identify Windows and BitLocker state
In recovery Command Prompt use diskpart and list volume only to identify volumes, then enter exit. Recovery drive letters may differ from normal Windows.
If a volume is BitLocker-locked, unlock it with the correct recovery key before expecting file or offline repair tools to read Windows. Never publish the key.
7. Check the file system after confirming the volume
When the correct Windows letter is known and data is backed up, begin with the least disruptive supported disk check. Avoid aggressive repair switches on a drive that disappears, freezes, makes unusual sounds or holds the only copy of important data.
Use the SSD manufacturer’s health diagnostic whenever recovery allows it.
8. Repair boot files only when the drive and Windows are readable
Modern Windows 11 systems normally use UEFI and an EFI System Partition. Boot repair must match that layout. Confirm the Windows volume, EFI partition and firmware mode before using bcdboot or related commands.
Do not format the EFI partition as a first attempt. Follow Microsoft or manufacturer guidance for the specific UEFI configuration.
9. Repair offline Windows files with confirmed paths
Offline SFC and DISM syntax requires the real Windows and boot paths visible in recovery. Do not assume Windows is C:. When the paths are uncertain, use System Restore, update removal or professional recovery instead of copying commands from another PC.
10. Recognise a failing SSD or controller
- The drive vanishes intermittently from BIOS.
- Recovery freezes while reading the disk.
- SMART or manufacturer diagnostics report failure.
- Files were corrupt or read-only before the blue screen.
- Installation cannot reliably detect or write to the drive.
Stop repeated repair attempts and prioritise professional data recovery when the files are irreplaceable.
11. Reinstall only after storage is stable
A clean installation erases the selected Windows partition and is appropriate only after backup and hardware checks. Installation failures, disappearing partitions or recurring 0x7B errors on a clean setup point to storage, controller, firmware or motherboard trouble.
Avoid these common mistakes
- Do not initialise or format a drive recovery cannot identify.
- Do not guess between AHCI, RAID or VMD modes.
- Do not run boot repair against unconfirmed partitions.
- Do not keep stressing a drive showing failure symptoms.
Frequently asked questions
What causes INACCESSIBLE_BOOT_DEVICE in Windows 11?
Common causes include a failed update, changed BIOS storage mode, missing storage driver, SSD or controller failure, file-system damage and boot configuration problems.
Why did it happen after changing AHCI or RAID mode?
Windows may not have the required boot-time driver enabled for the new controller mode. Return to the previously working documented setting.
Can Startup Repair fix this error?
It may help when startup files are damaged, but it cannot repair a drive that is missing, failing or controlled by an unavailable storage driver.
Technical steps align with Microsoft guidance for bug check 0x7B, Windows Recovery Environment, update removal, BitLocker, UEFI boot repair and manufacturer storage-controller practices.
Official references
For platform-specific behavior and recovery options, compare this guide with the current documentation from the relevant official source.