When deploying Windows 11 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.
C:\Windows\panther\setuperr.log will contain the following errors:
BiUpdateEfiEntry failed c000000dBiExportBcdObjects failed c000000dBiExportStoreAlterationsToEfi failed c000000dFailed to export alterations to firmware. Status: c000000dThese errors indicate that the sysprep process is failing to properly configure the boot settings required for the guest OS.
This behavior is caused by a Microsoft Windows issue in the sysprep process when using the `/generalize` option. The issue results in incorrect Boot Configuration Data (BCD) settings after the generalize process completes, preventing the guest OS from configuring boot settings required for customization.
VMware engineering has been collaborating with Microsoft on this issue. In the meantime, the following workaround has been confirmed:
Workaround: BCD Repair Script (SetupComplete.cmd)
Follow these steps to repair the BCD entries automatically after the Sysprep process:
C:\Windows\Setup\Scripts\SetupComplete.cmd in that directory.bcdedit -set {current} osdevice partition=C:
bcdedit -set {current} device partition=C:
bcdedit -set {memdiag} device partition=\Device\HarddiskVolume1Note: Subscribe to this article to be updated on the fix status of this issue (Reference: Subscribe to a Broadcom knowledge article by article or product).