none
Windows vista became non genuine after automatic update (Build 6002)

    Question

  • My computer was working fine until i got a windows update on the 13th of october and the when i got back on, I had the "Windows vista (build 6002) is not Genuine"

    I've tried both rewriting the validation files the the command prompt and i've tried doing the phone activation.
    The command prompt didn't work and the only thing that pops up with the slui.exe 4 file is a page that says "type in your activation code" and there are no directions for phone activation.

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a8
    Windows Product Key: *****-*****-JQMWD-2QJRJ-RJ34F
    Windows Product Key Hash: R8gPTEFMoOygFewoq/uOoWMpz68=
    Windows Product ID: 89578-OEM-7332157-00237
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6002.2.00010300.2.0.003
    ID: {B63CC203-7CED-414D-8BE2-5600976BF4B7}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6002.vistasp2_gdr.120824-0336
    TTS Error: 
    Validation Diagnostic: 
    Resolution Status: N/A

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

    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: 100 Genuine
    Microsoft Office Professional 2007 - 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: B4D0AA8B-604-645_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:\Users\brit x3\AppData\Local\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>{B63CC203-7CED-414D-8BE2-5600976BF4B7}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6002.2.00010300.2.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-RJ34F</PKey><PID>89578-OEM-7332157-00237</PID><PIDType>2</PIDType><SID>S-1-5-21-397148462-3030776477-163826579</SID><SYSTEM><Manufacturer>TOSHIBA</Manufacturer><Model>Satellite L300</Model></SYSTEM><BIOS><Manufacturer>INSYDE</Manufacturer><Version>1.20</Version><SMBIOSVersion major="2" minor="4"/><Date>20080828000000.000000+000</Date></BIOS><HWID>7B313507018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>TOSINV</OEMID><OEMTableID>TOSINV00</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0014-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Professional 2007</Name><Ver>12</Ver><Val>AE5328E62D8BF7A</Val><Hash>+XRtNVIcdKC71oPpdj32iaAXaZg=</Hash><Pid>81605-957-8765243-65405</Pid><PidType>1</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"/></Applications></Office></Software></GenuineResults>  

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Software licensing service version: 6.0.6002.18005

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: MgAAAAEAAQABAAIAAQABAAAAAwABAAEAJJQABpy5Rm4yfST2xlHy9PZMPEBgNKxWKoU=

    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 TOSINV TOSINV00
      FACP TOSINV TOSINV00
      HPET TOSINV TOSINV00
      BOOT TOSINV TOSINV00
      MCFG TOSINV TOSINV00
      ASF! TOSINV TOSINV00
      SLIC TOSINV TOSINV00
      SSDT PmRef CpuPm

    Monday, October 22, 2012 10:59 PM

Answers

  • The problem is that your system is unable to properly read the BIOS SLIC table that should be present in the system to be able to self-activate the OS.  

     

     You need to change the Product Key to the one on the COA sticker on the machine's case (or inside the battery compartment),  using the Change Product Key link at the bottom of the System properties page.

     

    You may need to activate by phone.   


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Tuesday, October 23, 2012 9:12 AM
    Moderator

All replies

  • The problem is that your system is unable to properly read the BIOS SLIC table that should be present in the system to be able to self-activate the OS.  

     

     You need to change the Product Key to the one on the COA sticker on the machine's case (or inside the battery compartment),  using the Change Product Key link at the bottom of the System properties page.

     

    You may need to activate by phone.   


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Tuesday, October 23, 2012 9:12 AM
    Moderator
  • I found the sticker but the key has been partially rubbed off (with it being a laptop that's not really a surprise) so typing in the key is impossible.

    Since that's not an option, do you think flashing the bios would work? if not is there any way for me to get the key other than on the sticker?

    Tuesday, October 23, 2012 10:57 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.



    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Wednesday, October 24, 2012 9:51 AM
    Moderator