In my opinion, this is an unfixed bug in Windows 10 KMS Host. Any help or information about appropriate update/hotfix would be really appreciated. I found out we are not the only organisation with this problem. After wasting 1 hour time with MS phone support they confirmed this as a 'solution', which I find quite ridiculous and I'm afraid the 'genuine-again' status is
So far the only 'solution' (?) for me is SLMGR -REARM, restart, then Win7 reactivates again successfullyĪgainst KMS and becomes genuine again.
To call IT department asking 'Why is the background of my Windows black, saying my Windows is The 25 requests limit got exceeded soon and KMS host started to activate all KMS clients successfully, including new Win 10 clients.Ī few days later, Win 7 users (so far ONLY Win 7 users, not Win 8, 8.1 or 10) started KMS client machines (We have hundreds of machines, Winħ, 8, 8.1 and 10) started to connect to KMS server again. I installed an appropriate KMS host key and successfully activated new Win 10 Ent. Which worked for many years as KMS host without problems, to Win 10 Enterprise + installed all updates. In order to activate new Win 10 Enterprise in my organisation, I did in-place upgrade of Win 7 Enterprise,
