If Windows offers recovery options on the error screen, use them. Otherwise you need a Windows installation USB, made on another PC with Microsoft's media creation tool. If BitLocker is on, have your recovery key ready (aka.ms/myrecoverykey). If Windows cannot start, see the startup guide.
Work through these checks
0 of 7 complete01Run Startup Repair
Startup Repair is Microsoft's first method for boot loader problems and often rebuilds missing BCD entries automatically.
- On the error screen, press F1 or Esc for recovery options if offered, or start from the Windows installation USB and choose Repair your computer.
- Choose Troubleshoot > Advanced options > Startup Repair and select your Windows.
Windows starts normally.
If it does not helpIf Startup Repair cannot fix it, open Command Prompt from the same menu (or press Shift + F10 on the installation USB).
02Check the drive letters in recovery
In the recovery environment the Windows partition often has a different letter, and commands must use the right one.
- In Command Prompt, run diskpart, then list vol, and note the letter of the large NTFS volume with Windows and the small FAT32 volume (the EFI system partition). Type exit.
- Confirm with dir C:\Windows (replace C: with the letter you found).
You know the letter of the Windows partition.
If it does not helpUse that letter instead of C: in the next steps.
03Rebuild the BCD with bootrec
Microsoft's method for BCD errors scans for Windows installations and rebuilds the boot configuration.
- Run bootrec /scanos.
- Then run bootrec /rebuildbcd and answer Y to add the Windows installation it finds.
- Close Command Prompt and choose Continue to start Windows.
Windows starts.
If it does not helpIf rebuildbcd finds 0 installations or Windows still does not start, use bcdboot in step 4.
04Recreate the boot files with bcdboot
BCDBoot copies fresh boot files, including winload.efi entries, from the Windows folder and creates a new BCD.
- Run bcdboot C:\Windows (with the Windows partition letter from step 2).
- Wait for "Boot files successfully created" and restart.
Windows starts with new boot files.
If it does not helpIf bcdboot reports a failure, check the file system in step 5 and try again.
05Check the file system
File system errors can hide the files the boot manager needs.
- In the recovery Command Prompt, run chkdsk C: /f (with the Windows partition letter).
- If it reports bad sectors, run chkdsk C: /r as well.
- Repeat step 4 afterwards.
Chkdsk /r can take hours on large drives.
Chkdsk finishes and Windows starts.
If it does not helpMany bad sectors mean the drive is failing; copy your files off and replace it.
06Undo a pending update
Microsoft's startup troubleshooting includes reverting pending update actions when an update left Windows unable to start.
- In Troubleshoot > Advanced options, choose Uninstall Updates and remove the latest quality update.
- Or in Command Prompt run DISM /Image:C:\ /Cleanup-Image /RevertPendingActions (with the correct letter), then restart.
Windows starts after the update is removed.
If it does not helpInstall the update again later once Windows works.
07Reset or reinstall Windows
If the boot files cannot be rebuilt, a fresh installation creates a new working boot setup.
- Copy your files to another drive first, for example by connecting the disk to another PC.
- Choose Troubleshoot > Reset this PC > Keep my files, or install Windows from the USB.
Reset this PC removes installed apps; a clean installation erases the partition you install to.
Windows starts normally.
If it does not helpIf you used another operating system alongside Windows, reinstall its boot manager afterwards according to its documentation.
Possible causes
- Missing or damaged boot configuration data (BCD)
- An interrupted Windows update or power loss during startup
- Partitions changed, cloned or resized
- Another operating system or boot manager installed alongside Windows
- File system errors on the Windows drive
Was this helpful?
Your progress is saved on this device.