none
Apparently my Product ID was hijacked! My Vista now says I have Invalid License after 6 years!

    Question

  • I bought a Hp laptop back in 2007 and have used it ever since.  Last night when I turned my computer on, it told me to activate my windows.  Out of the blue.  I tried and it told me that I had an invalid license.  I contacted the Answer Desk and was told that the system was blocking it due to multiple activations.  I have never installed it on another machine and figure that some way someone has hijacked my product id.  Is there anyway to get a product id without paying for another one?  Also was wondering, I have  command prompt that comes on upon start up, could that have anything to do with how my key was hijacked?

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-27HYQ-XTKW2-WQD8Q
    Windows Product Key Hash: U8YEZzymoD4DMyaMb32rPrNIS90=
    Windows Product ID: 89578-OEM-7332157-00061
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6002.2.00010300.2.0.003
    ID: {6585F398-8C5B-4F3C-8D08-088F40935E41}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6002.vistasp2_gdr.130707-1535
    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: 102
    Microsoft Office Home and Student 2007 - 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: http=127.0.0.1:8877;https=127.0.0.1:8877
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files\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>{6585F398-8C5B-4F3C-8D08-088F40935E41}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6002.2.00010300.2.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-WQD8Q</PKey><PID>89578-OEM-7332157-00061</PID><PIDType>2</PIDType><SID>S-1-5-21-3558930684-3958589224-86571855</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>MCP67</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.30    </Version><SMBIOSVersion major="2" minor="4"/><Date>20080424000000.000000+000</Date></BIOS><HWID>44310500018400FE</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-MPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>102</Result><Products><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><PidType>19</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>  

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Software licensing service version: 6.0.6002.18005
    Name: Windows(TM) Vista, HomePremium edition
    Description: Windows Operating System - Vista, OEM_SLP channel
    Activation ID: bffdc375-bbd5-499d-8ef1-4f37b61c895f
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 89578-00146-321-500061-02-1033-6000.0000-0062013
    Installation ID: 003105191145341111762263925774598714195554231083742142
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43473
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43474
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=43476
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43475
    Partial Product Key: WQD8Q
    License Status: Notification
    Notification Reason: 0xC004F059.

    Windows Activation Technologies-->
    N/A

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

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: no, invalid SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information: 
      ACPI Table Name OEMID Value OEMTableID Value
      APIC PTLTD APIC  
      FACP NVIDIA MCP67-M 
      SRAT AMD   HAMMER  
      HPET PTLTD HPETTBL 
      BOOT PTLTD $SBFTBL$
      MCFG PTLTD  MCFG  
      TCPA Phoeni x      
      SSDT PTLTD POWERNOW
      SLIC HPQOEM SLIC-MPC

    Tuesday, January 28, 2014 6:26 PM

Answers

  • Your problem is that for some reason, the system is unable to properly read the SLIC table in the BIOS, which is required to be able to self-activate the OEM_SLP Key with which the computer came installed.

    The normal solution is to change the Key to the one on your COA sticker - but you say that you are unable to read the Key there.

    In such circumstances, the only things you can do are

    1) recreate the Licensing Store - in case it's a minor software problem causing the misread

    2) try updating the BIOS to the latest available Vista-compliant one, from the manufacturer's website

    3) Contact the manufacturer direct, and see if they can provide assistance to correct the SLIC table

    4) a reformat and reinstall using the manufacturer's recovery media

    5) purchase a new license for Windows (or a new computer)   

    There *may* be an alternative solution though, if you are patient and persistent.

    Attempt Telephone Activation, and speak to an operator - they will tell you that your current Key
    is blocked (they should then ask for confirmation of your Product Key). Explain
    to them your problem, that you need to change the Key to the one on your sticker,
    but that the sticker is unreadable (could they please supply a replacement
    Key?). Hopefully they will ask for documentary proof of the sticker, in the
    form of an email with a picture of the affected sticker - and you can proceed
    from there.

    Sometimes it takes two or three calls before you get an operator who actually knows and uses
    this procedure - but I know that it can and does happen.


    Recreate the Licensing Store with the correct data.

    1) Open an Internet Browser window.

    2) Type: %windir%\system32 into the browser address bar.

    3) Find the file CMD.exe

    4) Right-Click on CMD.exe and select 'Run as Administrator'

    5) Type: net stop slsvc (it may ask you if you are sure, select yes)

    6) Type: cd %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareLicensing

    7) Type: rename tokens.dat tokens.bar

    8) Type: cd %windir%\system32

    9) Type: net start slsvc

    10) Type: cscript slmgr.vbs -rilc (It may take a long time for this to complete, please be patient)

    11) Restart your computer twice. 

    You may be asked to enter your COA Key and/or Activate. – if asked for the Key, use the one on your COA sticker on the machine’s case (you may need to activate by telephone).  

    Once complete, run another MGADiag report and post back with the results.     


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

    Tuesday, January 28, 2014 11:11 PM
    Moderator

All replies

  • Have you tried entering in the Product Key that is listed on the COA sticker that should be either on the case or in the battery compartment under the battery? 

    Please do not read this sentence. Please ignore the previous sentence.

    Tuesday, January 28, 2014 7:03 PM
  • This laptop has been around for almost 7 years and I have 3 children that are now teenagers but the sticker is so worn now from all the use it has seen over the years that I cannot read the COA sticker.

    I can read some of the letters and numbers but some I am truly guessing at what it is.

    • Edited by cynmills Tuesday, January 28, 2014 7:10 PM
    Tuesday, January 28, 2014 7:07 PM
  • Your problem is that for some reason, the system is unable to properly read the SLIC table in the BIOS, which is required to be able to self-activate the OEM_SLP Key with which the computer came installed.

    The normal solution is to change the Key to the one on your COA sticker - but you say that you are unable to read the Key there.

    In such circumstances, the only things you can do are

    1) recreate the Licensing Store - in case it's a minor software problem causing the misread

    2) try updating the BIOS to the latest available Vista-compliant one, from the manufacturer's website

    3) Contact the manufacturer direct, and see if they can provide assistance to correct the SLIC table

    4) a reformat and reinstall using the manufacturer's recovery media

    5) purchase a new license for Windows (or a new computer)   

    There *may* be an alternative solution though, if you are patient and persistent.

    Attempt Telephone Activation, and speak to an operator - they will tell you that your current Key
    is blocked (they should then ask for confirmation of your Product Key). Explain
    to them your problem, that you need to change the Key to the one on your sticker,
    but that the sticker is unreadable (could they please supply a replacement
    Key?). Hopefully they will ask for documentary proof of the sticker, in the
    form of an email with a picture of the affected sticker - and you can proceed
    from there.

    Sometimes it takes two or three calls before you get an operator who actually knows and uses
    this procedure - but I know that it can and does happen.


    Recreate the Licensing Store with the correct data.

    1) Open an Internet Browser window.

    2) Type: %windir%\system32 into the browser address bar.

    3) Find the file CMD.exe

    4) Right-Click on CMD.exe and select 'Run as Administrator'

    5) Type: net stop slsvc (it may ask you if you are sure, select yes)

    6) Type: cd %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareLicensing

    7) Type: rename tokens.dat tokens.bar

    8) Type: cd %windir%\system32

    9) Type: net start slsvc

    10) Type: cscript slmgr.vbs -rilc (It may take a long time for this to complete, please be patient)

    11) Restart your computer twice. 

    You may be asked to enter your COA Key and/or Activate. – if asked for the Key, use the one on your COA sticker on the machine’s case (you may need to activate by telephone).  

    Once complete, run another MGADiag report and post back with the results.     


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

    Tuesday, January 28, 2014 11:11 PM
    Moderator