Hello,
See if anything from here helps you:
https://learn.microsoft.com/en-us/windows-server/get-started/activation-troubleshoot-kms-issues
Regards.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I built a windows 10 1803 system a couple years ago to run as kms host for windows 10 vdi. It has been working fine. However, I just updated to 2004 and now it is broke. After the last reboot it said windows is not activated. it says no kms server could be contacted and to check the application log (when i ran slmgr /ato). The application log only shows that an activation request was sent to the kms server (itself) but that's it. I do have a snapshot and can revert back to 1803. I did this a couple times already (including going to 1903) and won't activate after updating.
Hello,
See if anything from here helps you:
https://learn.microsoft.com/en-us/windows-server/get-started/activation-troubleshoot-kms-issues
Regards.
See if anything from here helps you:
not really...
Is the KMS client computer activated?
Since many are showing x days left until reactivation, built a new windows 10 system. Ran slmgr /ato and failed (0xC0040F74 no kms server could be contacted).
Verify that the KMS activation threshold is met.
It is. Clients were activating before the kms host was updated to more recent versions (tried 1903 and 2004).
On the KMS host computer, look in the KMS event log for event ID 12290.
Only has 12288 showing it sent an activation request to the kms server.