Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Windows 7 Professional Deactivation COA SLP RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello all,

    I have seen similar issues reported here but not been able to glean enough information to help me resolve my own problems, hoping to get some insights and get this cleared up for my user ASAP.

    The machine seems to have stopped recognizing the activation out of the blue. The only update around the time of deactivation was to the Windows AV definitions (KB915597, 1.293.949.0). After attempting to reactivate with the license code on the machine and failing, I reached out to Microsoft and then at their recommendation HP to see if anyone could help. HP recommended I reinstall Windows on the machine, which I would really like to avoid doing if at all possible.

    Below is the MGADIAG report. Any help would be greatly appreciated.

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a2
    Windows Product Key: *****-*****-M8R2G-MBYQB-P2GYK
    Windows Product Key Hash: VFLFsOqcYgU8FmxxWxc46GWlN0c=
    Windows Product ID: 00371-OEM-9310744-40930
    Windows Product ID Type: 8
    Windows License Type: COA SLP
    Windows OS version: 6.1.7601.2.00010100.1.0.048
    ID: {AD3878DC-50B9-449D-AE58-9B4F78D0179B}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Professional
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_ldr_escrow.190320-1700
    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\Internet Explorer\iexplore.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>{AD3878DC-50B9-449D-AE58-9B4F78D0179B}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-P2GYK</PKey><PID>00371-OEM-9310744-40930</PID><PIDType>8</PIDType><SID>S-1-5-21-517312108-1949140658-1005477477</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Compaq 8100 Elite SFF PC</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>786H1 v01.13</Version><SMBIOSVersion major="2" minor="6"/><Date>20110714000000.000000+000</Date></BIOS><HWID>489D3107018400FC</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-BPC</OEMTableID></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, Professional edition
    Description: Windows Operating System - Windows(R) 7, OEM_COA_SLP channel
    Activation ID: da22eadd-46dc-4056-a287-f5041c852470
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00186-107-440930-02-1033-7601.0000-1272019
    Installation ID: 007456899102466676077952530806886600820855882315970050
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
    Partial Product Key: P2GYK
    License Status: Notification
    Notification Reason: 0xC004F200 (non-genuine).
    Remaining Windows rearm count: 1
    Trusted time: 5/7/2019 12:15:58 PM

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C4A2
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 5:6:2019 12:21
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: LgAAAAEAAQABAAIAAAACAAAAAQABAAEAln2ss2wGmJH4gJbZLFGmYMjVVHJcXQ==

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x20001
    OEMID and OEMTableID Consistent: yes
    BIOS Information: 
      ACPI Table Name OEMID Value OEMTableID Value
      APIC COMPAQ IBEXPEAK
      FACP COMPAQ IBEXPEAK
      HPET COMPAQ IBEXPEAK
      MCFG COMPAQ IBEXPEAK
      ASF! COMPAQ IBEXPEAK
      TCPA COMPAQ IBEXPEAK
      SLIC HPQOEM SLIC-BPC
      DMAR COMPAQ IBEXPEAK

    Thursday, May 9, 2019 4:50 PM

Answers

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    With internet access on the system, from an elevated Command Prompt, run the following:

    slmgr.vbs -ato

    It will either be successful or it will show to you a message with a command to run. If it is not successful, post the results here and we can see what it could be.

    Thursday, May 9, 2019 5:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Tripredacus,

    I ran command and received a an error 0xC004C003 The activation server determined the specified product key is blocked.

    Anything I can do here? I'm not sure what would've caused this key to be suddenly blocked from my end.

    Friday, May 10, 2019 1:55 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Product key on the COA should work, but there are some reasons why it wouldn't.

    Did you record what the active product key was before putting in the one from the COA? That original key that HP put into the OS should be the one in there, and not the one from the COA.

    The things that you can do at this point:

    1. Put back in the original key that was in the OS before, reboot, run slmgr -ato again and if it fails, post error code and new MGADiag report.

    2. Run slui 4 and go through telephone activation using the product key on the COA.

    Friday, May 10, 2019 4:41 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    The Product Key has been blocked by Microsoft - probably because of too many activations on too many machines.

    Is this the Key on the COA sticker on the machines case?? - if not, then change the Key to that, and all should be well.

    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Friday, May 17, 2019 3:49 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi @Tripredacus,

    Thanks for your response. Attempting to work through your steps, I don't believe I have the original key recorded as it was injected directly from the BIOS- if this is the case, to restore the machine is it possible that I will have to reinstall Windows to have it auto activate? I ask this because inputting the COA key via telephone resulted in the same error. I did this after running slui 4 in the elevated prompt.

    Thanks again.

    Wednesday, May 22, 2019 12:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hey Noel,

    Thank you for your response/time. I had spoken with Microsoft about the issue and they advised me to reach out to the manufacturer saying that it wasn't blocked by them. Is there a line in the MGADiag you don't mind showing me that determines where the block is coming from?

    BTW, I did attempt to activate with the COA and had no luck.

    Thanks again.

    Wednesday, May 22, 2019 12:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    There are two crucial lines in the report...

    Cached Online Validation Code: 0xc004c4a2

    and

    Notification Reason: 0xC004F200 (non-genuine).

    Unfortunately, neither give a reason as such -

    The first simply means that the Key is blocked - "

    Genuine Validation determined the product key has been blocked.

    The second means that it is 'not genuine'  - usually because of the first.

    MS are the only people with authorisation to block a Key - so they are the ones who will if necessary have to issue a replacement Key (Keys cannot be 'un-blocked', for security reasons)

    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Wednesday, May 22, 2019 1:58 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi @Tripredacus,

    Thanks for your response. Attempting to work through your steps, I don't believe I have the original key recorded as it was injected directly from the BIOS- if this is the case, to restore the machine is it possible that I will have to reinstall Windows to have it auto activate? I ask this because inputting the COA key via telephone resulted in the same error. I did this after running slui 4 in the elevated prompt.

    Thanks again.

    This isn't the case. Windows 7 does not use a product key in the BIOS. HP puts their key into the OS, which should show up in either of the partials in the MGADiag report. The partials in your paste above have the wrong key. I will leave it to Noel to determine whether or not it is proper to post what that key is. I believe technically it is not supposed to be public record, however it was leaked years ago and is easily found online.

    If you reinstall, make sure to use the HP branded recovery DVD. It should not ask for a product key and should automatically activate.

    In a case where the COA key is blocked, there is nothing that can be done unfortunately. Now, that COA is only the proof of license.

    • Edited by Tripredacus Wednesday, May 22, 2019 4:12 PM
    Wednesday, May 22, 2019 4:10 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    The OEM_SLP Keys are considered public domain- so there's no problem with posting them.

    It may be worth a try to use it - although I suspect that it will fail because the proper licenses aren't present in the OS..

    The HP Key for Win 7 Pro is

    74T2M-DKDBC-788W3-H689G-6P6GT

    If you change the Key to that, then reboot, it should automatically activate (but I suspect that it will fail)

    If you then run a new MGADiag report it may tell us a little more.

    olmboyo

    Can you check that the COA sticker on the case is actually for Windows 7 Professional?

    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.


    • Edited by Noel D PatonModerator Thursday, May 23, 2019 10:56 AM correct typo - and attempt to correct formatting!
    Thursday, May 23, 2019 10:56 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for that info. The documentation doesn't make it entirely clear what domain those keys are in, other than being included with NDA materials, the pages with the keys themselves are not marked as such.

    Regarding this particular topic, it should "activate" properly as the marker is present and the BIOS information is valid.

    Thursday, May 23, 2019 4:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Please try the troubleshooting tips offered here.

    Carey Frisch

    Friday, May 24, 2019 4:41 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Although the error codes are similar, the cause is NOT that referred to in that article, which is about KMS Volume Activation failures, rather than OEM or COA SLP activation.

    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Friday, May 24, 2019 3:15 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    The BIOS information may well be correct - but the necessary licences are only present in the OS when it was installed using the manufacturer's Recovery media (or from the master copy in their plant)

    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Friday, May 24, 2019 3:18 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Any update with your success/failure??

    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Friday, May 31, 2019 3:23 PM
    Moderator