Note the error code, then from the recovery screen choose Enter Recovery Environment (or press F1/Esc for recovery options). Try Uninstall Updates, Startup Repair and System Restore. If those fail, rebuild boot files with bootrec/bcdboot, then check the drive.

What's going on

You can see it in two forms: the blue “Your PC/Device needs to be repaired” screen from the boot manager, which shows an error code, and “Automatic Repair couldn’t repair your PC” after repair attempts fail. Where there's a code, it points to the cause: 0xc0000225 and 0xc000000e mean boot data or the boot device is missing, 0xc0000001 often means a damaged boot file or memory, and 0xc000021a means a critical Windows process failed.

Most cases are caused by a failed update, corrupted boot configuration, or a drive with errors. Your files are typically still on the drive even when Windows won’t start.

Symptoms

  • Blue recovery screen: “Your PC/Device needs to be repaired” or “ran into a problem and couldn't be repaired”.
  • An error code such as 0xc0000001, 0xc000000e or 0xc0000225.
  • Options to press Enter, F1, F8 or Esc.

What causes it

  • Failed or interrupted Windows update.
  • Corrupted Boot Configuration Data (BCD) or EFI partition.
  • Drive errors or a failing SSD/HDD.
  • Changed BIOS settings or disconnected drive.

Try these fixes

  1. Write down the error codeIt narrows down which fix applies.
  2. Open Windows RecoveryTo open Windows Recovery: turn the PC on, and as soon as the Windows logo appears hold the power button to force it off. Do this three times and Windows opens Automatic Repair → Advanced options. Or boot from a Windows installation USB and choose Repair your computer.
  3. Uninstall recent updatesTroubleshoot → Advanced options → Uninstall Updates → latest quality update first, then latest feature update.
  4. Startup Repair and System RestoreTry Startup Repair; then System Restore to a point before the problem.
  5. Rebuild boot filesOpen Command Prompt in recovery and run the commands below.
  6. Check the diskIn the same Command Prompt run chkdsk C: /f (use the Windows drive letter shown by dir).
  7. Save data and reset if neededIf nothing works, copy files off using a Windows USB or Linux live USB, then use Reset this PC or a clean install.

Command

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

Run from Windows Recovery → Troubleshoot → Advanced options → Command Prompt. On UEFI PCs, if /fixboot says 'Access is denied', rebuild the boot files with bcdboot C:\Windows (check the Windows drive letter with dir first).

How to tell it worked: Windows starts normally and Reliability Monitor shows no new critical startup errors.

Avoiding it in future

Keep backups, let updates finish, and keep at least 20 GB free on C:.