KMS Server (Windows 10 Activation) borked after April 2022 Server updates

[timbo343]

We ran the latest round of updates over the easter holidays and our KMS server is on one of our Virtual DCs - this is Windows Server 2019 Server.

 

We have been testing the roll out of our image (windows 10) and noticed it isn't licensing against the KMS server. Looking into this, none of the machines on the domain are auto licensing themselves against the server when we run slmgr -ato yet our Office KMS works without any issues.

 

Our other servers work as expected when we run slmgr -ato on them and find the KMS server without any issues.

 

We found something on reddit

which points to an update which is borking the KMS.

 

I'd be interested to know if anyone has applied either the March 2022 or April 2022 update and are having the same issue.

 

So the issue is, running slmgr -ato on a windows 10 machine where the KMS is hosted on a patched Windows Server 2019, the Windows 10 machine reports the KMS server cannot be reached.

 

The Reddit article states microsoft couldn't fix the issue but one of the poster's mentioned deactivating and reactivating the KMS host - something i don't want to do.

[timbo343]

Ok so it seems the Windows Server 2022 KMS key doesn't work on the Windows 10 clients yet the Windows Server 2019 KMS code works.

 

This seems to be after applying the latest updates to our Windows Server 2019 KMS host.

Edited April 27, 2022 by timbo343

[chaplic]

I had something similar after I did an inplace upgrade from server 2019 to 2022 which ran KMS. If you dig through licensing.microsoft.com there's a link to raise a ticket, I just asked for an updated KMS host key