Diagnostic guide
'INACCESSIBLE_BOOT_DEVICE' After a Windows Update – Is Your Data Safe?
Symptom
Windows shows a blue screen with INACCESSIBLE_BOOT_DEVICE (stop code 0x7B) at startup and restarts or loops into recovery.
Microsoft describes this bug check as Windows losing access to the system partition during startup. Documented causes include boot-device driver problems, file-system recognition problems, storage hardware failure, and changes such as a BIOS/UEFI update, a controller mode change or moving a disk to a different controller. Most of these leave your files untouched. The danger is in the shortcuts: switching storage modes at random, running bootrec on a failing disk, or reinstalling over the old partition.
Do not
STOP - Change One Thing, and Only a Reversible One
- Do not toggle AHCI, RAID or Intel VMD modes at random in the BIOS
- Do not run bootrec /fixmbr or fixboot on a drive that may be failing
- Do not clean-install Windows over the old partition
- Do not delete or recreate partitions
- Do not keep forcing power-offs if the drive is making noise
Why this matters: Switching storage mode is reversible; reinstalling is not. If the drive itself is failing, repair tools that write to it can make the situation worse. Protect the files first, then fix Windows.
Cause
Most Likely Causes
- 01
Storage Controller Mode or Driver Change
High LikelihoodA BIOS update or setting changed AHCI, RAID or VMD mode, or the needed storage driver is not loaded at boot.
- 02
Pending or Failed Update
High LikelihoodMicrosoft's troubleshooting lists reverting pending update actions as a step, which shows an update can leave boot components inconsistent.
- 03
Disk Cloned or Moved to Different Hardware
Medium LikelihoodA cloned system disk placed on a different controller may lack the right driver at boot.
- 04
Failing Drive or File System Damage
Medium LikelihoodThe system partition cannot be read reliably, which Microsoft lists among the causes.
What to do
Safe Diagnostic Checks
These checks are non-destructive and safe to perform. Follow them exactly as written.
Undo recent changes first
- 01If you changed any BIOS/UEFI setting recently, put it back to what it was
- 02Disconnect USB drives and other extra storage and try again
- 03Note whether the drive is detected in the BIOS/UEFI and with the right size
- 04Photograph the stop code and any additional information shown
Use Windows Recovery Environment carefully
- 01From the recovery screen choose Troubleshoot > Advanced options
- 02Try 'Uninstall Updates' if it is offered; Microsoft lists reverting a recent update as a documented step
- 03If asked for a BitLocker recovery key, find it at aka.ms/myrecoverykey rather than guessing
Do not choose Reset this PC. If the drive makes noise or disappears, stop.
Escalate
When Professional Recovery Is Required
You should seek professional data recovery if any of these apply:
- The drive is not detected in BIOS/UEFI or shows the wrong size
- The drive clicks or the PC freezes before the blue screen
- Recovery tools fail and the files are not backed up
- BitLocker encryption is on and you do not have the key
- A reset, reinstall or boot repair was already attempted
Process
Our Recovery Process
- Turnaround Time
- 2-5 business days
- Success Rate
- Assessed in the free evaluation; depends on the damage
What happens when you bring your drive to us:
- 01Free evaluation: drive health first, then controller and boot configuration
- 02Image the system drive before any boot repair
- 03Extract your user data from the image
- 04Where needed, restore booting on a fresh drive rather than the old one
- 05Verify your files open
- 06Return the data on new media
FAQ
Frequently Asked Questions
Related
Related Guides
- 01
Stuck in 'Preparing Automatic Repair' – Getting Your Files Out Before You Reset
The PC shows 'Preparing Automatic Repair' or 'Automatic Repair couldn't repair your PC' and restarts again and again without reaching the desktop. - 02
Windows Update Triggered a BitLocker Recovery Screen – Finding the Key and Staying Out of a Reset
After an update or restart the PC stops at a blue screen asking for a BitLocker recovery key you do not remember ever seeing. - 03
NVMe Drive Not Detected in BIOS After Crash
Your NVMe SSD is no longer detected in BIOS or the operating system after a crash or sudden event.
Background reading
Free diagnosis
Need Professional Data Recovery?
Free Diagnosis • No Recovery, No Charge
Our certified technicians have recovered thousands of drives with these exact symptoms. Get your free evaluation today.
- 97% Success Rate
- Across all device types
- ISO-5 Cleanroom
- Class 100 certified facility
- 24/7 Emergency
- Available for critical cases