INACCESSIBLE_BOOT_DEVICE Blue Screen
INACCESSIBLE_BOOT_DEVICE (stop code 0x7B) means Windows lost access to the drive it starts from while it was loading. Common causes are a changed BIOS storage setting, a new drive or controller, a failed update, file system errors or a failing drive. Unplug extra drives, then try Safe Mode once, Startup Repair and uninstalling the latest update.
Try these quick fixes first
- Unplug external drives, USB flash drives and memory cards, then restart.
- Ask whether anyone changed BIOS settings or updated the BIOS just before this started.
- After two failed starts, Windows opens Automatic Repair. Select Advanced options to reach the fixes below.
- If you see a BitLocker recovery screen, don’t guess. Call IT.
- If the computer starts again, restart it once more to make sure the fix holds.
What does INACCESSIBLE_BOOT_DEVICE mean?
Microsoft says this error means Windows lost access to its system partition during startup, so it always appears while the computer is starting.
- Note whether it happens at every start or only some.
- Note what changed just before: a Windows update, a BIOS update or setting change, a new or replaced drive, or repair work on the computer.
- If Windows shows a BitLocker recovery screen, write down the recovery key ID it shows and call IT.
- If the computer was just set up or reimaged, call IT. Microsoft notes that some disk controllers need extra drivers when Windows starts.
On Windows 11, version 24H2 and later, the screen is black instead of blue. Our blue screen of death guide explains both versions.
Unplug extra drives and undo hardware changes
Microsoft’s first fix for this stop code is to remove recently added hardware, especially drives and disk controllers.
- Shut down the computer.
- Unplug external drives, USB flash drives, memory cards and anything else you connected recently.
- Start the computer.
- If Windows loads, reconnect devices one at a time. If one brings the error back, stop using it and tell IT.
- If someone added or replaced a drive inside the computer, ask IT to check it. Microsoft notes that a drive’s firmware can be incompatible with your version of Windows.
Did someone change the BIOS?
Changing the storage controller mode in the BIOS (UEFI settings), such as switching it to AHCI, can cause this error, and Microsoft’s fix is to change it back.
- Ask whether anyone changed BIOS settings or updated the BIOS just before the error started.
- If so, call IT. Changing BIOS settings on a work computer is their job, and the fix is to put the setting back the way it was.
- Don’t try other BIOS settings to see what works. Some BIOS changes also make Windows ask for the BitLocker recovery key.
- IT can also check the PC maker’s website for a newer BIOS and storage controller firmware.
Start in Safe Mode, then restart normally
Microsoft says Safe Mode loads a core set of storage drivers that can let Windows reach the drive again, so starting it once can get the next normal start working.
- On the Automatic Repair screen, select Advanced options. If it doesn’t appear, hold the power button as soon as the logo appears until the computer turns off. Do this twice; on the third start, Automatic Repair appears.
- On the Choose an option screen, select Troubleshoot > Advanced options > Startup Settings > Restart.
- If Windows asks for a BitLocker recovery key, stop and call IT.
- Press 4 or F4 to start in Safe Mode.
- When Safe Mode loads, select Start > Power > Restart to start Windows normally.
Run Startup Repair
Startup Repair, part of the Windows Recovery Environment (WinRE), looks for damaged system files, corrupted boot configuration data and incompatible drivers that stop Windows from loading, and fixes what it can.
- From Automatic Repair, select Advanced options > Troubleshoot > Advanced options > Startup Repair.
- Follow the prompts and let it finish. The computer may restart.
- If it reports that it couldn’t repair the computer, take a photo of the details for IT and try the next fix.
Uninstall the latest update
In unusual cases, Microsoft says, an update that Windows couldn’t finish installing causes this error, and the recovery screen can remove the latest update without touching your files.
- From Automatic Repair, select Advanced options > Troubleshoot > Advanced options > Uninstall Updates.
- Select Uninstall latest quality update and follow the prompts.
- If the error began right after an upgrade to a new Windows version, ask IT before removing anything.
- If Windows starts, tell IT which update you removed so they can hold it back on other computers. If Windows says “We removed some recently installed updates,” it did this for you and blocks those updates for 30 days.
Use System Restore
Microsoft’s fixes for this stop code include System Restore, which rolls back drivers, updates and settings to a restore point and keeps your personal files.
- From Automatic Repair, select Advanced options > Troubleshoot > Advanced options > System Restore.
- Choose a restore point from before the error started. Select Show more restore points if you need older ones.
- Select Scan for affected programs, then Next > Finish.
- If no restore points are listed, call IT. Don’t select Reset this PC or Point-in-time restore on a work computer. Those can remove apps or recent files.
Ask IT to check the drive and boot files
The remaining fixes use the recovery Command Prompt and can change boot files, so they’re for IT, and they start by making sure the drive still works.
- IT confirms Windows can still see the drive. If it can’t, the drive or its connection may have failed, and getting your files back comes first.
- IT checks the file system with
chkdsk /f /rand can run System File Checker offline. - IT checks the boot configuration data and can undo an update that is stuck pending.
- IT looks for missing or misbehaving storage drivers and filter drivers, and updates the BIOS, storage firmware and drivers.
- If the drive has failed and your files weren’t backed up, ask IT about data recovery before anyone replaces or wipes it.
Why does this happen?
Microsoft lists these causes:
- A storage driver or filter driver that’s missing, damaged or misbehaving.
- File system corruption, or damaged files in the boot partition.
- A change to the storage controller mode or other storage settings in the BIOS.
- A different storage controller than the one Windows was installed with, or a drive moved to another computer.
- A faulty drive, storage controller or motherboard.
- In unusual cases, an update that Windows couldn’t finish installing.
When should you call IT?
- Windows asks for a BitLocker recovery key. Note the key ID on the screen. On a company computer, the key is normally backed up to your organization’s Microsoft Entra ID or Active Directory, where IT can look it up.
- The error is back after Safe Mode, Startup Repair and uninstalling the latest update.
- Someone changed or updated the BIOS.
- The drive isn’t detected, or Windows warned about the drive’s health before this started.
- You need files from the computer that aren’t backed up.
- A recovery screen offers to reset or reinstall Windows.
If the drive has failed and files weren’t backed up, read about our data recovery service.
OAC Technology’s IT support team fixes problems like this for businesses across the Twin Cities. Clients can call 952-548-5558, Monday to Friday, 8 a.m. to 6 p.m. Central. Not a client yet? Call the same number or send us a message.
Common questions
What does inaccessible boot device mean?
It means Windows lost access to its system partition while starting up, so it can’t finish loading. Microsoft’s code for this stop error is 0x7B.
How do I fix INACCESSIBLE_BOOT_DEVICE on Windows 11?
Remove recently added drives and undo BIOS changes, then from the recovery screen try Safe Mode once, Startup Repair, Uninstall Updates and System Restore, in that order. If none of them works, IT checks the drive and boot files.
Will I lose my files?
Not because of the error itself, and the fixes in this guide keep your personal files. If the drive is failing, though, have IT copy your files off before anyone tries more repairs.
Can a Windows update cause INACCESSIBLE_BOOT_DEVICE?
Yes, occasionally. Microsoft lists an update that couldn’t finish installing as an unusual cause, so remove the latest update from the recovery screen, and if that doesn’t work, IT can undo a pending update from the command line.
How do I get past a “Boot device not found” error?
It means the computer can’t find a drive to start Windows from, a different problem from the INACCESSIBLE_BOOT_DEVICE stop code (error 3F0 on HP computers). Unplug USB drives and other devices and restart, then run your maker’s drive test: on an HP, press Esc repeatedly as it starts, then F2, and choose “Symptom Tests”; on a Dell, press F12 and choose “Diagnostics”. Your IT team can check the drive and BIOS settings.









