locked
Windows Vista suddenly not genuine RRS feed

  • Question

  • Hello,

    Upon starting up my computer today I was greeted with a little message asking me if I'd like to activate my copy of Windows, now I've had this computer running a legit OEM copy of Vista Ultimate for nearly 3 years now so I'm wondering what exactly is up all of a sudden. Upon clicking "activate now" and inputting the code as shown on the side of my machine I get a "this code is not valid" message, and further to this I have noticed that the code stated in the diagnostic and the code on the side of the box do not match. The computer is an HP Compaq Presario purchased from JB Hifi and the only software I installed the last time my computer was on was the latest version of logitech setpoint as my mouse had been acting up recently (randomly left and right clicking by itself). Even after a system restore that undid this installation however I am still receiving the same error message.

    Hoping you can help me out here,
    Max W

     

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a8
    Windows Product Key: *****-*****-VFWRT-JGH7R-R933G
    Windows Product Key Hash: gYrJFhcKVmHMbiVVuoEU7w/jsC0=
    Windows Product ID: 89580-OEM-7332132-00015
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6002.2.00010100.2.0.001
    ID: {0861153D-80A9-42F9-944C-896AB334A482}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Ultimate
    Architecture: 0x00000000
    Build lab: 6002.vistasp2_gdr.101014-0432
    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: 114 Blocked VLK 2
    Microsoft Office Professional Edition 2003 - 114 Blocked VLK 2
    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_672A8F41-307-80004005_672A8F41-349-80004005_672A8F41-244-80004005

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Users\Max\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>{0861153D-80A9-42F9-944C-896AB334A482}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6002.2.00010100.2.0.001</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-R933G</PKey><PID>89580-OEM-7332132-00015</PID><PIDType>2</PIDType><SID>S-1-5-21-4176517140-2408954786-3606468303</SID><SYSTEM><Manufacturer>System Manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>2006/12/19</Version><SMBIOSVersion major="2" minor="4"/><Date>20080716000000.000000+000</Date></BIOS><HWID>02313507018400F8</HWID><UserLCID>0C09</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Cen. Australia Standard Time(GMT+09:30)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>114</Result><Products><Product GUID="{90110409-6000-11D3-8CFE-0150048383C9}"><LegitResult>114</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>59D1605114E3500</Val><Hash>vfZmaSmFPIYrLWTcZSZErUQg+Fo=</Hash><Pid>73931-640-0000106-57751</Pid><PidType>14</PidType></Product><Product GUID="{91120000-0014-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Professional 2007</Name><Ver>12</Ver><Val>A1AB29A3118477C</Val><Hash>Lbr2jEI1DNn0N+pLhVOOFndqIlU=</Hash><Pid>81605-958-3997106-65411</Pid><PidType>1</PidType></Product></Products><Applications><App Id="15" Version="11" Result="114"/><App Id="16" Version="11" Result="114"/><App Id="18" Version="11" Result="114"/><App Id="19" Version="11" Result="114"/><App Id="1A" Version="11" Result="114"/><App Id="1B" Version="11" Result="114"/><App Id="44" Version="11" Result="114"/><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: OgAAAAIAAwABAAEAAgADAAAAAgABAAEAeqjWSJmT5QH4n2AIkgBkCQYGje/y9M6fIDISme4RrFbI9A==

    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            Nvidia        NVDAACPI
      FACP            Nvidia        NVDAACPI
      HPET            Nvidia        NVDAACPI
      MCFG            Nvidia        NVDAACPI
      SSDT            PTLTD         POWERNOW

    Sunday, June 12, 2011 3:35 PM

Answers

  • "Maximus_W" wrote in message news:9da3ac86-1918-4370-8bd7-83b81f286d75...

    After running through the fixes for a number of other cases of this error (sfc /scannow, another CMD fix I cannot remember, system restore etc.) the system has finally accepted the on-case product ID and is now showing as genuine in MGAdiag.

    Case closed, thank you very much for whichever of those many solutions in other threads ended up working for me in the end,
    Max W.

    New diag, just in case there's anything I should know to stop this happening again:

     

     

    Diagnostic Report (1.9.0027.0):

    -----------------------------------------

    Windows Validation Data-->

    Validation Status: Genuine

    Validation Code: 0

    Cached Online Validation Code: 0x0

    Windows Product Key: *****-*****-2PDWJ-6H3VR-6MPBY

    Windows Product Key Hash: hudW52w04SNIviQ52vvYWTjDOpY=

    Windows Product ID: 89580-OEM-7200874-17073

    Windows Product ID Type: 8

    Windows License Type: COA SLP

    Windows OS version: 6.0.6002.2.00010100.2.0.001

     

    Other data-->

    SYSTEM><Manufacturer>System Manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>2006/12/19</Version><SMBIOSVersion major="2" minor="4"/><Date>20080716000000.000000+000</Date></BIOS

    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



    Changing the Key to the COA Key is what did the trick - it would appear that for whatever reason, your PC is unable to read the BIOS SLIC table that should be present, and which is required to self-activate the OEM_SLP Key that you were formerly using.
     
    Having said that, it looks as if you have replaced the motherboard on that machine? In which case, the license is technically no linger valid. The original machine should have been an HP - this one appears to be a retail motherboard. It's always possible that updating the BIOS with a non-compliant version has caused the problem.
     
    You should also note that your installation of Office is non-genuine.
    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Maximus_W Sunday, June 12, 2011 4:58 PM
    Sunday, June 12, 2011 4:16 PM
    Moderator

All replies

  • After running through the fixes for a number of other cases of this error (sfc /scannow, another CMD fix I cannot remember, system restore etc.) the system has finally accepted the on-case product ID and is now showing as genuine in MGAdiag.

    Case closed, thank you very much for whichever of those many solutions in other threads ended up working for me in the end,
    Max W.

    New diag, just in case there's anything I should know to stop this happening again:

     

     

    Diagnostic Report (1.9.0027.0):

    -----------------------------------------

    Windows Validation Data-->

    Validation Status: Genuine

    Validation Code: 0

    Cached Online Validation Code: 0x0

    Windows Product Key: *****-*****-2PDWJ-6H3VR-6MPBY

    Windows Product Key Hash: hudW52w04SNIviQ52vvYWTjDOpY=

    Windows Product ID: 89580-OEM-7200874-17073

    Windows Product ID Type: 8

    Windows License Type: COA SLP

    Windows OS version: 6.0.6002.2.00010100.2.0.001

    ID: {0861153D-80A9-42F9-944C-896AB334A482}(3)

    Is Admin: Yes

    TestCab: 0x0

    LegitcheckControl ActiveX: Registered, 1.9.42.0

    Signed By: Microsoft

    Product Name: Windows Vista (TM) Ultimate

    Architecture: 0x00000000

    Build lab: 6002.vistasp2_gdr.101014-0432

    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: 114 Blocked VLK 2

    Microsoft Office Professional Edition 2003 - 114 Blocked VLK 2

    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_672A8F41-307-80004005_672A8F41-349-80004005_672A8F41-244-80004005

     

    Browser Data-->

    Proxy settings: N/A

    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)

    Default Browser: C:\Users\Max\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>{0861153D-80A9-42F9-944C-896AB334A482}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6002.2.00010100.2.0.001</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-6MPBY</PKey><PID>89580-OEM-7200874-17073</PID><PIDType>8</PIDType><SID>S-1-5-21-4176517140-2408954786-3606468303</SID><SYSTEM><Manufacturer>System Manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>2006/12/19</Version><SMBIOSVersion major="2" minor="4"/><Date>20080716000000.000000+000</Date></BIOS><HWID>02313507018400F8</HWID><UserLCID>0C09</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Cen. Australia Standard Time(GMT+09:30)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>114</Result><Products><Product GUID="{90110409-6000-11D3-8CFE-0150048383C9}"><LegitResult>114</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>59D1605114E3500</Val><Hash>vfZmaSmFPIYrLWTcZSZErUQg+Fo=</Hash><Pid>73931-640-0000106-57751</Pid><PidType>14</PidType></Product><Product GUID="{91120000-0014-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Professional 2007</Name><Ver>12</Ver><Val>A1AB29A3118477C</Val><Hash>Lbr2jEI1DNn0N+pLhVOOFndqIlU=</Hash><Pid>81605-958-3997106-65411</Pid><PidType>1</PidType></Product></Products><Applications><App Id="15" Version="11" Result="114"/><App Id="16" Version="11" Result="114"/><App Id="18" Version="11" Result="114"/><App Id="19" Version="11" Result="114"/><App Id="1A" Version="11" Result="114"/><App Id="1B" Version="11" Result="114"/><App Id="44" Version="11" Result="114"/><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

    Name: Windows(TM) Vista, Ultimate edition

    Description: Windows Operating System - Vista, OEM_COA_SLP channel

    Activation ID: f79b5e33-4a4e-451c-9e8a-55dcc9bdb89d

    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f

    Extended PID: 89580-00144-008-717073-02-3081-6002.0000-1642011

    Installation ID: 002141551531995511322830311710422795409696973651065441

    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: 6MPBY

    License Status: Licensed

     

    Windows Activation Technologies-->

    N/A

     

    HWID Data-->

    HWID Hash Current: OgAAAAIAAwABAAEAAgADAAAAAgABAAEAeqjWSJmT5QH4n2AIkgBkCQYGje/y9M6fIDISme4RrFbI9A==

     

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

      FACP Nvidia NVDAACPI

      HPET Nvidia NVDAACPI

      MCFG Nvidia NVDAACPI

      SSDT PTLTD POWERNOW

     

     

     


    Sunday, June 12, 2011 4:05 PM
  • "Maximus_W" wrote in message news:9da3ac86-1918-4370-8bd7-83b81f286d75...

    After running through the fixes for a number of other cases of this error (sfc /scannow, another CMD fix I cannot remember, system restore etc.) the system has finally accepted the on-case product ID and is now showing as genuine in MGAdiag.

    Case closed, thank you very much for whichever of those many solutions in other threads ended up working for me in the end,
    Max W.

    New diag, just in case there's anything I should know to stop this happening again:

     

     

    Diagnostic Report (1.9.0027.0):

    -----------------------------------------

    Windows Validation Data-->

    Validation Status: Genuine

    Validation Code: 0

    Cached Online Validation Code: 0x0

    Windows Product Key: *****-*****-2PDWJ-6H3VR-6MPBY

    Windows Product Key Hash: hudW52w04SNIviQ52vvYWTjDOpY=

    Windows Product ID: 89580-OEM-7200874-17073

    Windows Product ID Type: 8

    Windows License Type: COA SLP

    Windows OS version: 6.0.6002.2.00010100.2.0.001

     

    Other data-->

    SYSTEM><Manufacturer>System Manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>2006/12/19</Version><SMBIOSVersion major="2" minor="4"/><Date>20080716000000.000000+000</Date></BIOS

    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



    Changing the Key to the COA Key is what did the trick - it would appear that for whatever reason, your PC is unable to read the BIOS SLIC table that should be present, and which is required to self-activate the OEM_SLP Key that you were formerly using.
     
    Having said that, it looks as if you have replaced the motherboard on that machine? In which case, the license is technically no linger valid. The original machine should have been an HP - this one appears to be a retail motherboard. It's always possible that updating the BIOS with a non-compliant version has caused the problem.
     
    You should also note that your installation of Office is non-genuine.
    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Maximus_W Sunday, June 12, 2011 4:58 PM
    Sunday, June 12, 2011 4:16 PM
    Moderator
  • Changing the Key to the COA Key is what did the trick - it would appear that for whatever reason, your PC is unable to read the BIOS SLIC table that should be present, and which is required to self-activate the OEM_SLP Key that you were formerly using.
    Having said that, it looks as if you have replaced the motherboard on that machine? In which case, the license is technically no linger valid. The original machine should have been an HP - this one appears to be a retail motherboard. It's always possible that updating the BIOS with a non-compliant version has caused the problem.
    You should also note that your installation of Office is non-genuine
    -- 

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

    The issue would be the instillation of a non-standard BIOS version then, though I had installed that at least a month ago with no issue and so didn't think it likely to be the culprit.

    Also for my version(s) of Office: I am aware that 2003 was not due to the license "running out" so to speak, though I thought I had fully uninstalled that, apparently not. The Office 2007 however should be a fully genuine, as-I believe-is shown in the above.

    Thanks a lot,
    Max W 


    Sunday, June 12, 2011 4:37 PM
  • "Maximus_W" wrote in message news:30bee1f0-ca64-43f9-ba63-4f41a2821c63...
    Changing the Key to the COA Key is what did the trick - it would appear that for whatever reason, your PC is unable to read the BIOS SLIC table that should be present, and which is required to self-activate the OEM_SLP Key that you were formerly using.
    Having said that, it looks as if you have replaced the motherboard on that machine? In which case, the license is technically no linger valid. The original machine should have been an HP - this one appears to be a retail motherboard. It's always possible that updating the BIOS with a non-compliant version has caused the problem.
    You should also note that your installation of Office is non-genuine
    -- 

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

    The issue would be the instillation of a non-standard BIOS version then, though I had installed that at least a month ago with no issue and so didn't think it likely to be the culprit.

    Also for my version(s) of Office: I am aware that 2003 was not due to the license "running out" so to speak, though I thought I had fully uninstalled that, apparently not. The Office 2007 however should be a fully genuine, as-I believe-is shown in the above.

    Thanks a lot,
    Max W 



    You must have been ignoring the requests to activate :)
    It's definitely the cause of your non-genuine issue.
    Yes, 2007 shows as being genuine - it's 2003 that has a problem. Unfortunately, it's not possible to rip the dregs of that out completely without ripping out 2007 as well...
    http://support.microsoft.com/kb/290301 shows how you can try it - but be prepared to have to reinstall 2007.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Sunday, June 12, 2011 5:02 PM
    Moderator
  • To be honest I think I may have simply been getting the key wrong... a few characters are looking a little tired on that sticker.
    Definitely good to know what the culprit was, I'll see if I can't reinstall the official BIOS while I'm at it then, all it's been is a pain since I put it on there.

    Thanks again for your help,
    Max W

    Sunday, June 12, 2011 5:15 PM