Forum Discussion
Server 2022 KMS host key bug; Can't activate Win10 Enterprise LTSB/LTSC
We recently dropped our new Server 2022 KMS host key onto our KMS server. After the necessary update to accept the 2022 key and activating the new 2022 host key, we were able to activate our most com...
Well well... Server 2022 KMS Key bug strikes again.
The Server 2019 February 2022 Updates fixed the problem. UNFORTUNATELY, the Server 2019 March 2022 Updates broke KMS again. I was hoping that the April updates would fix that, nope.
Windows 10 Enterprise LTSC 2019, 2021 and Windows 10 Enterprise 2016 LTSB cannot activate again. Other versions activate just fine.
Should I upgrade my KMS Server to Server 2022 and expect the problem to go away?
Anyone experiencing the same problem again?
The Server 2019 February 2022 Updates fixed the problem. UNFORTUNATELY, the Server 2019 March 2022 Updates broke KMS again. I was hoping that the April updates would fix that, nope.
Windows 10 Enterprise LTSC 2019, 2021 and Windows 10 Enterprise 2016 LTSB cannot activate again. Other versions activate just fine.
Should I upgrade my KMS Server to Server 2022 and expect the problem to go away?
Anyone experiencing the same problem again?
It's not just you, ours is doing the exact same thing.
Issue was fixed after KB5010427 back in February, and I never looked back at it. Now that I see your comment, I tried activating a test Win10 10 Ent. LTSC 2019 VM, and nope. Failed to activate, back to square one all over again.
Good God, Microsoft...
Issue was fixed after KB5010427 back in February, and I never looked back at it. Now that I see your comment, I tried activating a test Win10 10 Ent. LTSC 2019 VM, and nope. Failed to activate, back to square one all over again.
Good God, Microsoft...
- ajc, I suggest you try flushing the DNS on your KMS server (ipconfig /flushdns) and then run on the KMS slmgr.vbs /ato. Then try again the activation on your Windows 10 LTSC.
TBH what threw me off is that the GUI said that KMS was successfully activated, but via the CLI it wasn't.
Running the 2 steps above fixed my problem.
I am wondering if the march updates messed up something on the dns cache on KMS.- Solid, that worked thanks! I missed your response above saying as much, happy it was that simple.
Now if it would quit doing that, that'd be fine too. 😛ajc196Armando_Rivera great to see it is solved. And once again "It's always DNS"
