Skip to contentGo to the directory tree
  1. C:
  2. EFI
  3. Microsoft\Boot
  4. bootmgfw.efi
FileRisk: Do not touch

bootmgfw.efi \EFI\Microsoft\Boot\bootmgfw.efi

bootmgfw.efi, the Windows Boot Manager in UEFI mode: firmware starts it, it reads the BCD and then loads winload.efi of the chosen Windows.

Updated on By AltF4 Formation

What it’s for

bootmgfw.efi is the Windows Boot Manager on UEFI PCs, the counterpart of bootmgr on BIOS PCs. The “Windows Boot Manager” entry stored in the firmware’s NVRAM points to it. It reads the BCD store, shows the menu when there are several entries, then starts winload.efi of the selected system.

What it contains

An EFI executable signed by Microsoft. With Secure Boot, the firmware checks its signature before running it. The reference copy is C:\Windows\Boot\EFI\bootmgfw.efi, and bcdboot copies it to the ESP. On installation media the default loader is \EFI\Boot\bootx64.efi.

Risks and best practices

  • A missing or altered file gives a blank boot screen or a “No bootable device” error. Restore it with bcdboot C:\Windows /s S: /f UEFI, not by copying it manually.
  • If Secure Boot is on and the signature no longer validates, the firmware refuses to run it: check it with Get-AuthenticodeSignature.
  • An update can replace this file; its version follows the operating system’s.

Useful commands

Fenêtre de terminal
# As administrator: mount the ESP, then check signature and version
mountvol S: /S
Get-AuthenticodeSignature S:\EFI\Microsoft\Boot\bootmgfw.efi | Select-Object Status, SignerCertificate
(Get-Item S:\EFI\Microsoft\Boot\bootmgfw.efi).VersionInfo.FileVersion
# Is Secure Boot on?
Confirm-SecureBootUEFI
Fenêtre de terminal
:: "Windows Boot Manager" entry in firmware
bcdedit /enum firmware

Report a mistake