none
Windows Product key - seems to disappear RRS feed

  • Question

  • I bought a new computer from Best Buy with windows 7 home premium the day it was first available.  This was some time ago. We had a virus on the computer; I hired a local company to remove the virus and then it said windows was not valid.  He spent two days getting MS to recognize the key.  I have the valid sticker on my computer.

    Now, many months later, it says the windows is not valid.  It is a valid key.  I ran the diag tool and it shows both the OEM key and my key, but still won't let me validate.  The computer is long past the warranted date from the store.  How do I fix this?

    Diagnostic Report (1.9.0019.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50

    Cached Validation Code: 0x0
    Windows Product Key: *****-*****-*****-*****-MDKHQ
    Windows Product Key Hash: TFSN03sdCKRBsPB+OonWcASqtag=
    Windows Product ID: 00359-OEM-*******-15581
    Windows Product ID Type: 8
    Windows License Type: COA SLP
    Windows OS version: 6.1.7600.2.00010300.0.0.003
    ID: {47F8E2F2-8AC6-4880-9719-597DB4E3AFDE}(1)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Home Premium
    Architecture: 0x00000009
    Build lab: 7600.win7_gdr.101026-1503
    TTS Error: T:20100605092517115-
    Validation Diagnostic:
    Resolution Status: N/A

    WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002

    WGA 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: 100 Genuine
    Microsoft Office Standard Edition 2003 - 100 Genuine
    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_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005

    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-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{47F8E2F2-8AC6-4880-9719-597DB4E3AFDE}</UGUID><Version>1.9.0019.0</Version><OS>6.1.7600.2.00010300.0.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-MDKHQ</PKey><PID>00359-OEM-*******-15581</PID><PIDType>8</PIDType><SID>S-1-5-21-4174813398-723076488-917727274</SID><SYSTEM><Manufacturer>HP-Pavilion</Manufacturer><Model>NY543AA-ABA s5220y</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>5.24</Version><SMBIOSVersion major="2" minor="5"/><Date>20090619000000.000000+000</Date></BIOS><HWID>44B83607018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Mountain Standard Time(GMT-07:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-CPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Standard Edition 2003</Name><Ver>11</Ver><Val>86155888D676874</Val><Hash>u1ojJb3M/zi+i5+gzhWou5BjSeE=</Hash><Pid>70141-058-3720385-56850</Pid><PidType>1</PidType></Product></Products><Applications><App Id="16" Version="11" Result="100"/><App Id="18" Version="11" Result="100"/><App Id="1A" Version="11" Result="100"/><App Id="1B" Version="11" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAACAAAAJlBAAAAAAAAYWECAAAAAAAu2jxNwwTLAWbXGpOihAOpMHzDmWxsjur0woFmQk2DSihJ5kUEJvEBOEHE5qBUGiabMUVmKJlNWzOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAx4dZsxs/sxaQSZh6DCEuBH7wIA7P1+iv48DVx/rrZqTxNYI96ftYsTfhoYJNm+XVEzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM

    Licensing Data-->
    C:\Windows\system32\slmgr.vbs(1333, 5) Microsoft VBScript runtime error: Permission denied

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C533
    HealthStatus: PASS
    Event Time Stamp: 3:14:2011 13:08
    WAT Activex: Registered
    WAT Admin Service: Registered

    HWID Data-->
    HWID Hash Current: LAAAAAEAAgABAAEAAAABAAAAAQABAAEA6GEmpMw/wBKqdsAmOrBWvvz/Rso=

    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            HPQOEM        SLIC-CPC
      FACP            HPQOEM        SLIC-CPC
      HPET            HPQOEM        SLIC-CPC
      MCFG            HPQOEM        SLIC-CPC
      SLIC            HPQOEM        SLIC-CPC
      SSDT            PmRef        CpuPm


    Monday, March 14, 2011 7:58 PM

Answers

  • Hi Chris,

      I've checked the key and it is Valid and Genuine.  So that's not causing the problem.

     

      From the Diagnostic Report I see a few things:

    1) "TTS Error: T:20100605092517115- "  This usually indicates a "Trusted Store Tamper" but that long number (a time stamp) shows that the tamper last occurred in June of 2010. So, while this may have caused any problem you saw back in June, it's not the cause of the current issue.

     

     2) "Licensing Data-->
    C:\Windows\system32\slmgr.vbs(1333, 5) Microsoft VBScript runtime error: Permission denied
    "

     This is most likely the cause of the current issue.  Unfortunately, we have not had much success resolving issues similar to this, on the forums. 

    One thing you could try is Repairing Windows using System Restore.  This will return Windows to a "saves" Restore Point from the past:

    1) Click the Start button
    2) In the Start Search field, type: System Restore and hit the Enter key
    3) Select "Choose Different Restore Point", Put a checkmark in the box that says "Show restore points older than 5 days" and select a restore point that corresponds to a date Before you first noticed the issue.
    4) Click the "Next" button.
    5) Reboot and see if that resolves the issue.

    If this doesn't resolve the issue or you don't have any restore points from before this issues occurred, my only recommendation would be to contact Microsoft Assisted Support at one of the below URLs.

    North America: http://support.microsoft.com/contactus/cu_sc_genadv_master?ws=support&ws=support#tab4

    Outside North America:
    http://support.microsoft.com/contactus/?ws=support#tab0

     

    Sorry I couldn't be more help,

     

     


    Darin MS
    Tuesday, March 15, 2011 9:06 PM

All replies

  • Why did you edit the report to mask the product key in fields three and four and part of the PID?  Is it a leaked key that the tech used on your computer?  The computer was manufactured five weeks before Windows 7 was released to manufacturing (July 24, 2009).  It did not ship with this copy of Windows 7. 

    The tech should have used a system builder OEM copy or a retail copy but not an SLP copy.  SLP copies are factory installed.  The Tech may have downloaded a leaked OEM SLP key from internet. 

    Windows Product Key: *****-*****-*****-*****-MDKHQ

    Windows Product ID: 00359-OEM-*******-15581
    Windows Product ID Type: 8
    Windows License Type: COA SLP

    The COA SLP key cannot be right.  It means that a factory installed copy of Windows has been reactivated with the key on the sticker placed on the computer at the factory.  The problem is that Windows 7 was not available at time of manufacture in the report when the sticker was supposed to have been affixed

    <Date>20090619000000.000000+000</Date>

    You need to get the tech to fix this or purchase a retail copy of Windows.

     


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Monday, March 14, 2011 8:27 PM
    Answerer
  • Please report the full unmodified Diagnostic Report.

    The Unmodified Diagnostic Report will not compromise the security of your Product Key but will still allow me to check the key through my Key Check system.

     

    If you do not wish to post the unmodified Diagnostic Report, please contact Microsoft Assisted Support at one of the below URLs for further assistance.

    North America: http://support.microsoft.com/contactus/cu_sc_genadv_master?ws=support&ws=support#tab4

    Outside North America:
    http://support.microsoft.com/contactus/?ws=support#tab0

     

    Thank you,


    Darin MS
    Monday, March 14, 2011 10:33 PM
  • Sorry, I thought I should not put the keys on there.  The full report is below.  The computer was in the Best Buy inventory and they would not sell it until windows 7 was released.

     

    Diagnostic Report (1.9.0019.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50

    Cached Validation Code: 0x0
    Windows Product Key: *****-*****-QYTYK-CCC4W-MDKHQ
    Windows Product Key Hash: TFSN03sdCKRBsPB+OonWcASqtag=
    Windows Product ID: 00359-OEM-9800693-15581
    Windows Product ID Type: 8
    Windows License Type: COA SLP
    Windows OS version: 6.1.7600.2.00010300.0.0.003
    ID: {47F8E2F2-8AC6-4880-9719-597DB4E3AFDE}(1)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Home Premium
    Architecture: 0x00000009
    Build lab: 7600.win7_gdr.101026-1503
    TTS Error: T:20100605092517115-
    Validation Diagnostic:
    Resolution Status: N/A

    WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002

    WGA 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: 100 Genuine
    Microsoft Office Standard Edition 2003 - 100 Genuine
    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_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005

    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-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{47F8E2F2-8AC6-4880-9719-597DB4E3AFDE}</UGUID><Version>1.9.0019.0</Version><OS>6.1.7600.2.00010300.0.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-MDKHQ</PKey><PID>00359-OEM-9800693-15581</PID><PIDType>8</PIDType><SID>S-1-5-21-4174813398-723076488-917727274</SID><SYSTEM><Manufacturer>HP-Pavilion</Manufacturer><Model>NY543AA-ABA s5220y</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>5.24</Version><SMBIOSVersion major="2" minor="5"/><Date>20090619000000.000000+000</Date></BIOS><HWID>44B83607018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Mountain Standard Time(GMT-07:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-CPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Standard Edition 2003</Name><Ver>11</Ver><Val>86155888D676874</Val><Hash>u1ojJb3M/zi+i5+gzhWou5BjSeE=</Hash><Pid>70141-058-3720385-56850</Pid><PidType>1</PidType></Product></Products><Applications><App Id="16" Version="11" Result="100"/><App Id="18" Version="11" Result="100"/><App Id="1A" Version="11" Result="100"/><App Id="1B" Version="11" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAACAAAAJlBAAAAAAAAYWECAAAAAAAu2jxNwwTLAWbXGpOihAOpMHzDmWxsjur0woFmQk2DSihJ5kUEJvEBOEHE5qBUGiabMUVmKJlNWzOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAx4dZsxs/sxaQSZh6DCEuBH7wIA7P1+iv48DVx/rrZqTxNYI96ftYsTfhoYJNm+XVEzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM

    Licensing Data-->
    C:\Windows\system32\slmgr.vbs(1333, 5) Microsoft VBScript runtime error: Permission denied

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C533
    HealthStatus: PASS
    Event Time Stamp: 3:14:2011 13:08
    WAT Activex: Registered
    WAT Admin Service: Registered

    HWID Data-->
    HWID Hash Current: LAAAAAEAAgABAAEAAAABAAAAAQABAAEA6GEmpMw/wBKqdsAmOrBWvvz/Rso=

    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   HPQOEM  SLIC-CPC
      FACP   HPQOEM  SLIC-CPC
      HPET   HPQOEM  SLIC-CPC
      MCFG   HPQOEM  SLIC-CPC
      SLIC   HPQOEM  SLIC-CPC
      SSDT   PmRef  CpuPm

     


    Chris
    Monday, March 14, 2011 11:15 PM
  • Hi Chris,

      I've checked the key and it is Valid and Genuine.  So that's not causing the problem.

     

      From the Diagnostic Report I see a few things:

    1) "TTS Error: T:20100605092517115- "  This usually indicates a "Trusted Store Tamper" but that long number (a time stamp) shows that the tamper last occurred in June of 2010. So, while this may have caused any problem you saw back in June, it's not the cause of the current issue.

     

     2) "Licensing Data-->
    C:\Windows\system32\slmgr.vbs(1333, 5) Microsoft VBScript runtime error: Permission denied
    "

     This is most likely the cause of the current issue.  Unfortunately, we have not had much success resolving issues similar to this, on the forums. 

    One thing you could try is Repairing Windows using System Restore.  This will return Windows to a "saves" Restore Point from the past:

    1) Click the Start button
    2) In the Start Search field, type: System Restore and hit the Enter key
    3) Select "Choose Different Restore Point", Put a checkmark in the box that says "Show restore points older than 5 days" and select a restore point that corresponds to a date Before you first noticed the issue.
    4) Click the "Next" button.
    5) Reboot and see if that resolves the issue.

    If this doesn't resolve the issue or you don't have any restore points from before this issues occurred, my only recommendation would be to contact Microsoft Assisted Support at one of the below URLs.

    North America: http://support.microsoft.com/contactus/cu_sc_genadv_master?ws=support&ws=support#tab4

    Outside North America:
    http://support.microsoft.com/contactus/?ws=support#tab0

     

    Sorry I couldn't be more help,

     

     


    Darin MS
    Tuesday, March 15, 2011 9:06 PM