Windows boot troubleshooting: WinRE, reagentc and the BCD store

Goal

Diagnose and repair a Windows system that fails to start, using the Windows Recovery Environment (WinRE) and the bcdedit/reagentc command-line tools, with a safe rollback point for BCD changes.

Prerequisites

An elevated (administrator) command prompt — inside WinRE, or in a running Windows session for reagentc/bcdedit on the online system. If the system volume is BitLocker-protected, have the recovery key: WinRE needs it to unlock the volume (manage-bde -unlock C: -RecoveryPassword <key>), and boot-configuration changes can trigger a recovery-key prompt at the next start; from a running system, suspend protection for one restart first with manage-bde -protectors -disable C: -RebootCount 1.

Steps

1. Check WinRE: reagentc /info displays "the current status of Windows RE and any available recovery image"; it works on the running system or, with /target <path>, on an offline image. If it reports disabled and an image is present, reagentc /enable turns it back on.
2. Reach WinRE: Windows starts it automatically after repeated failed starts; from a running system shutdown /r /o /t 0 restarts into it; or boot installation media and choose "Repair your computer". Startup Repair is a menu item under Troubleshoot > Advanced options, separate from the Command Prompt item.
3. Back up the store before changing it: bcdedit /export C:\BCD-Backup; bcdedit /import C:\BCD-Backup restores it, deleting all current entries first. Inside WinRE drive letters often differ, so pick a path that exists there.
4. Inspect: bcdedit /enum (same as /enum active) lists the boot entries; the Windows Boot Loader's osdevice shows the system volume's letter, which in WinRE is often not C:. For that volume Microsoft's procedure runs chkdsk /f D:, sfc /scannow /offbootdir=D:\ /offwindir=D:\windows and DISM /image:D:\ /cleanup-image /restorehealth (with D: as found).
5. Safe Mode: bcdedit /set {default} safeboot minimal (or network, which includes network drivers, per BcdLibrary_SafeBoot). Use {default} from WinRE, where {current} is the recovery environment's own entry; from the running system {current} is the running installation. In PowerShell quote identifiers ('{current}', '{default}') because unquoted braces are parsed as a script block, e.g. bcdedit /set '{current}' safeboot minimal. The setting persists across reboots; undo it with bcdedit /deletevalue {default} safeboot.
6. Verify with bcdedit /enum and, if WinRE was touched, reagentc /info.

Expected result

reagentc /info reports WinRE enabled with a valid image path; bcdedit /enum shows the expected default entry and no leftover safeboot value; the next boot reaches the normal logon screen.

Limits and test basis

Microsoft's reference warns that changing some boot entry options with bcdedit /set "could render your computer inoperable" — always export first. bcdedit and reagentc need administrator rights. For a single visit to the advanced boot menu instead of a persistent Safe Mode setting, run bcdedit /set {current} onetimeadvancedoptions on on the running system; it shows the menu at the next start only.