BCDBoot fails with "Failure when attempting to copy boot files" when creating native boot VHDX

Debasish Kar 20 Reputation points
2026-06-22T12:53:35.71+00:00

Hi,

I am trying to create a native boot VHDX on Windows 11. I created a VHDX, initialized it as GPT, formatted it as NTFS, and applied Windows from install wim using DISM. The Windows files appear to be present, including winload efi. However, when I run BCDBoot against the deployed installation, I immediately get "Failure when attempting to copy boot files". Running BCDBoot against my current Windows installation works normally. I tested both Windows 8.1 and Windows 10 1909 and get the same result. Has anyone seen this issue on recent Windows 11 builds?

Windows for home | Windows 11 | Install and upgrade
0 comments No comments

Answer accepted by question author
Anonymous
2026-06-22T23:48:43.7+00:00

Hi Debasish Kar,

I understand how frustrating this can be, especially when DISM completes successfully and all expected Windows files appear to be present, yet BCDBoot immediately fails with "Failure when attempting to copy boot files". Based on the information you provided, I can see that DISM completed successfully and the deployed Windows files (including winload.efi) are present, but BCDBoot fails immediately with "Failure when attempting to copy boot files".

To narrow this down further, could you provide:

  • The exact bcdboot command you are running.
  • Whether Windows 11 is installed in UEFI or Legacy BIOS mode.
  • Whether the VHDX contains only the Windows partition or also contains its own EFI System Partition.

In the meantime, please try the following:

1, Confirm the VHDX is attached and assigned a drive letter

Open Disk Management and verify that the Windows partition inside the VHDX is mounted and accessible (for example, V:).

2, Try specifying the firmware type explicitly

If your host system is UEFI, run: bcdboot V:\Windows /f UEFI

3, Check whether BCDBoot can access the system EFI partition

Assign a drive letter to the EFI System Partition temporarily:

mountvol S: /s
bcdboot V:\Windows /s S: /f UEFI

If BCDBoot succeeds when the EFI partition is specified explicitly, the issue may be related to locating the target boot partition automatically.

4, Verify the deployed image architecture matches the host

For example, ensure you're not deploying an x86 image onto an x64 UEFI boot environment.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".    

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.