none
Windows 10 Enterprise KMS Host renders Windows 7 Enterprise KMS clients NOT GENUINE ! RRS feed

  • Question

  • Hello,

      in order to activate new Win 10 Enterprise in my organisation, I did in-place upgrade of Win 7 Enterprise, which worked for many years as KMS host without problems, to Win 10 Enterprise + installed all updates. I installed an appropriate KMS host key and successfully activated new Win 10 Ent. KMS host. KMS client machines (We have hundreds of machines, Win 7, 8, 8.1 and 10) started to connect to KMS server again. The 25 requests limit got exceeded soon and KMS host started to activate all KMS clients successfully, including new Win 10 clients.

      A few days later, Win 7 users (so far ONLY Win 7 users, not Win 8, 8.1 or 10) started to call IT department asking "Why is the background of my Windows black, saying my Windows is not genuine ??". We have 3-5 such incidents everyday.

      So far the only "solution" (?) for me is SLMGR -REARM, restart, then Win7 reactivates again successfully against KMS and becomes genuine again. MGAdiag tool then returns 0 - genuine. 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 only temporary.

      I found out we are not the only organisation with this problem. Any help or information about appropriate update/hotfix would be really appreciated. In my opinion, this is an unfixed bug in Windows 10 KMS Host.

    Regards,
    George


    Monday, September 14, 2015 2:51 PM

All replies

  • Hello,

    Do you have the output of the MGA diag tool from a Windows 7 machine that is failing and can you make it available, including the log files?

    Does slmgr -ato work rather then the almgr -rearm?


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, September 14, 2015 5:58 PM
  • Hello,

      slmgr -ato doesn't work until I execute slmgr -rearm + restart. (Error: Windows is running within the non-genuine notification period.)

      I also found out how to make Win7 not genuine "on demand" - just by going to http://www.microsoft.com/Genuine/validate

      Windows validation gets always interrupted ('Windows validation was interrupted. The validation service is not available at this time. Please try again later.") and then genuine status immediately changes to not genuine.

      MGA diag report and slmgr -dlv of not genuine Win7 attached.

    Regards,
    George

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    
    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a7
    Windows Product Key: *****-*****-2VJC9-XBBR8-HVTHH
    Windows Product Key Hash: k/l/EMDQdwK9OvdCkPtHG1YdosE=
    Windows Product ID: 00392-918-5000002-85616
    Windows Product ID Type: 1
    Windows License Type: KMS Client
    Windows OS version: 6.1.7601.2.00010100.1.0.004
    ID: {A9543A80-F977-4528-81F9-A7DEE0D92375}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Enterprise
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.150715-0600
    TTS Error: 
    Validation Diagnostic: 
    Resolution Status: N/A
    
    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    
    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002
    
    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002
    
    OGA Data-->
    Office Status: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3
    
    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed
    
    File Scan Data-->
    
    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{A9543A80-F977-4528-81F9-A7DEE0D92375}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.004</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-HVTHH</PKey><PID>00392-918-5000002-85616</PID><PIDType>1</PIDType><SID>S-1-5-21-1659762722-1119709416-546730148</SID><SYSTEM><Manufacturer>ASUS</Manufacturer><Model>All Series</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>2103</Version><SMBIOSVersion major="2" minor="8"/><Date>20140627000000.000000+000</Date></BIOS><HWID>CB1C0900018400F4</HWID><UserLCID>0405</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Europe Standard Time(GMT+01:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  
    
    Spsys.log Content: 0x80070002
    
    Licensing Data-->
    Software licensing service version: 6.1.7601.17514
    
    Name: Windows(R) 7, Enterprise edition
    Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
    Activation ID: ae2ee509-1b34-41c0-acb7-6d4650168915
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00392-00170-918-500000-03-1029-7601.0000-2422013
    Installation ID: 014893828262196774629086088725189935448914194141154895
    Partial Product Key: HVTHH
    License Status: Notification
    Notification Reason: 0xC004F200 (non-genuine).
    Remaining Windows rearm count: 3
    Trusted time: 11.9.2015 15:39:24
    Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.
    
    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C4A7
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 9:9:2015 10:51
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:
    
    
    HWID Data-->
    HWID Hash Current: KAAAAAAAAQABAAEAAAABAAAAAQABAAEAln3k7awOpK+0f7QOyqHI9g==
    
    OEM Activation 1.0 Data-->
    N/A
    
    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information: 
      ACPI Table Name	OEMID Value	OEMTableID Value
      APIC			ALASKA		A M I
      FACP			ALASKA		A M I
      HPET			ALASKA		A M I
      MCFG			ALASKA		A M I
      FPDT			ALASKA		A M I
      SSDT			Ther_R		Ther_Rvp
      SSDT			Ther_R		Ther_Rvp
      SSDT			Ther_R		Ther_Rvp
      SSDT			Ther_R		Ther_Rvp
      SSDT			Ther_R		Ther_Rvp
    
    

    C:\>cscript c:\windows\system32\slmgr.vbs -dlv
    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.
    
    Software licensing service version: 6.1.7601.17514
    
    Name: Windows(R) 7, Enterprise edition
    Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
    Activation ID: ae2ee509-1b34-41c0-acb7-6d4650168915
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00392-00170-918-500000-03-1029-7601.0000-2422013
    Installation ID: 014893828262196774629086088725189935448914194141154895
    Partial Product Key: HVTHH
    License Status: Notification
    Notification Reason: 0xC004F200 (non-genuine).
    Remaining Windows rearm count: 3
    Trusted time: 11.9.2015 15:41:56
    Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.
    


    Tuesday, September 15, 2015 9:29 AM
  • Hello,

    Are these brand new Windows 7 machines, attempting to activate for the first time?

    They are new KMS clients that have not activated via a KMS before according the above output.

    Can you make the application log available for download?

    Also output from the KMS host ( slmgr /dlv and application log would be useful.


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, September 15, 2015 5:20 PM
  • Hi,

    We hope your issue has been resolved, if you've found solution by yourself. We would appreciate it if you could share with us and mark it as answer. Your experience will help other community members facing similar problems.

    Regards,

    D. Wu


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Thursday, September 24, 2015 1:17 AM
    Moderator
  • Hello,

      these aren't new Win7 machines, the MGA diag report attached in my previous post originates from a machine which was installed in 2013 and running happily as a KMS client.

    Brand new Win7 machines behave as expected - they activate against KMS host successfully right after installation. By going to http://www.microsoft.com/Genuine/validate I can make them not genuine as mentioned above.

    Application logs from my KMS Host and the failed KMS client are available

    here

    slmgr -dlv report of the KMS host (Win10 Ent. 32b CZ on vSphere virtual machine) attached. I hope the czech letters and words won't puzzle you much.

    Regards,
    George

    C:\WINDOWS\system32>cscript slmgr.vbs -dlv
    Microsoft (R) Windows Script Host verze 5.812
    Copyright (C) Microsoft Corporation 1996-2001. Všechna práva vyhrazena.
    
    Verze služby SLS (Software Licensing Service): 10.0.10240.16384
    
    Název: Windows(R), Enterprise edition
    Popis: Windows(R) Operating System, VOLUME_KMS_W10 channel
    ID aktivace: 0724cb7d-3437-4cb7-93cb-830375d0079d
    ID aplikace: 55c92734-d682-4d71-983e-d6ec3f16059f
    Rozšířené PID: 03612-00206-390-043103-03-1029-10240.0000-2292015
    Kanál kódu Product Key: Volume:CSVLK
    ID instalace: 008680700733798352377671321986382092431395943721951021
    Adresa URL licence k použití:             https://activation-v2.sls.microsoft.com/SLActivateProduct/SLActivateProduct.asmx?configextension=Retail
    Adresa URL pro ověření: https://validation-v2.sls.microsoft.com/SLWGA/slwga.asmx
    Část kódu Product Key: 26J4X
    Stav licence: Licencováno
    Zbývající počet obnovení aktivačního období Windows: 1001
    Zbývající počet obnovení aktivačního období skladové jednotky (SKU): 1001
    Důvěryhodný čas: 11.9.2015 16:22:17
    
    V tomto počítači je povolena Služba pro správu klíčů.
        Aktuální počet: 50
        Naslouchání na portu: 1688
        Publikování DNS povoleno
        Priorita Služby pro správu klíčů: Normální
    
    Souhrnné požadavky přijaté Službou pro správu klíčů od klientů
        Přijaté požadavky celkem: 10246
        Přijaté neúspěšné požadavky: 340
        Požadavky se stavem licence Nelicencováno: 0
        Požadavky se stavem licence Licencováno: 2076
        Požadavky se stavem licence Počáteční poskytnutá lhůta: 215
        Požadavky se stavem licence Platnost licence vypršela nebo Hardware je mimo toleranci: 9
        Požadavky se stavem licence Poskytnutá lhůta pro neoriginální program: 0
        Požadavky pomocí služby Upozornění na stav licence: 7606


    • Edited by McClane74 Thursday, September 24, 2015 4:00 PM
    Thursday, September 24, 2015 3:56 PM
  • We're having exactly the same issue.. 

    this is one of the very few posts that describes the exact situation we're having but no answer :(


    Thursday, October 8, 2015 8:57 AM
  • We are also experiencing this, and have found the same workaround.  Hope we can get a proper resolution soon.
    Monday, October 19, 2015 6:12 PM
  • Hi George,

    do you have any news about this issue?

    Thanks


    M.

    Thursday, December 3, 2015 11:33 AM
  • Hi,

      I had no more patience to wait for Microsoft to fix their helter-skelter dud system. I moved the KMS host to Windows 7 Enterprise and installed KB3079821.This KB enables Win7 and WinServer 2008 R2 KMS hosts to activate Windows 10 and it wasn't available at the time of my upgrade to Win10 (Which was actually the reason for the upgrade).

     I have no more problems with not genuine systems now. Going to http://www.microsoft.com/Genuine/validate and launching the genuine test makes not genuine Win7 KMS clients genuine right away !

      And another, a bit off-topic MS "gotcha" - Due to another unfixed BUG I can't run KMS host for MS Office 2013 and MS Office 2016 on the same system ! 

      Microsoft, it really HURTS to manage your flagship products....

    Regards,
    George


    Monday, December 7, 2015 11:57 AM
  • I fully understand... We've found out, that impacted users do not come back after we rearm their Windows, so hopefully it was one-time operation and we can keep Windows 10 KMS host. Anyway we have escalated the issue and reopened the case with Microsoft.


    M.

    BTW: Fall update has changed KMS host to MAK client and lost information about KMS host for Office 2016 :( We have restored the host from a backup.


    • Edited by MStoppl Monday, December 7, 2015 12:14 PM
    Monday, December 7, 2015 12:11 PM
  • Does anyone know if this KB (https://support.microsoft.com/en-us/kb/3058168) will allow Windows 8 KMS hosts to activate Windows 10 Anniversary Update (build 1607)?

    We ran into an issue much like what this thread describes.  We have Office 2010 KMS clients, so the only version of Windows (non-server) that could act as a KMS host and be able to activate Office 2010 and Windows 10 was Windows 8 (after some hotfixes).  Then we found out that Windows 10 anniversary (1607) would not activate against that Windows 8 KMS host, and there was no hotfix, so we upgraded -- forgetting that we needed Windows 8 for the Office 2010 clients.  We decided to provide MAKs to those Office 2010 users.  Now, we find out that the Windows 10 KMS host is breaking our existing Windows 7 KMS clients.

    As if this whole activation process wasn't a burden on your users already, Microsoft.  It's just increasingly hostile being a Microsoft customer.

    Tuesday, October 18, 2016 6:47 PM
  • I installed a new KMS host on Windows server 2016.

    We had exactly the same problems. A lot Windows 7 clients became Non Genuine.

    I had to remove the new KMS host and revert back to our old Windows 2008 R2 KMS server.

    I activated Active based  Directory activation for windows 10 and windows 2016 clients.

    AD controllers are 2012 R2.

    I installed the "Windows Srv 2016 DataCtr/Std KMS" key for the Active based  Directory activation.


    Friday, October 21, 2016 8:20 AM
  • I installed a new KMS host on Windows server 2016.

    We had exactly the same problems. A lot Windows 7 clients became Non Genuine.

    I had to remove the new KMS host and revert back to our old Windows 2008 R2 KMS server.

    I activated Active based  Directory activation for windows 10 and windows 2016 clients.

    AD controllers are 2012 R2.

    I installed the "Windows Srv 2016 DataCtr/Std KMS" key for the Active based  Directory activation.


    I have had to do the same.  Very frustrating
    Thursday, November 3, 2016 8:04 AM
  • Were you able to solve this issue or find any further info on it? We also have a new KMS server on Windows Server 2016 and having such problems.
    Wednesday, November 9, 2016 1:55 PM
  • Have the same problem, and will be working with MS today. Noticed that doing a slmgr -rearm will allow for activation afterward, but not sure if it will cause systems to go non-genuine again after re-upping its activation later.
    Monday, November 14, 2016 7:30 PM
  • Try going to http://www.microsoft.com/Genuine/validate  and run validate process (at least twice, in case of error). In my case last year, I was able to make Win7 clients non-genuine again after rearm by this validation.

    I opened this thread more than 1 year ago. It seems Micro$oft still hasn't bothered to fix this. Moreover, this rubbish seems to be adopted by KMS host in new server 2016. Maybe they just need to drive Win7 out of clients asap.

    Tuesday, November 15, 2016 9:46 AM
  • Have the same problem, and will be working with MS today. Noticed that doing a slmgr -rearm will allow for activation afterward, but not sure if it will cause systems to go non-genuine again after re-upping its activation later.

    You should. As far as I understand, you can rearm KMS-activated system more than 3 times. For me rearming ~20 machines was OK, 2 machines lost ability to activate again.

    Just migrated back to 2012 R2 again. 

    Right now AD-based activation works much better. Anyway, if you will be able to solve this with MS support, please let people know. Thanks!

    Friday, November 25, 2016 11:10 AM
  • Have the same problem, and will be working with MS today. Noticed that doing a slmgr -rearm will allow for activation afterward, but not sure if it will cause systems to go non-genuine again after re-upping its activation later.

    You should. As far as I understand, you can rearm KMS-activated system more than 3 times. For me rearming ~20 machines was OK, 2 machines lost ability to activate again.

    Just migrated back to 2012 R2 again. 

    Right now AD-based activation works much better. Anyway, if you will be able to solve this with MS support, please let people know. Thanks!

    Unfortunately KMS activation will completely fail after 3 re-arms are used.  We are running into this in our environment.  We have to either re-image the machines or use a registry deletion script to reset the re-arm count.

    Has anyone figured out why KMS on 2016 is causing this?  Our previous server was 2008R2 and we never had these issues?  Can Microsoft chime in with some kind of acknowledgement?  As it is, TechNet has confirmed that the activation GUI is also broken and have suggested that you use the CLI to activate.  So is KMS on server 2016 completely useless then?  If they can confirm I would at least start rolling servers back to 2012R2.

    Also, after manually rearming all of my windows 7 machines, I'm worried that this will occur again when it's time to reactivate them again.  Can anyone shed some light on this?  I'm really hoping that won't be the case, because this upgrade to 2016 has been a nightmare so far, I'm hoping it will not continue.

    Tuesday, November 29, 2016 3:07 PM
  • Really Microsoft, Really!?!?!  Why even have the option to install a kms host for legacy clients on 2016 server then?

    This is from a TechNet blog, but it won't allow me to post a link yet.

    blogs.technet.microsoft.com/askpfeplat/2016/10/24/kms-activation-for-windows-server-2016/

    "The recommendation at this point is to leave your existing KMS system alone.  Whether it is running on Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2, continue to service the machine via security and quality updates.  Allow your KMS system to activate down-level operating systems and Office installs (Windows 7, Windows Server 2008/2008 R2, and Office 2010).  Utilize Active Directory Based Activation (ADBA) for all new clients (Windows 8, 8.1, Windows Server 2012, 2012 R2, 2016, Windows 10, Office 2013, and Office 2016)."

    So there is the answer, it's not recommended to activate Windows 7 PC's with Server 2016 KMS hosts.


    • Edited by bakerr12304 Wednesday, November 30, 2016 3:42 PM
    Wednesday, November 30, 2016 3:42 PM
  • Unfortunately KMS activation will completely fail after 3 re-arms are used.

    This is not true.

    You can rearm an unlimited number of times if you have a successful KMS activation between rearming operations. The KMS activation will reset the counter, regardless of what shows in slmgr /dlv, which is correct if it shows 1 left.

    You may have sysprepped with SkipRearm which is incorrect, but even so, you can fix it by rearming after build.

    But the issue with Windows 10 / 2016 KMS host is real, with no relation at all to the number of activations available.

    Monday, January 9, 2017 10:17 AM
  • Why in the WORLD is this still an issue? I've been dealing with this since the moment we rolled out our new Server 2016 based KMS server and my users are starting to really get upset about it. I'm close to having to sandbag the whole thing and go back to Server 2012 R2 KMS.

    Microsoft....please focus some energy on this. It's insane that Enterprise IT departments are having to deal with this. Let's see a fix asap.

    Wednesday, January 11, 2017 5:41 PM
  • I would like to see a fix for this issue as well.
    Thursday, January 12, 2017 6:03 PM
  • This is a very frustrating issue.  We also have a new Server 2016 KMS host for a large enterprise mixed OS environment.  The calls have been trickling in.  I suppose we can create a script to rearm all Windows 7 clients but why can't Microsoft release some sort of fix for this already. 
    • Edited by G-Eazy Wednesday, January 18, 2017 4:22 AM
    Tuesday, January 17, 2017 6:08 PM
  • Can confirm this is happening even after a rearm of some of our Windows 7 systems. I will now be forced to remove and downgrade our KMS server to try and fix this issue. Thanks a TON (INTENSE sarcasm) Microsoft for being able to A) properly program your own software (did you even test this??) and B) communicate on working towards an resolution on this for the community. I should open a ticket and make them fix it, but I can no longer take the headaches of the daily pounding I am getting from our staff and students getting a non genuine message and complaining.

    Get on it fellas, this should be pretty embarrassing for you.......


    Wednesday, January 18, 2017 3:20 PM
  • This is the fix I was provided from MS because rearm does not appear to work half the time on our older Windows 7 images for some reason.  I will probably put this in a bat file and blast it out with SCCM.  I hope the activation issues don't come back when the clients check back in to the KMS server a few months from now... 

    net stop sppsvc 
    del %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-0.C7483456-A289-439d-8115-601632D005A0 /ah 
    del %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-1.C7483456-A289-439d-8115-601632D005A0 /ah 
    del %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\tokens.dat 
    del %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\cache\cache.dat 
    net start sppsvc 
    slmgr /ato


    • Proposed as answer by Eric Zhong Wednesday, January 9, 2019 2:55 PM
    Wednesday, January 25, 2017 4:43 PM
  • Thank you G-Eazy, That helped me.

    The conclusion I have is that KeyManagementServices (KMS) for Windows 10 and Server 2016 doesn't.

    My Configuration:

    Server 2008R2 Domain level (No AD Activation)

    Server 2008R2 KMS servers (No Windows10 or 2016 Activation)

    The Volume Activation role didn't install properly on our 2016 server (errors).  Not much documentation about the VAMT which is  in the Windows 10 ADK which is critical for success.  For folks who successfully installed the role did it include that installation of VAMT ..if it didn't than it seems absurd that it didn't.

    Wow, I try not to be critical (and yes I should probably be @ 2012R2 domain level) but this feels like it has been harder that it should be for more people than just me.

    Friday, February 3, 2017 4:06 PM
  • Hi All

    Anyone know if the issue with Server 2016 KMS hosts and Windows 7 clients is resolved? I hope many months later the recommendation is not still to leave KMS hosts on previous Server OS versions.

    Thanks in advance

    Friday, May 12, 2017 2:34 AM
  • Hello,

    Yes this is resolved.


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Friday, May 12, 2017 4:10 PM
  • "Yes this is resolved."

    That sounds nice but how exactly? What update/fix needs to be installed?

    A bit more information would be very welcome.

    Thanks in advance.

    Sunday, May 21, 2017 7:31 PM
  • Hello,

    The change was done on the activation servers so you do not need to install a fix\update


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, May 22, 2017 7:45 PM
  • Darrel, thanks for your swift reply. I appreciate that.

    I'm glad I do not have to update any of our 2500 Win7 computers. That is a relief!
    But apparently something has to be done on the Win2K16 KMS activation server I have?

    Or do I misunderstand your remark and this was resolved on the Microsoft back-end and our new KMS server does not need to be updated at all?

    Regards,
    Marcel

    Thursday, May 25, 2017 5:31 AM
  • Hello,

    This is resolved on the Microsoft back-end and your KMS server does not need to be updated.


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Friday, May 26, 2017 4:25 PM
  • Hi Darrell,

    This is still a problem for me. I have a Windows Server 2016 KMS host that will not activate Windows 7 clients. Is there something I need to do on the server? On the KMS host I currently have Windows 10 Education key, Windows Server 2016 Key and Office 2016 key installed. It will not allow me to install the Windows 7 KMS key, but I don't believe I need that, is that correct?

    No Windows 7 clients are activating.

    Thanks

    Toby

    Wednesday, August 30, 2017 11:01 AM
  • Hello Topy,

    That is a different issue.

    You should only need the Windows Server 2016 and the Office 2016 Keys installed.

    What is the error message that the Windows 7 clients are getting?

    Can you post the output of the slmgr /dlv?


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, August 30, 2017 3:52 PM
  • Hi Darrell,

    Thanks for responding. The output from /dlv is now showing as activated because yesterday I actually setup another KMS host running Windows Server 2012. This activated the Windows 7 clients fine.

    Anyway, I have tired to get the out of /dlv for you by setting the client to point to the Windows Server 2016 again using slmgr -skms

    Below is the output for /dlv (disregard the fact that it says activated thats just because it was pointing to the 2012 server)

    Microsoft (R) Windows Script Host Version 5.8

    Copyright (C) Microsoft Corporation. All rights reserved.

    Software licensing service version: 6.1.7601.17514

    Name: Windows(R) 7, Professional edition
    Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
    Activation ID: b92e9980-b9d5-4821-9c94-140f632f6312
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00170-868-000000-03-2057-7600.0000-2232015
    Installation ID: 016125809992636143610370612955326466814380801531511322
    Partial Product Key: GPDD4
    License Status: Licensed
    Volume activation expiration: 258180 minute(s) (179 day(s))
    Remaining Windows rearm count: 1
    Trusted time: 31/08/2017 08:11:52

    Key Management Service client information
        Client Machine ID (CMID): 2ef80b7d-3e61-49c4-a181-51226cf681fa
        Registered KMS machine name: dc01.*****.school:1688
        KMS machine extended PID: 06401-00206-271-840929-03-2057-9600.0000-2422017
        Activation interval: 120 minutes
        Renewal interval: 10080 minutes
        KMS host caching is enabled

    Also when I run /ato the error I get is, Error 0xC004F074 Computer could not be activated. The Key Management Service (KMS) is unavailable.

    As soon as I point it back to the Windows 2012 Server it activates straight away. Both servers have exactly the same firewall settings as they are controlled by Group Policy. Any ideas?

    Many Thanks

    Toby


    • Edited by Toby2017 Friday, September 1, 2017 9:31 AM
    Thursday, August 31, 2017 7:28 AM
  • Hello Toby,

    I think your issue hasn't been resolved yet. At least, not Automatically.

    I've found the following MS-article:

    https://support.microsoft.com/en-us/help/4032981/powershell-script-for-windows-7-non-genuine-issue-is-available

    I have the same issue as you, and I try this PowerShell Script to get it work. I don't know at the Moment if it really works... Just want to letting you know...

    Patrik

    • Proposed as answer by Cantoris Wednesday, January 9, 2019 2:45 PM
    Friday, September 29, 2017 2:18 PM
  • This was very helpful! Thank you for posting it!!
    Friday, September 29, 2017 6:27 PM
  • Thanks Patrik - while the powershell script did not work for me, the manual process did.  One caveat, the first two files in the list are hidden, so you will have to use the /ah switch to delete them:

    From elevated cmd prompt:
    net stop sppsvc
    del %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-0.C7483456-A289-439d-8115-601632D005A0 /ah
    del %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-1.C7483456-A289-439d-8115-601632D005A0 /ah
    del %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\tokens.dat
    del %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\cache\cache.dat
    net start sppsvc
    slmgr /ato

    Hope this helps someone.

    Gary

    • Proposed as answer by Cantoris Wednesday, January 9, 2019 2:45 PM
    Wednesday, November 28, 2018 10:16 PM