locked
"Vista Home Premium product key you entered is invalid for activation" on 3 year old machine RRS feed

  • Question

  • For the first time that I can remember, I am getting a pop up window saying"The Windows Vista Home Premium product key you entered is invalid for activation".  Ummm...I have had this same machine, purchased with a licensed copy, directly from Gateway for three years.  Why would I start getting some activation message now?

    I have checked the forums and threads for something close, but cannot find an adequate answer.  The slui.exe 4 only prompts me with three choices (buy new,type different key or contact Gateway) and no phone prompt.  There is no other information on screen than that.

    What is my next step?  My diagnostic screen is below and license is genuine.

     

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Genuine
    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-3RBY2-BGQ2R-DR9M6
    Windows Product Key Hash: EYIpz/47G03lWRAOmk3kg+lR7Rc=
    Windows Product ID: 89578-OEM-7332157-00141
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6002.2.00010300.2.0.003
    ID: {7ECF199F-B733-429B-A000-DB2FA53287F4}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.7.69.2
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6002.vistasp2_gdr.100218-0019
    TTS Error:
    Validation Diagnostic:
    Resolution Status: N/A

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

    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: 2.0.48.0
    OGAExec.exe Signed By: Microsoft
    OGAAddin.dll Signed By: Microsoft

    OGA Data-->
    Office Status: 100 Genuine
    Microsoft Office OneNote 2003 - 100 Genuine
    Microsoft Office Basic 2007 - 100 Genuine
    OGA Version: Registered, 2.0.48.0
    Signed By: Microsoft
    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

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files\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>{7ECF199F-B733-429B-A000-DB2FA53287F4}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6002.2.00010300.2.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-DR9M6</PKey><PID>89578-OEM-7332157-00141</PID><PIDType>2</PIDType><SID>S-1-5-21-1828408566-2717901271-1568717851</SID><SYSTEM><Manufacturer>Gateway                         </Manufacturer><Model>M285-E                          </Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies LTD</Manufacturer><Version>78.15   </Version><SMBIOSVersion major="2" minor="4"/><Date>20070711000000.000000+000</Date></BIOS><HWID>EB313507018400EE</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/><GANotification><File Name="OGAAddin.dll" Version="2.0.48.0"/></GANotification></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91A10409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office OneNote 2003</Name><Ver>11</Ver><PidType>0</PidType></Product><Product GUID="{91120000-0013-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Basic 2007</Name><Ver>12</Ver><Val>A8D34BEE37885AE</Val><Hash>h8CtrH+0KsFmzCU3rAquOX+bLgo=</Hash><Pid>89445-OEM-6472781-81162</Pid><PidType>4</PidType></Product></Products><Applications><App Id="A1" Version="11" Result="100"/><App Id="16" 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
    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-500141-02-1033-6000.0000-1132007
    Installation ID: 238826943455380476515385249155943893509285248486409492
    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: DR9M6
    License Status: Notification
    Notification Reason: 0xC004F057.

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: NAAAAAEAAwABAAEAAQABAAAAAwABAAEAeqj+fB0BPBXYhkjkbDdEh/L0/oa8+75SrFb0SA==

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            GATEWA        SYSTEM 
      FACP            GATEWA        SYSTEM 
      HPET            GATEWA        SYSTEM 
      BOOT            GATEWA        SYSTEM 
      MCFG            GATEWA        SYSTEM 
      ASF!            GATEWA        SYSTEM 
      APIC            GATEWA        SYSTEM 
      SSDT            GATEWA        SYSTEM 

    Friday, April 30, 2010 9:06 PM

Answers

  • Hello chucksdaone,

    The key to your problem is this line all the way at the bottom of the report:

    BIOS valid for OA 2.0: yes, but no SLIC table

    Computers from major manufacturers like Gateway use a Windows License type called System Lock Preinstall (SLP).  There is data in the Windows installation that is unique to the manufacturer, and there is data in the motherboard BIOS that is also unique to that computer manufacturer.  So, after the Gateway branded installation of Vista Home Premium was imaged onto your computer, boxed up and sent to you, upon first startup, Vista was programmed to go looking for the data in the motherboard that is unique to Gateway.  When it found the data, Windows self-activated and all was well.

    Windows randomly runs a check to see if it is still installed on the computer it's supposed to be on.  In this context, the SLIC table is the information that the installed copy of Vista looks for to ensure that it is still installed on a Gateway computer.

    So, the last time it checked, for some unknown reason, Windows could not find the SLIC table in the computer's BIOS.  Under those circumstances, Windows assumes it is no longer on a Gateway computer, and since that is a violation of the Software Licensing Terms, Windows throws a fit and tells you it is not activated.  You ran the Software Licensing User Interface, entered the product key on the Certificate of Authenticity (CoA), which changed the license type from OEM SLP to COA SLP (IIRC), and your Windows on your Gateway is now happily activated once again.


    Buy Office 2007 Now, Get Office 2010 Free http://office2010.microsoft.com/en-us/tech-guarantee/microsoft-office-2010-technology-guarantee-FX101825695.aspx?CTT=97
    Tuesday, May 4, 2010 2:16 PM

All replies

  • Does anyone have an answer?  I'd like to get my genuine screen back...  :)
    Saturday, May 1, 2010 12:23 PM
  • Bueller? Bueller?  anyone, anyone????
    Sunday, May 2, 2010 1:19 PM
  • i have the same problem as you, my product key, printed on the underside of my dell laptop is coming up with the same message...yet it worked for over a year and is a legal copy...I watch this thread for answers.
    Sunday, May 2, 2010 4:08 PM
  • I received a MS phone number in another forum, but here is the pathetic Windows ending:

    This makes no sense...  :(

    I called the number and, after a couple of transfers, got a message along the lines of "we are experiencing system problems and cannot answer your call"- CLICK.  OK, i understand that MS may not have enough live bodies to go around, so I decided to run the "slui.exe 4" again.  I gave me three choices- one of which was to enter a "different product key".

    I chose that options, entered my CURRENT key from the bottom of my laptop and everything is fine.  Windows "reactivated" itself and I was rewarded with a silly message verifying that I have a genuine copy of Windows. 

    MS:  if all you want to do is verify my legit copy, WHY DON'T YOU MAKE THAT ONE OF YOUR OPTIONS???????  People with legit copies on legit machines don't need to spend hours looking for an answer to your stupid bubble message.  YOU WASTED MY VALUABLE TIME - ONLY WISH I COULD RETURN THE FAVOR!!!

    Monday, May 3, 2010 10:52 PM
  • Hello chucksdaone,

    The key to your problem is this line all the way at the bottom of the report:

    BIOS valid for OA 2.0: yes, but no SLIC table

    Computers from major manufacturers like Gateway use a Windows License type called System Lock Preinstall (SLP).  There is data in the Windows installation that is unique to the manufacturer, and there is data in the motherboard BIOS that is also unique to that computer manufacturer.  So, after the Gateway branded installation of Vista Home Premium was imaged onto your computer, boxed up and sent to you, upon first startup, Vista was programmed to go looking for the data in the motherboard that is unique to Gateway.  When it found the data, Windows self-activated and all was well.

    Windows randomly runs a check to see if it is still installed on the computer it's supposed to be on.  In this context, the SLIC table is the information that the installed copy of Vista looks for to ensure that it is still installed on a Gateway computer.

    So, the last time it checked, for some unknown reason, Windows could not find the SLIC table in the computer's BIOS.  Under those circumstances, Windows assumes it is no longer on a Gateway computer, and since that is a violation of the Software Licensing Terms, Windows throws a fit and tells you it is not activated.  You ran the Software Licensing User Interface, entered the product key on the Certificate of Authenticity (CoA), which changed the license type from OEM SLP to COA SLP (IIRC), and your Windows on your Gateway is now happily activated once again.


    Buy Office 2007 Now, Get Office 2010 Free http://office2010.microsoft.com/en-us/tech-guarantee/microsoft-office-2010-technology-guarantee-FX101825695.aspx?CTT=97
    Tuesday, May 4, 2010 2:16 PM
  • Thanks Dan, you were the most helpful reply. That make sense right up until the SLIC table going away.  I would assume that is something that a normal person wouldn't have a clue about (like me), so why would it disappear and cause my problem?  That's a rhetorical question and isn't worthy of research, but hope others that experience this can resolve it as simply as I was able to.

     

    PS:  I just hung up with another software vendor because its authentication went away.  They apparently use some portion of the Windows key + other factors to validate their own license.  When it changed to COA, their software went off line as well.  So if other peeps have a problem after switching the key around, you may have to contact that vendor or just re-install the software.

    Tuesday, May 4, 2010 5:07 PM