Question

You use Azure VM Image Builder (AIB) to create a custom Windows 11 multi-session image for an AVD host pool. Your template runs a PowerShell customizer that installs applications and then you manually add a step that runs 'sysprep /generalize /oobe /shutdown' as part of the build. After the build completes and you deploy session hosts from the resulting image version, the VMs fail to boot correctly and appear stuck. What is the most likely cause and correct action?

Accepted Answer

AIB automatically generalizes the image at the end of the build; running sysprep manually causes a double generalization that corrupts the image, so remove the manual sysprep step.

Answer

You must run sysprep twice for multi-session images; add a second sysprep call after the first to fully generalize the OS.

Answer

Sysprep is not supported on Windows 11 multi-session, so switch the source to Windows Server and re-run the build.

Answer

The build failed because AIB requires the image to remain specialized; change the distribute target to a specialized VHD instead of a managed image.