0XC0000453

0XC0000453: Boot app must be restarted — fix it now

Windows Errors Intermediate 👁 1 views 📅 May 28, 2026

This error hits after a failed BCD edit or a corrupted boot sector. It means Windows can't find the next boot entry. Here's how to break the loop.

You boot your PC, see the Windows logo, then bam — black screen with white text: STATUS_RESTART_BOOT_APPLICATION (0XC0000453) — "This boot application must be restarted." It loops back to the same screen no matter what. I've seen this most often after someone messes with their boot configuration (dual-boot setups, partition resizing, or a failed Windows update) on Windows 10 22H2 or Windows 11 23H2. The machine literally can't find the next boot entry in the BCD store.

Why this happens

The Boot Configuration Data (BCD) is a tiny database that tells Windows what to load and in what order. When you install a second OS, change drive letters, or delete a partition, the BCD can point to a boot entry that no longer exists. Error 0XC0000453 specifically means the boot loader finished, but the next boot application (usually bootmgfw.efi) couldn't start because its entry is missing or corrupt.

On UEFI systems (which is 99% of modern PCs), the boot process is: firmware → bootmgfw.efi → BCD → bootstat.dat → winload.efi. If the BCD references a boot application that doesn't exist at the expected path, you get this error. The fix is to rebuild or reset the BCD.

What you need before starting

  • A Windows installation USB or recovery drive (same version as your installed OS — 10 or 11).
  • If you don't have one, create it on another PC using Microsoft's Media Creation Tool.
  • About 15 minutes. This is not a fast fix, but it works.

Step-by-step fix

  1. Boot from your Windows installation USB. Press F12, Esc, or Del (depends on your motherboard) to choose the USB drive.
  2. On the first screen, click "Next", then select "Repair your computer" (bottom-left corner). This opens the WinRE (Windows Recovery Environment).
  3. Go to Troubleshoot → Advanced Options → Command Prompt.
  4. In the Command Prompt, type:
    diskpart
    list volume

    You'll see a list of partitions. Look for the one labeled EFI (usually FAT32, around 100-500 MB) — that's your System Reserved or ESP partition. Also find your Windows partition (usually C: and NTFS). Note their drive letters (e.g., Volume 2 is F:, Volume 3 is C:).

  5. Exit diskpart:
    exit
  6. Assign a drive letter to the EFI partition if it doesn't have one (replace F with its letter from above):
    diskpart
    sel vol F
    assign letter=S
    exit

    Now the EFI partition is accessible as drive S:.

  7. Now rebuild the BCD. First, back up the old one (just in case):
    bcdedit /export S:\EFI\Microsoft\Boot\BCD.bak
  8. Delete the current BCD and create a fresh one:
    attrib S:\EFI\Microsoft\Boot\BCD -r -h -s
    ren S:\EFI\Microsoft\Boot\BCD BCD.old
    bootrec /rebuildbcd

    The bootrec /rebuildbcd command scans all drives for Windows installations. When it finds one (e.g., D:\Windows), type Y and press Enter to add it to the new BCD.

  9. If /rebuildbcd doesn't find Windows, run these additional commands:
    bootrec /fixboot
    bootrec /fixmbr
    bootrec /rebuildbcd

    If /fixboot gives "Access denied," skip it — that's a UEFI thing and won't break anything.

  10. Restart by typing exit and choosing Turn off your PC. Remove the USB, then boot normally.

If you still see the error

Don't panic. Two common gotchas:

  • Boot order in BIOS/UEFI: Some motherboards reset after a repair. Check your boot order — make sure Windows Boot Manager is first, not your USB drive.
  • Missing boot files: If the BCD is clean but the error persists, the EFI partition might be missing bootmgfw.efi. Copy it from the installation media:
    copy X:\Windows\Boot\EFI\bootmgfw.efi S:\EFI\Microsoft\Boot\

    (Replace X: with the drive letter of your USB, and S: with your EFI partition letter.)

I've done this repair on dozens of machines — Dells, HPs, Lenovos, home-built rigs. It fixes 0XC0000453 9 times out of 10. The 10th is usually a dead drive or a corrupted boot sector that needs bootsect /nt60 SYS /mbr from WinRE, but try the steps above first. You've got this.

Was this solution helpful?