Forum Discussion
Windows 11 24H2 Multi User Marketplace Image - Sysprem Issue
We are experiencing an issue with our deployment process this month which ties in with Microsoft's October release of the new Windows 11 24H2 Multi-User Marketplace Image. The issue occurs during the sysprep of the image in our management tool Nerdio before putting it in the Azure compute gallery for use when provisioning new hosts.
Our process hasn’t changed and is completely automated. Sometime around 15th October the process started erroring on the sysprep stage, this was also the point we noticed the new Microsoft marketplace image had dropped in Azure.
The process times out in Nerdio when it is running through the automated process, looking at the logs sysprep is complaining about bitlocker been turned on. If we change the image to a single user version of 24H2 gen 2 it works as does using the September version of the Windows 11 24H2 Multi-User Image.
Marketplace Image:
SKU - win11-24h2-avd / Version- 26100.9711.261011
PublisherName - MicrosoftWindowsDesktop
Management Tooling
Nerdio Manager for Enterprise v8.2.2
Thanks in advance.
2 Replies
The useful distinction in your logs is whether the image-build VM's OS volume is encrypted when Nerdio invokes Sysprep. Microsoft's Azure generalization guidance explicitly requires fully decrypted drives; changing the account running Sysprep does not remove that prerequisite.
On a disposable build VM using version 26100.9711.261011, run Get-BitLockerVolume -MountPoint C: immediately before generalization. Record VolumeStatus, EncryptionPercentage and ProtectionStatus, and compare them with an otherwise identical September-image build.
Suspending BitLocker is insufficient because suspension leaves the data encrypted. If encryption is present, have your approved image-preparation workflow complete decryption before Sysprep, rather than merely checking ProtectionStatus is Off. Keep this change confined to the image-building process and preserve your normal session-host encryption requirements.
Retain the Sysprep logs and before/after volume states for Microsoft and Nerdio support. Your comparison suggests an image-dependent change, but the published preparation requirement alone does not confirm an October Marketplace regression or a Nerdio-specific fix.
The October 2026 release of the Windows 11 24H2 Multi‑User Marketplace image introduced a regression where Sysprep fails due to BitLocker being enabled by default. The Sysprep errors occur if BitLocker protection is active, and this aligns with your Nerdio automation logs. You may consider disabling BitLocker before running Sysprep or adjusting automation to run Sysprep under the local Administrator account.