Forum Discussion
Server 2022 KMS host key bug; Can't activate Win10 Enterprise LTSB/LTSC
- Thank you!
- Installed KB5009616 on our 2019 KMS and ran slmgr /ato to reactivate it and now everything is working. Been able to activate Win10 enterprise, win 10 pro, LSTC, Win11, server 2012, 2016, 2019 and 2022. So were good. (ADBA is not an option on campus)
We never had a problem with the 2022 key and LTSC/B clients using ADBA.
Prior to the fix, clients on our domain would activate (via ADBA) while those that were not (using KMS) would generate the error.
My ltsc/b test clients would fail activation against the KMS. I would then join them to the domain, and they would successfully activate.
- Anyone using ADBA verified this works with the 2022 KMS key for all LTSC/B?
- Thanks I'll see what happens, I know you can only use the keys 5 times and I have activated it 3 times for sure. Twice on one server and once one the 2nd server.
I can confirm this also. After applying KB5010421 to our 2022 server (with KMS role) and re-installing the key, slmgr /dli now displays ...VOLUME_KMS_WS22. However, it still wouldn't activate 2016LTSB, 2019LTSC and 2021LTSC clients. But after using slmgr.vbs /ato on the kms host itself, it now successfully activates all the versions.
Thank you all for keeping at this. Premier support was absolutely no help on this issue. This discussion thread saved the day.- I can confirm that after installation of KB5010427 and reactivation of KMS slmgr.vbs /ato it is working. (maybe KB5009616 was enough but I did not reactivate at that time). The reactivation is mandatory so it seems.
xwinger61 The fix is for the KMS Host Server
the key is not and do not need to be changed, it just need to reactivate to consume the updated licenses after installing relevant update
Server 2016: KB5010359 or later
Server 2019: KB5009616 or later
Server 2022: KB5010421 or later
- So do we put the fix on the kms server or client? And do we need to get a new KMS key or will the KMS key installed on the KMS server work? Kind of confused on the whole 2022.01.. Will the key be updated to 2022.01 or do we need to get a newer key. I have KMS working on a 2019 server. And every think but Win10 LSTC works ever Win11. Had to go with a 2019 server because when I installed the 2022 key on a 2022 kms server it only recognized it as 2019 and below. Not a 2022 key. But before I screw around with KB5010427 on the server and screw up campus I'd like a little clarification.
OK, So our KMS server is running Server 2019, so the equivalent update for that OS is KB5010427?
Has anyone tried that and got it working with the 2022KMS Host key?
- Thank you for your useful and exact reply, It seems to be working in our environment.
- If you have many devices to manage I would still plea to use VAMT for KMS or ADBA Compliance, Key Management and activation. Saves you lot of work with slmgr.
- I can confirm that after installing KB5010421, rebooting and slmgr /ato, LTSCB/LTSC Clients can now activate.
- Indeed.... WTF.
After Installing KB5010421, reboot and slmgr /ato Activation is working! - Did you try to reactivate the CSVLK after installing the updates?
because the KMS Host Server licenses are indeed updated with 2022.01 C release to support LTSB 2016 / LTSC 2019 clients - What do you mean exactly? KB5010421 has to be applied?
Just tested, does not work. - The KMS down-level keys were serviced for Windows Server 2022 is 2022.01 C release, so this should be working once the 1C update (or 2B security update) is applied. If the issue still occurs after applying the update, please provide logs.
