none
7 Not genuine - but I have a valid key RRS feed

  • Question

  • Hi, I bourght a new computer with Windows 7 Professional and it is activated etc etc. After a few months it starts complaining that its not genuine - tried a few of the normal sites, which frankly all end up the same - go and buy another copy! Not really what I need frankly.  After a bit of checking I finally realised that the activation key visible in the properties of computer and the key on the licencing label stuck to the machine don't actually match - great! So my question in short is how can I enter the real key without going through a complete re-install?

    thanks CHDJA

    Sunday, November 7, 2010 5:04 PM

Answers

  • Hi, I bourght a new computer with Windows 7 Professional and it is activated etc etc. After a few months it starts complaining that its not genuine - tried a few of the normal sites, which frankly all end up the same - go and buy another copy! Not really what I need frankly.  After a bit of checking I finally realised that the activation key visible in the properties of computer and the key on the licencing label stuck to the machine don't actually match - great! So my question in short is how can I enter the real key without going through a complete re-install?

    thanks CHDJA


    See Carey's post and respond with the MGA Diagnostic report but here is a little background which was posted by Darin Smith MSFT to explain the differences in the product keys you are seeing:
     

    "Computers, which are built by large manufactures that come with Windows Pre-Installed, come with two (2) Product Keys:

    A)   OEM SLP: This key comes pre-installed in Windows, when it comes from the Factory. This key is geared to work with the OEM Bios Flag found only on that Manufacturer's computer hardware. So when Windows was installed using the OEM SLP key (at the factory) Windows looks at the motherboard and sees the proper OEM Bios Flag (for that Manufacturer and that version of Windows) and Self-Activates. (that's why you did not need to Activate your computer after you brought it home)

     

    B)    COA SLP: This is the Product key that you see on the sticker on the side (or bottom or sometimes in a laptop's battery compartment) of your computer. It is a valid product key, but should only be used in limited situations (such as this case when the OEM SLP key stops self-activating for whatever reason). The key must be activated by Phone.

    (Note: All manufacturers that use the OEM SLP system are required by contract to include a Certificate of Authenticity (COA) sticker, that has a COA SLP key, on the computer."
    • Marked as answer by Darin Smith MS Monday, November 8, 2010 10:13 PM
    Sunday, November 7, 2010 8:07 PM

All replies

  • The Product ID shown in Computer Properties is not the Product Key.

    To help us analyze and troubleshoot a non-genuine notification issue you may be experiencing, please download and run the Microsoft Genuine Advantage Diagnostics Tool. 

    Once you run the tool, click on the Continue button, then click on the Copy button and paste the report into your post, along with your question. 

    Thank you!

     


    Carey Frisch
    Sunday, November 7, 2010 6:08 PM
    Moderator
  • Hi, I bourght a new computer with Windows 7 Professional and it is activated etc etc. After a few months it starts complaining that its not genuine - tried a few of the normal sites, which frankly all end up the same - go and buy another copy! Not really what I need frankly.  After a bit of checking I finally realised that the activation key visible in the properties of computer and the key on the licencing label stuck to the machine don't actually match - great! So my question in short is how can I enter the real key without going through a complete re-install?

    thanks CHDJA


    See Carey's post and respond with the MGA Diagnostic report but here is a little background which was posted by Darin Smith MSFT to explain the differences in the product keys you are seeing:
     

    "Computers, which are built by large manufactures that come with Windows Pre-Installed, come with two (2) Product Keys:

    A)   OEM SLP: This key comes pre-installed in Windows, when it comes from the Factory. This key is geared to work with the OEM Bios Flag found only on that Manufacturer's computer hardware. So when Windows was installed using the OEM SLP key (at the factory) Windows looks at the motherboard and sees the proper OEM Bios Flag (for that Manufacturer and that version of Windows) and Self-Activates. (that's why you did not need to Activate your computer after you brought it home)

     

    B)    COA SLP: This is the Product key that you see on the sticker on the side (or bottom or sometimes in a laptop's battery compartment) of your computer. It is a valid product key, but should only be used in limited situations (such as this case when the OEM SLP key stops self-activating for whatever reason). The key must be activated by Phone.

    (Note: All manufacturers that use the OEM SLP system are required by contract to include a Certificate of Authenticity (COA) sticker, that has a COA SLP key, on the computer."
    • Marked as answer by Darin Smith MS Monday, November 8, 2010 10:13 PM
    Sunday, November 7, 2010 8:07 PM
  • Hi Carey,

    I hope I have given you here what you were expecting and that it helps you understand the problem - It sure doesn't mean a right lot to me other than it looks like I don't understand why ther's a problem!

    thanks CHDJA

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

    Validation Code: 0x8004FE21
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-GM2YY-R2KTT-43HG8
    Windows Product Key Hash: UhVqQM4C3ocWWq4h2L4psSCs0pU=
    Windows Product ID: 55041-OEM-8992671-00282
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7600.2.00010100.0.0.048
    ID: {7179B102-17AD-485E-AE66-69B143A8A07F}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows 7 Professional
    Architecture: 0x00000009
    Build lab: 7600.win7_gdr.100618-1621
    TTS Error:
    Validation Diagnostic:
    Resolution Status: N/A

     

    Tuesday, November 9, 2010 9:34 PM
  • Hi Carey,

    I hope I have given you here what you were expecting and that it helps you understand the problem - It sure doesn't mean a right lot to me other than it looks like I don't understand why ther's a problem!

    thanks CHDJA

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

    Validation Code: 0x8004FE21
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-GM2YY-R2KTT-43HG8
    Windows Product Key Hash: UhVqQM4C3ocWWq4h2L4psSCs0pU=
    Windows Product ID: 55041-OEM-8992671-00282
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7600.2.00010100.0.0.048
    ID: {7179B102-17AD-485E-AE66-69B143A8A07F}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows 7 Professional
    Architecture: 0x00000009
    Build lab: 7600.win7_gdr.100618-1621
    TTS Error:
    Validation Diagnostic:
    Resolution Status: N/A

     


    Unfortunately you didn't provide the entire report.  Instead of just the first part you need to click Copy after the report first shows.  That will copy the entire report and allow Carey or someone else to tell you exactly what has happened.  The Validation code and Cached code does help some but there is other information further down that may explain exactly what is happening.
    Wednesday, November 10, 2010 4:10 AM
  • Hi, thanks for the replies - here is the rest report again - hope it's all here this time around, maybe someone can tell me what is the issue please?

     

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

    Validation Code: 0x8004FE21
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-GM2YY-R2KTT-43HG8
    Windows Product Key Hash: UhVqQM4C3ocWWq4h2L4psSCs0pU=
    Windows Product ID: 55041-OEM-8992671-00282
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7600.2.00010100.0.0.048
    ID: {7179B102-17AD-485E-AE66-69B143A8A07F}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows 7 Professional
    Architecture: 0x00000009
    Build lab: 7600.win7_gdr.100618-1621
    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: 103 Blocked VLK
    Microsoft Office Enterprise 2007 - 103 Blocked VLK
    2007 Microsoft Office system - 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 77F760FE-153-80070002_7E90FEE8-175-80070002_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_B4D0AA8B-920-80070057

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\Mozilla Firefox\firefox.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-->
    File Mismatch: C:\Windows\system32\en-US\sppc.dll.mui[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\en-US\sppcext.dll.mui[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\en-US\slc.dll.mui[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\en-US\slcext.dll.mui[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\en-US\sppuinotify.dll.mui[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\en-US\slui.exe.mui[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\en-US\sppcomapi.dll.mui[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\en-US\sppcommdlg.dll.mui[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\en-US\sppsvc.exe.mui[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\en-US\user32.dll.mui[6.1.7600.16385], Hr = 0x800b0100

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{7179B102-17AD-485E-AE66-69B143A8A07F}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-43HG8</PKey><PID>55041-OEM-8992671-00282</PID><PIDType>2</PIDType><SID>S-1-5-21-2583386045-2207712438-234898041</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>P43-ES3G</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F11</Version><SMBIOSVersion major="2" minor="4"/><Date>20091105000000.000000+000</Date></BIOS><HWID>DFBA3607018400F8</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>W. Europe Standard Time(GMT+01:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>steg</OEMID><OEMTableID></OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>103</Result><Products><Product GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>103</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>A36BCDDE3E4E58E</Val><Hash>1kJ2nt3swtsGCfowqLcbNyaEzTc=</Hash><Pid>89388-711-7276625-65147</Pid><PidType>14</PidType></Product><Product GUID="{91120000-0031-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>2007 Microsoft Office system</Name><Ver>12</Ver><PidType>19</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="103"/><App Id="A1" Version="12" Result="103"/><App Id="BA" Version="12" Result="103"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Software licensing service version: 6.1.7600.16385

    Name: Windows(R) 7, Professional edition
    Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
    Activation ID: 50e329f7-a5fa-46b2-85fd-f224e5da7764
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00178-926-700282-02-2055-7600.0000-2312009
    Installation ID: 009061979063776353678241520874596803167893628464800803
    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: 43HG8
    License Status: Licensed
    Remaining Windows rearm count: 1
    Trusted time: 15/11/2010 21:04:22

    Windows Activation Technologies-->
    HrOffline: 0x8004FE21
    HrOnline: N/A
    HealthStatus: 0x000000000000EF60
    Event Time Stamp: 11:10:2010 18:16
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:
    Tampered File: %systemroot%\system32\sppc.dll|sppc.dll.mui
    Tampered File: %systemroot%\system32\sppcext.dll|sppcext.dll.mui
    Tampered File: %systemroot%\system32\slc.dll|slc.dll.mui
    Tampered File: %systemroot%\system32\slcext.dll|slcext.dll.mui
    Tampered File: %systemroot%\system32\sppuinotify.dll|sppuinotify.dll.mui
    Tampered File: %systemroot%\system32\slui.exe|slui.exe.mui|COM Registration
    Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui
    Tampered File: %systemroot%\system32\sppcommdlg.dll|sppcommdlg.dll.mui
    Tampered File: %systemroot%\system32\sppsvc.exe|sppsvc.exe.mui


    HWID Data-->
    HWID Hash Current: NgAAAAEABgABAAEAAAACAAAAAQABAAEA6GEm2U5pRrwMNYQ05L/iX5iyiEdsWGI9ZPPMAUxY

    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   steg  GBTUACPI
      FACP   steg  GBTUACPI
      HPET   steg  GBTUACPI
      MCFG   steg  GBTUACPI
      TAMG   GBT     GBT   B0
      SLIC   steg  
      SSDT   PmRef  CpuPm

     

    Monday, November 15, 2010 8:05 PM
  • Hi, thanks for the replies - here is the rest report again - hope it's all here this time around, maybe someone can tell me what is the issue please?

     

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

    Validation Code: 0x8004FE21
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-GM2YY-R2KTT-43HG8
    Windows Product Key Hash: UhVqQM4C3ocWWq4h2L4psSCs0pU=
    Windows Product ID: 55041-OEM-8992671-00282
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7600.2.00010100.0.0.048

    OGA Data-->
    Office Status: 103 Blocked VLK
    Microsoft Office Enterprise 2007 - 103 Blocked VLK
    2007 Microsoft Office system - 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 77F760FE-153-80070002_7E90FEE8-175-80070002_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_B4D0AA8B-920-80070057

    Other data-->
    SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>P43-ES3G</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F11</Version><SMBIOSVersion major="2" minor="4"/><Date>20091105000000.000000+000</Date></BIOS><HWID>DFBA3607018400F8</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>W. Europe Standard Time(GMT+01:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>steg</OEMID>

    File Scan Data-->
    File Mismatch: C:\Windows\system32\en-US\sppc.dll.mui[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\en-US\sppcext.dll.mui[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\en-US\slc.dll.mui[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\en-US\slcext.dll.mui[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\en-US\sppuinotify.dll.mui[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\en-US\slui.exe.mui[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\en-US\sppcomapi.dll.mui[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\en-US\sppcommdlg.dll.mui[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\en-US\sppsvc.exe.mui[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\en-US\user32.dll.mui[6.1.7600.16385], Hr = 0x800b0100

     

    Windows Activation Technologies-->
    HrOffline: 0x8004FE21
    HrOnline: N/A
    HealthStatus: 0x000000000000EF60
    Event Time Stamp: 11:10:2010 18:16
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:
    Tampered File: %systemroot%\system32\sppc.dll|sppc.dll.mui
    Tampered File: %systemroot%\system32\sppcext.dll|sppcext.dll.mui
    Tampered File: %systemroot%\system32\slc.dll|slc.dll.mui
    Tampered File: %systemroot%\system32\slcext.dll|slcext.dll.mui
    Tampered File: %systemroot%\system32\sppuinotify.dll|sppuinotify.dll.mui
    Tampered File: %systemroot%\system32\slui.exe|slui.exe.mui|COM Registration
    Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui
    Tampered File: %systemroot%\system32\sppcommdlg.dll|sppcommdlg.dll.mui
    Tampered File: %systemroot%\system32\sppsvc.exe|sppsvc.exe.mui

     


    You would appear to be using a hack to enable alternative language packs, and also have a non-genuine install of Office, and also of Windows.
    All in all, you would appear to be using a totally non-genuine system!
    I would suggest that you take it back to where you got it from, accompanied by an MK47, and demand a refund. (<g>)
    Seriously, though, what make does your PC claim to be?
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Monday, November 15, 2010 10:45 PM
    Moderator