When Windows won't boot, the clock ticks and the pressure mounts; luckily, there are native tools to get everything up and running again without losing your cool. With bcdedit, bootrec, and the recovery environment itself (WinRE), we can diagnose and repair everything from MBR or boot sector errors to BCD corruption or boot manager problems.
Before you start typing commands haphazardly, it's important to understand where the process breaks down. The boot sequence has clear phases (BIOS/UEFI, Boot Manager, OS Loader, and Kernel) , and each one leaves different clues: black screens with a cursor, errors like "BOOTMGR is missing," messages about a corrupted BCD, or the dreaded "INACCESSIBLE_BOOT_DEVICE." This guide covers, from the simplest to the most complex, the methods that work best in Windows 7 , Windows 10, and Windows 11 when you need to get your hands dirty.
Start-up phases and what each symptom indicates
Understanding the basic workflow saves time. The pre-boot stage (POST) and the firmware (BIOS/UEFI) validate the hardware and locate the system disk. In BIOS, the MBR/PBR is read; in UEFI, the firmware executable is invoked.
- Phase 1 – Pre-boot (firmware)POST and disk detection. If the HDD light doesn't blink or Num Lock doesn't respond, the problem lies here and it's likely a hardware issue.
- Phase 2 – Boot ManagerBootmgr in BIOS (%SystemDrive%\bootmgr) or bootmgfw.efi in UEFI (\EFI\Microsoft\Boot\bootmgfw.efi). Typical errors: Missing/corrupted BCD, “Operating system missing”, “Bootmgr missing”.
- Phase 3 – Windows Loader (winload.exe/.efi)Essential drivers are loaded; if it fails, winload messages or BCD codes usually appear.
- Phase 4 – Kernel (ntoskrnl.exe)The system loads Registry subtrees and BOOT_START services. Screenshots like these are common here. 0x0000007B (INACCESSIBLE_BOOT_DEVICE) or blockages in the “rotating wheel”.
Depending on the symptom, we'll choose one approach or another. In the boot manager stage, bootrec and bcdedit are the best ; in the kernel stage, SFC/DISM and the Event Viewer from Safe Mode usually provide the definitive clue.
Enter WinRE and open the Command Prompt
To act quickly, the best approach is to access the recovery environment's command interpreter. In Windows 10/11, you can force WinRE by shutting down and restarting three times during the logo process until the "Recovery" screen appears.
- On the blue screen, tap on Advanced > Solve problems > Advanced.
- Choose Symbol of the system to open the console. From here we will launch bootrec, bcdedit, bcdboot and diskpart as required.
If you can't access WinRE that way, use a Windows installation USB/DVD. Boot from the media, choose your language, and click "Repair your computer" ; then follow the steps above to Command Prompt. If your computer still won't boot from USB/DVD, check the firmware for the boot order or the Boot Menu key (F12, Esc, etc.).
Bootrec.exe: what each option does and when to use it
Bootrec.exe is the emergency boot scalpel. Its four parameters cover the MBR, boot sector, and BCD store , and should be applied in a logical order.
- / FixMbr: rewrites a Windows-compatible MBR without touching the partition table. Useful for malware in the MBR or corruption of the master boot record.
- /FixBoot: creates a new boot sector. Key if the PBR is damaged or after installing an earlier version of Windows that left NTLDR as the bootloader.
- / ScanOs: Searches for Windows installations not listed in the BCD. Helps locate systems hidden from the boot menu.
- / RebuildBcd: scans and allows adding installations to the BCD. The option to completely rebuild the BCD when all else fails.
A typical sequence for a "Bootmgr is missing" or "BCD is corrupted" error is as follows. Run it from WinRE and confirm each step :
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
If `/RebuildBcd` doesn't resolve the issue or returns errors, it's time to back up the BCD, remove attributes, and force a clean rebuild. The exact commands are listed below in the BCD section.
Repair BCD errors with bcdedit and bcdboot
When the BCD store is corrupted or inconsistent, the reliable solution is to back it up, delete (or rename) it, and rebuild it . Note: In UEFI, the BCD resides on the EFI partition (FAT32); in BIOS, it's in the \Boot folder of the active partition.
First, identify the correct partition. In UEFI, the EFI (ESP) partition must be FAT32 and often does not have a drive letter.
diskpart
list disk
sel disk 0
list vol
sel vol <número de la partición EFI (FAT32)>
assign letter=Z:
exit
With the drive letter assigned, navigate to the Microsoft Boot directory and run the UEFI sector repair if necessary. This fixes the "Access is denied"/"Device not found" error in /FixBoot when the ESP is inaccessible.
cd /d Z:\EFI\Microsoft\Boot\
bootrec /FixBoot
Now, back up and rebuild the BCD. In modern versions (Windows 10 1709+ and Windows 11) the winning combination is to rename the BCD and use bcdboot:
ren BCD BCD.bak
bcdboot C:\Windows /s Z: /f ALL
bootrec /rebuildbcd
If you're working with BIOS/MBR or earlier systems, the pattern is very similar, with the only changes being the routing and switches. For versions prior to 1709, the following is documented:
ren BCD BCD.old
bcdboot C:\Windows /l en-us /s C: ALL
If the boot store is in C:\Boot (BIOS scenario), remove attributes, rename, and rebuild. This method forces a completely new BCD.
bcdedit /export C:\bcdbackup
attrib C:\Boot\BCD -r -s -h
ren C:\Boot\BCD BCD.old
bootrec /rebuildbcd
Replace Bootmgr and fix the boot sector
In some cases, Bootmgr is corrupt or missing. It can be copied from the installation media to the system root and protected.
- Locate the letter of your middle (e.g., E:) and the letter of your system (C:). Use diskpart or the WinRE Explorer If you have any doubts.
- Run:
copy E:\bootmgr C:\ attrib C:\bootmgr +s +h +r bootrec /fixmbr bootrec /fixboot bootrec /rebuildbcd
In BIOS/MBR, remember to also mark the system partition as active if it isn't already. A correct PBR without an active partition won't boot at all.
diskpart
sel disk 0
list partition
sel partition 1
active
exit
Diagnosis by symptoms: from BOOTMGR and NTLDR to INACCESSIBLE_BOOT_DEVICE
The messages are a good indicator. “BOOTMGR is missing” or “NTLDR is missing” point to damage in the boot manager/boot sector or a poorly prioritized disk. For Windows 7 and later, Startup Repair usually resolves NTLDR/BOOTMGR, and if not, the /FixBoot + /RebuildBcd combination will do the rest.
If the Boot Configuration Data (BCD) is missing or corrupted , try exporting, removing attributes, renaming, and rebuilding. If /RebuildBcd fails with "The requested system device cannot be found," check access to the partition containing the BCD.
This error is common when the environment cannot write to the boot partition, especially in UEFI. A frequent cause is a poorly formatted ESP ( NTFS instead of FAT32) , or one without an assigned drive letter, which prevents bootrec/bcdboot from working. Assign a drive letter to the ESP, format it to FAT32 if absolutely necessary, and then regenerate the BCD using bcdboot.
For “INACCESSIBLE_BOOT_DEVICE (0x0000007B)” errors in the kernel phase, suspect storage controllers , SATA (IDE/AHCI/RAID) changes, or third-party filters. Booting into Safe Mode or using “Last Good Configuration” may be enough to identify the culprit driver with the Event Viewer.
Automatic startup repair and diagnostic logging
It's always worth running the Startup Repair tool from within WinRE. It fixes common problems and leaves a very useful log showing what it did and didn't fix.
%windir%\System32\LogFiles\Srt\Srttrail.txt
Access the Windows system using the USB/ISO file for your version of Windows: Repair your computer > Troubleshoot > Advanced options > Startup Repair . If it boots, restart and check.
Quick fix for the UEFI manager: Repair ESP and FixBoot
On UEFI systems, if /FixBoot returns access denied or cannot find device, the fix involves assigning a drive letter to the ESP (FAT32) and running FixBoot from \EFI\Microsoft\Boot :
diskpart
list vol
sel vol <ESP FAT32>
assign letter=Z:
exit
cd /d Z:\EFI\Microsoft\Boot\
bootrec /FixBoot
If the BCD is empty or missing, bcdboot recreates the UEFI/BIOS boot structure from the Windows installation:
bcdboot C:\Windows /s Z: /f ALL
Advanced kernel-level repairs: SFC, DISM, and drivers
When the logo and spinning wheel appear but the system still won't boot, it's time to check system integrity. SFC and DISM in offline mode are key tools.
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
DISM /image:C:\ /get-packages
DISM /image:C:\ /remove-package /packagename:<nombre_paquete>
DISM /Image:C:\ /Cleanup-Image /RevertPendingActions
If there are pending updates blocking the boot process, clear the status using DISM or rename the pending.xml file and clean the identifier in the Registry. Do this carefully from WinRE.
- rename C:\Windows\winsxs\pending.xml a pending.xml.old.
- Loads Registry subtrees and deletes pendingxmlidentifier If it exists; download and restart.
If you suspect third-party startup drivers (upper/lower filters), check the class key: HKLM\SYSTEM\ControlSet001\Control\Class , remove any non-Microsoft filter values, and restart. As a temporary measure, a clean boot (msconfig) can help isolate conflicting services.
Check WinRE and its registration with reagentc
If the recovery environment fails to start or cannot find your image, you should check its status. Reagentc allows you to view, activate, or relocate WinRE to access Startup Repair and related tools.
reagentc /info
reagentc /enable
reagentc /disable
reagentc /setreimage /path C:\Recovery\WindowsRE
After enabling it or correcting the Winre.wim path , try the automatic repair again. Having WinRE running speeds up any recovery and avoids always relying on external media.
Quick reference commands
For BIOS/MBR (any supported Windows), the classic triad: useful when the problem is MBR/PBR/BCD basic.
bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd
For UEFI (Windows 10/11): CD to Microsoft Boot path, FixBoot and rebuild BCD with bcdboot.
cd /d Z:\EFI\Microsoft\Boot\
bootrec /FixBoot
ren BCD BCD.bak
bcdboot C:\Windows /s Z: /f ALL
When to use CHKDSK, Safe Mode, and Restore Subtrees
If the disk has experienced power outages or you see symptoms of unstable sectors, run CHKDSK. It's best to do this from within WinRE so it can lock and repair the disk.
chkdsk C: /f /r
Safe Mode ( or Safe Mode with Networking) allows you to uninstall problematic drivers and review events. If you suspect registry corruption, you can restore the hives from C:\Windows\System32\config\RegBack to …\config after renaming the current ones.
In very difficult scenarios, temporarily adjusting critical services like TrustedInstaller or disabling third-party filters can allow the system to boot and complete the repair. These steps are delicate; document changes and revert them once the system boots.
Reset this computer or reinstall while keeping your data
If none of the above works, Windows offers non-destructive options. From the media or WinRE: Continue > Reset this PC , choose to keep your files or perform a clean local reinstall.
As a last resort, perform a clean install using an installation USB drive. With a custom installation, Windows moves your data to Windows.old , from where you can recover documents if there is no physical disk damage.
To prevent future problems, schedule backups and restore points, and avoid abrupt shutdowns when installations or updates are pending , or consider disabling fast startup . An inexpensive UPS is worth its weight in gold.
This entire process, from basic to advanced, hinges on identifying at what stage your system is stuck. With WinRE at hand, bootrec for MBR/PBR, bcdedit/bcdboot for BCD, and utilities like SFC/DISM , most boot errors (including corrupted BCD, missing Bootmgr, and the dreaded INACCESSIBLE_BOOT_DEVICE) can be resolved without formatting . If you also verify that the EFI partition is FAT32 and accessible, and check for pending drivers and updates when the problem lies with the kernel, you'll be back to your desktop without any drama or dangerous shortcuts.
Passionate writer about the world of bytes and technology in general. I love sharing my knowledge through writing, and that's what I'll do on this blog, show you all the most interesting things about gadgets, software, hardware, tech trends, and more. My goal is to help you navigate the digital world in a simple and entertaining way.