Finding we are getting "Activate Windows" prompts now on the latest build we've done for our 2016 based images but the Activation script appears to have worked successfully. We are on ELM Version 24.3.2.1021. I've updated the ELM scripts and that seems to be when this started. Going to open the OS Layer as we are also seeing issues with our performance counters as well 😞 . If I run a "slmgr /ato" it immediately activates the VM successfully (in my MCS deployed VDAs). Any ideas? I also saw this in the edocs "Publishing images into environments where both KMS and Active Directory-based activation (ADBA) are being used at the same time causes problems with activation." Is there anything special I should do if ADBA is in place? Select "Do not use KMS" on the image? I'm not sure why this has changed though as I think we have had both for some time. We also have 2019 and 2022 based images that do not seem to have this issue despite the "use KMS" being set.