Skip to content

Ensure the EFI boot directory exists before running BCDBoot - #428

Draft
mpanduru wants to merge 1 commit into
cloudbase:masterfrom
mpanduru:bcdbootfix
Draft

mpanduru wants to merge 1 commit into
cloudbase:masterfrom
mpanduru:bcdbootfix

Conversation

@mpanduru

Copy link
Copy Markdown
Contributor

BCDBoot can attempt to copy the boot manager before EFI\Microsoft\Boot exists on the EFI system partition when generating images from newer Windows Server 2025 builds. This causes repeated BfspCopyFile failures with error 0x3 (ERROR_PATH_NOT_FOUND).

The issue was observed while generating a Windows Server 2025 image from the 24H2.19 ISO release:

SW_DVD9_Win_Srv_STD_CORE_2025_24H2.19_64Bit_English_DC_STD_MLF_X24-30560.ISO

The image generation produced the following logs:

BFSVC Error: BfspCopyFile(H:\windows\boot\EFI\bootmgfw.efi, \?\GLOBALROOT\Device\HarddiskVolume7\EFI\Microsoft\Boot\bootmgfw.efi) failed! (Attempt 60 of 60) Last Error = 0x3
BFSVC Warning: Failed to copy Boot Manager to Microsoft bootmgfw.efi location. Last error = 0x3

Create the destination directory in Create-BCDBootConfig before invoking BCDBoot for UEFI images. This ensures the directory exists for both the image-provided executable and the host fallback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant