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 common OS types in a quick test afterward -- Win10 Education 21H1, Server 2022, Server 2019, etc.
In the next few days, and even more today, we've been getting reports that Win10 Enterprise LTSB/LTSC across some signage devices and laboratory machines stopped activating. Sure enough, I could reproduce the issue from a known good network.
Just this morning I spun up entirely fresh VMs and verified all the above is still reproducible with the following results:
Windows Server 2022 = Successfully activated
Windows Server 2019 = Successfully activated
Windows Server 2016 = Successfully activated
Windows 10 Education 21H1 = Successfully activated
Windows 10 Enterprise LTSC 2021 = FAILED ACTIVATION (0xC004F074: License server reported that the computer could not be activated.)
Windows 10 Enterprise LTSC 2019 = FAILED ACTIVATION (0xC004F074: License server reported that the computer could not be activated.)
Windows 10 Enterprise 2016 LTSB = FAILED ACTIVATION (0xC004F074: License server reported that the computer could not be activated.)
Windows 10 Enterprise 2015 LTSB = Successfully activated (odd, after the previous two)
Windows 8.1 Enterprise = Successfully activated
Windows 7 Enterprise = Successfully activated
Anyone else seeing this or could possibly test and confirm? I feel like this **has** to be a bug with 2022 host keys, but it's so new that I can't find anyone else in the same boat. I have a Premier ticket open for this.
- FWIW, I've had at least 2 others confirm the same behavior over on Reddit:
https://reddit.com/r/sysadmin/comments/plq1hw/heads_up_windows_server_2022_kms_host_keys_seem - Error code 0xC004F074 indicates that Key Management Service [1] could not be contacted during the activation procedure.
Ensure the Windows 10 LTSC client has proper cummilative updated.
Hardcode the software protection KMS registry on the client devices to KeyManagementServiceName to refer the KMS Hostname
Registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform
use slmgr /skms KMSservername
slmgr /ato
if problem repeats use VLMSC management on KMS server and locate the device search and activate forcibly else redeploy the client device with proper updates.
By theory when you host VLMSC on 2022 OS then following clients will be supported.
https://docs.microsoft.com/en-us/windows-server/get-started/kms-activation-planning
CSVLK group CSVLK can be hosted on Windows editions activated by this KMS host
Volume License for Windows Server 2022
Windows Server 2022
Windows Server 2019
Windows Server 2016
Windows Server 2022 (all editions)
Windows Server Semi-Annual Channel
Windows Server 2019 (all editions)
Windows Server 2016 (all editions)
Windows 10 Enterprise LTSC 2019
Windows 10 Enterprise LTSC N 2019
Windows 10 LTSB (2015 and 2016)
Windows 10 Professional
Windows 10 Enterprise
Windows 10 Pro for Workstations
Windows 10 Education
Windows Server 2012 R2 (all editions)
Windows 8.1 Professional
Windows 8.1 Enterprise
Windows Server 2012 (all editions)
Windows Server 2008 R2 (all editions)
Windows Server 2008 (all editions)
Windows 7 Professional
Windows 7 Enterprise- Test cases were already being manually pointed to our host using slmgr /skms [host]:1688
Issues recurs on those editions while still fully patched. (Note that wholly unpatched downlevel OSs like Win7 and Win8.1, Win10 2015 LTSB activate fine)
