Your PC powers on, the fans spin, but Windows just won’t load. Black screen, “Bootmgr is missing”, or an endless restart loop. Before you grab a USB stick and wipe everything, know this: most Windows startup failures are bootloader problems, not dead installs. And they’re fixable in minutes from WinRE.
I’ve recovered dozens of machines this way, including a laptop that had been sitting in a drawer for two years because “it was dead”. It wasn’t. The MBR was just corrupted after a bad update. Here’s exactly what to do.
Get into the Windows Recovery Environment (WinRE) first
Everything hinges on reaching WinRE. If you can still log in, hold Shift while clicking Restart from the Start menu. That drops you straight into the blue recovery menu.
If Windows won’t even reach the login screen, force the issue: power on the PC and, the moment the Windows logo appears, hold the power button for 5 seconds. Repeat three times in a row. On the fourth boot, Windows detects the failed starts and throws you into WinRE automatically. This is the automatic repair trigger, and it works on Windows 10 and Windows 11.
If your machine uses UEFI with Fast Boot enabled and you can’t interrupt it, disable Fast Boot in BIOS first. That setting is the reason many people think their PC is bricked when it’s just refusing to hand over control.
Troubleshoot > Advanced options: what to click
Once inside WinRE, navigate to Troubleshoot > Advanced options. You’ll see a list with Startup Repair, Command Prompt, System Restore, Uninstall Updates, and Startup Settings.
Run Startup Repair first. It’s automated and fixes simple BCD corruption. But here’s the honest truth: it fails more often than it succeeds on real bootmgr errors. Don’t waste more than one attempt on it.
If it fails, jump to Command Prompt. That’s where the actual repair happens.
Repair Windows startup with bootrec commands
Inside CMD, type these one by one, pressing Enter after each:
- bootrec /fixmbr — rewrites the Master Boot Record. Fixes “operating system not found” errors.
- bootrec /fixboot — writes a new boot sector. Fixes “Bootmgr is missing”.
- bootrec /scanos — scans all drives for installed Windows systems.
- bootrec /rebuildbcd — rebuilds the Boot Configuration Data store. This is the one that actually brings Windows back most of the time.
On rebuildbcd, if it asks whether to add the installation to the boot list, type Y and hit Enter. If it says “Total identified Windows installations: 0”, don’t panic — that’s a symptom, not a death sentence. It usually means the BCD store or the EFI partition is messed up.
If bootrec /fixboot throws “Access Denied”
This is the most common error on UEFI systems. bootrec /fixboot fails when the EFI System Partition (ESP) isn’t mounted or has the wrong filesystem. Fix it like this:
- Type diskpart, then list disk, then select disk 0 (pick your system disk).
- list partition, then select partition X where X is the EFI partition (usually 100–500 MB, FAT32).
- assign letter=Z to mount it, then exit diskpart.
- Run bcdboot C:Windows /s Z: /f UEFI.
That last command rebuilds the entire EFI boot files from scratch, pulling fresh files from your Windows installation. In my experience, this single command fixes 80% of UEFI boot failures that bootrec alone can’t touch.
Check for a failing disk before you celebrate
Here’s the part nobody mentions: a corrupted bootloader is sometimes the first symptom of a dying drive. Before rebooting, run chkdsk C: /f /r from the same CMD window. If it reports bad sectors, back up your data immediately after Windows boots — don’t assume you’re in the clear.
Also run sfc /scannow /offbootdir=C: /offwindir=C:Windows to repair corrupted system files that might be triggering the boot failure in the first place. This offline SFC scan works from WinRE and catches damage Startup Repair ignores.
When nothing works: what’s actually left
If you’ve done fixmbr, fixboot, rebuildbcd, and bcdboot and Windows still won’t start, you’re facing one of three scenarios: a physically failing drive, a corrupted registry hive, or a Windows update that broke the kernel.
For registry corruption, try System Restore from Advanced options, pointing to a restore point before the failure. For update damage, use Uninstall Updates in the same menu — it rolls back the last cumulative update without touching your files.
Only if all of that fails should you consider a bootable USB with the Windows ISO to run a repair install (in-place upgrade). That preserves your programs and files. Formatting is the absolute last resort, and honestly, if you reach that point, the problem was likely hardware all along.
The bottom line: Windows startup repair without formatting works because the bootloader is a small, rebuildable component. Your data lives in a completely separate layer. As long as the drive spins, you almost never need to wipe anything.
