Windows & BSOD · critical

How to fix Error 0xc0000034 at startup (BCD or winload.efi not found)

Windows & BSOD troubleshooting guide

What this error means

Windows does not start and shows a blue Recovery screen with error code 0xc0000034. Microsoft's name for this code is STATUS_OBJECT_NAME_NOT_FOUND: the Windows Boot Manager looked for something it needs and could not find it, usually an entry in the boot configuration data (BCD) or the Windows loader file winload.efi. It often appears after an interrupted update, a disk or partition change, or a failed attempt to install a second operating system. The fix is usually rebuilding the boot files from the recovery environment.

Updated

Applies to
Windows 11 and Windows 10
Difficulty
Intermediate
Before changes
Medium; boot repair commands change boot files

Reviewed by Matyáš Rada · Documentation checked: 2026-10-31 · Checked against Microsoft's Windows startup troubleshooting, NTSTATUS and BCDBoot documentation; not tested on every configuration.

Before you begin

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 complete
01Run Startup Repair

Startup Repair is Microsoft's first method for boot loader problems and often rebuilds missing BCD entries automatically.

  1. 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.
  2. Choose Troubleshoot > Advanced options > Startup Repair and select your Windows.
What to expect

Windows starts normally.

If it does not help

If Startup Repair cannot fix it, open Command Prompt from the same menu (or press Shift + F10 on the installation USB).

Browse related errors
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.

  1. 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.
  2. Confirm with dir C:\Windows (replace C: with the letter you found).
What to expect

You know the letter of the Windows partition.

If it does not help

Use that letter instead of C: in the next steps.

Browse related errors
03Rebuild the BCD with bootrec

Microsoft's method for BCD errors scans for Windows installations and rebuilds the boot configuration.

  1. Run bootrec /scanos.
  2. Then run bootrec /rebuildbcd and answer Y to add the Windows installation it finds.
  3. Close Command Prompt and choose Continue to start Windows.
What to expect

Windows starts.

If it does not help

If rebuildbcd finds 0 installations or Windows still does not start, use bcdboot in step 4.

Browse related errors
04Recreate the boot files with bcdboot

BCDBoot copies fresh boot files, including winload.efi entries, from the Windows folder and creates a new BCD.

  1. Run bcdboot C:\Windows (with the Windows partition letter from step 2).
  2. Wait for "Boot files successfully created" and restart.
What to expect

Windows starts with new boot files.

If it does not help

If bcdboot reports a failure, check the file system in step 5 and try again.

Browse related errors
05Check the file system

File system errors can hide the files the boot manager needs.

  1. In the recovery Command Prompt, run chkdsk C: /f (with the Windows partition letter).
  2. If it reports bad sectors, run chkdsk C: /r as well.
  3. Repeat step 4 afterwards.

Chkdsk /r can take hours on large drives.

What to expect

Chkdsk finishes and Windows starts.

If it does not help

Many bad sectors mean the drive is failing; copy your files off and replace it.

Browse related errors
06Undo a pending update

Microsoft's startup troubleshooting includes reverting pending update actions when an update left Windows unable to start.

  1. In Troubleshoot > Advanced options, choose Uninstall Updates and remove the latest quality update.
  2. Or in Command Prompt run DISM /Image:C:\ /Cleanup-Image /RevertPendingActions (with the correct letter), then restart.
What to expect

Windows starts after the update is removed.

If it does not help

Install the update again later once Windows works.

Browse related errors
07Reset or reinstall Windows

If the boot files cannot be rebuilt, a fresh installation creates a new working boot setup.

  1. Copy your files to another drive first, for example by connecting the disk to another PC.
  2. 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.

What to expect

Windows starts normally.

If it does not help

If you used another operating system alongside Windows, reinstall its boot manager afterwards according to its documentation.

Browse related errors

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

Sources & further reading