The Boot Configuration Data (BCD) store tells the Windows Boot Manager which operating systems exist, where they are, and how to start them. It replaced boot.ini in Windows Vista. When Windows fails to boot with errors like “The Boot Configuration Data for your PC is missing or contains errors” (0xc000000f, 0xc0000034), BCD is usually the cause.

Where BCD lives

Firmware Location
UEFI \EFI\Microsoft\Boot\BCD on the EFI System Partition
BIOS (legacy) \Boot\BCD on the active system partition

Check which your system uses: System Information (msinfo32) → BIOS Mode.

Read the store

Run Command Prompt as Administrator:

bcdedit /enum

Key entries:

  • Windows Boot Manager {bootmgr} — default entry, timeout, display order.
  • Windows Boot Loader — one per installation; {current} is the running system, {default} the default.
    • device / osdevice — the partition containing Windows
    • path — \Windows\system32\winload.efi (UEFI) or winload.exe (BIOS)
    • recoverysequence — the linked Windows Recovery Environment

bcdedit /enum all /v shows every object with full GUIDs.

Back up first

bcdedit /export C:\bcd-backup

Restore with bcdedit /import C:\bcd-backup.

Common changes

:: Boot menu timeout (seconds)
bcdedit /timeout 5

:: Change the default OS
bcdedit /default {GUID}

:: Rename an entry
bcdedit /set {current} description "Windows Server 2022"

:: Boot into Safe Mode (minimal / network) on next starts
bcdedit /set {current} safeboot minimal
bcdedit /set {current} safeboot network
:: …and back to normal
bcdedit /deletevalue {current} safeboot

:: Show the advanced boot options menu (F8-style) every boot
bcdedit /set {current} bootmenupolicy legacy

:: Log loaded drivers to C:\Windows\ntbtlog.txt
bcdedit /set {current} bootlog yes

On a remote VPS: Safe Mode may disable networking and Remote Desktop. Only change boot settings if you can reach the server’s VNC console from your control panel.

Repair BCD when Windows won’t boot

Boot into the Windows Recovery Environment (WinRE): from a Windows installation ISO (Repair your computer), or automatically after failed boots. Open Troubleshoot → Advanced options → Command Prompt.

1. Try automatic repair first

Startup Repair in WinRE fixes many BCD problems on its own.

2. bootrec (mainly BIOS/MBR systems)

bootrec /scanos
bootrec /rebuildbcd
bootrec /fixmbr
bootrec /fixboot

/fixboot may report Access is denied on some UEFI systems — use bcdboot instead.

3. Rebuild with bcdboot (UEFI and BIOS)

Find the Windows drive letter in WinRE (often not C:) with diskpart → list volume. For UEFI, assign a letter to the FAT32 EFI partition:

diskpart
list volume
select volume 2        :: the FAT32 EFI System Partition
assign letter=S
exit

bcdboot D:\Windows /s S: /f UEFI

For BIOS systems: bcdboot D:\Windows /s C: /f BIOS (where C: is the active system partition in WinRE).

bcdboot copies fresh boot files and creates a new BCD store pointing at the Windows installation.

4. Check the disk

chkdsk D: /f
sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows

On our Windows VPS plans, the VNC console in the control panel shows the boot process and the recovery environment when Windows can’t start. If you need installation media for repairs, open a support ticket; if recovery isn’t possible, reinstall the OS from the control panel and restore your data from backup.

  • Windows
  • Boot
  • Troubleshooting