Forum Discussion
Windows OS edition validation error
Hey, that validation error usually comes down to the OS edition of the image not being one that AVD accepts for the deployment type you're setting up, so it's almost always fixable once we spot the mismatch.
A few things to check. First, are you using a marketplace image or a custom one from a compute gallery? And is this host pool pooled or personal? That combination matters a lot. For a pooled host pool you need a multi-session edition, specifically Windows 11 Enterprise multi-session (or Windows 10 Enterprise multi-session). If you accidentally picked Windows 11 Enterprise (single session), Pro, or Home, the validation will fail because those editions aren't supported for that scenario. Personal host pools can use single session Enterprise, but Pro and Home still won't pass.
If it's a custom image, the most common culprits are that the base image was built from an unsupported edition, or it wasn't generalized properly before being captured. AVD checks the edition during validation, so a custom image needs to be based on a supported Enterprise or Enterprise multi-session edition and sysprepped or generalized correctly, otherwise you'll hit exactly this kind of error.
Quickest test: try spinning up a session host using a clean marketplace image of Windows 11 Enterprise multi-session and see if validation passes. If it does, then the issue is your custom image rather than the host pool config, which narrows it down nicely.
If you can share whether it's marketplace or custom, the exact edition or SKU you're deploying, and where exactly the error shows up (during host pool creation, adding session hosts, etc.), I'm happy to help pinpoint it. What does your current image source look like?