When deploying Windows 11 24H2 virtual machines from templates with Guest OS Customization enabled in vCenter, the Windows desktop fails to load after login. Instead, a ShellHost.exe error message appears repeatedly, preventing normal system operation. Manual sysprep works correctly, but the automated customization through vCenter fails.
This issue is caused by a Microsoft Windows bug in the sysprep process when using the /generalize
option (which vCenter's Guest OS Customization uses).
The bug results in incorrect Boot Configuration Data (BCD) settings after the generalize process completes. Specific errors that occur during this process include:
BiUpdateEfiEntry failed c000000d
BiExportBcdObjects failed c000000d
BiExportStoreAlterationsToEfi failed c000000d
Failed to export alterations to firmware. Status: c000000d
These errors indicate that the sysprep process is failing to properly configure the boot settings required for the guest OS.
VMware engineering has been collaborating with Microsoft on this issue. In the meantime, the following workarounds have been confirmed to work around the issue:
If already using Windows 11 24H2 with updates installed:
As identified by customers, this workaround can resolve the issue after Guest OS Customization is run:
Note: VMware engineering has confirmed that removing the specific Windows updates (Options 1 and 2) is the most reliable solution until Microsoft addresses this issue.