locked
The message 'This copy of Windows is not genuine' has appeared on my screen. RRS feed

  • Question

  • Had this computer for around 3 years and there is now a message saying that the copy of Vista is not genuine.  It also mentions Build 6002 whatever that is.

    All we've done to the machine since we've had it is to upgrade the memory about 3 weeks ago, and having done that we had to update the BIOS. I guess it doesn't like it.  We've tried the slui.exe 4 option to try to get a phone number to speak to someone but that didn't work.

    Any help would be appreciated.

     

     

    Diagnostic Report (1.9.0019.0):

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

    WGA Data-->

    Validation Status: Invalid License

    Validation Code: 50

     

    Cached Validation Code: N/A, hr = 0xc004f012

    Windows Product Key: *****-*****-T3PCK-3FRWY-KKMRQ

    Windows Product Key Hash: l3Vu3XOYEcKE/ZqlRC9vew8kcKs=

    Windows Product ID: 89578-OEM-7332157-00180

    Windows Product ID Type: 2

    Windows License Type: OEM SLP

    Windows OS version: 6.0.6002.2.00010300.2.0.003

    ID: {F14239FE-3A9B-4501-A41E-CC9E87EA98E1}(1)

    Is Admin: Yes

    TestCab: 0x0

    WGA Version: N/A, hr = 0x80070002

    Signed By: N/A, hr = 0x80070002

    Product Name: Windows Vista (TM) Home Premium

    Architecture: 0x00000000

    Build lab: 6002.vistasp2_gdr.091208-0542

    TTS Error: 

    Validation Diagnostic: 

    Resolution Status: N/A

     

    WgaER Data-->

    ThreatID(s): N/A, hr = 0x80070002

    Version: 6.0.6001.18000

     

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

    OGAExec.exe Signed By: Microsoft

    OGAAddin.dll Signed By: Microsoft

     

    OGA Data-->

    Office Status: 100 Genuine

    Microsoft Office Professional Edition 2003 - 119 Cryptographics Error

    OGA Version: Registered, 2.0.48.0

    Signed By: Microsoft

    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_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:\Users\Vanessa\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>{F14239FE-3A9B-4501-A41E-CC9E87EA98E1}</UGUID><Version>1.9.0019.0</Version><OS>6.0.6002.2.00010300.2.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-KKMRQ</PKey><PID>89578-OEM-7332157-00180</PID><PIDType>2</PIDType><SID>S-1-5-21-575597325-3701719810-3412111378</SID><SYSTEM><Manufacturer>OEM</Manufacturer><Model>OEM</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>6.00 PG</Version><SMBIOSVersion major="2" minor="5"/><Date>20080119000000.000000+000</Date></BIOS><HWID>83323507018400F6</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00: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="{91110409-6000-11D3-8CFE-0150048383C9}"><LegitResult>119</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>3DD5B28B185B70C</Val><Hash>ITGihfd+/sd7N5hLd0dCCDWnZyA=</Hash><Pid>70145-OEM-5790214-13286</Pid><PidType>6</PidType></Product></Products><Applications><App Id="15" Version="11" Result="100"/><App Id="16" Version="11" Result="100"/><App Id="18" Version="11" Result="100"/><App Id="19" Version="11" Result="100"/><App Id="1A" Version="11" Result="100"/><App Id="1B" Version="11" Result="100"/><App Id="44" Version="11" 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-500180-02-2057-6000.0000-0572007

    Installation ID: 047220308956475910711591193220537373269221006032132670

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

    License Status: Notification

    Notification Reason: 0xC004F057.

     

    Windows Activation Technologies-->

    N/A

     

    HWID Data-->

    HWID Hash Current: NAAAAAEABAABAAEAAQABAAAAAgABAAEA6GHm6uaYPrIi9Kp2SOSU91L28vRagcaqrFaA1w==

     

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

      FACP IntelR AWRDACPI

      HPET IntelR AWRDACPI

      MCFG IntelR AWRDACPI

     

     


     


    Saturday, March 27, 2010 9:16 PM

Answers

  • Hello jakscrakers,

    Computers, which are built by large manufactures that come with Windows Pre-Installed, come with two (2) Product Keys:

    A)   OEM SLP: This key comes pre-installed in Windows, when it comes from the Factory. This key is geared to work with the OEM Bios Flag found only on that Manufacturer's computer hardware. So when Windows was installed using the OEM SLP key (at the factory) Vista looks at the motherboard's Bios and sees the OEM Bios Flag and Self-Activates. (that's why you did not need to Activate your computer after you brought it home)

     

    B)    COA SLP: This is the Product key that you see on the sticker on the side (or bottom) of your computer.The COA SLP key is a 'Back up' to the OEM SLP key in events where the OEM SLP key stops self-activating because it can no longer see the OEM Bios Flag. The key must be activated by Phone.

    (Note: All manufacturers that use the OEM SLP system are required by contract to include a Certificate of Authenticity (COA) sticker, that has a COA SLP key, on the computer).

     

       Your Windows is using an OEM SLP key, but (because you flashed the Bios) cannot see the OEM Bios Flag in the computer’s motherboard and is unable to Self-Activate.

      To fix the issue, you will need to change out the OEM SLP key with the COA SLP key.  The normal way to do this is to click the ‘Start’ button, right-click ‘Computer’, select ‘Properties’ and then click ‘Change Product Key’ (located in the lower right-hand side of the window). Enter the COA SLP key and follow the instructions in the Change Product Key Wizard.

     

    Alternate steps to change the product key

     

    1)    Click the Start button

    2)    Type: slui.exe 3 and hit the Enter key

    3)    Type in the Product key from the sticker on your computer

    4)    Click the Next button.

    5)    You will be asked if want to Activate, click ok

    6)    It will attempt to Activate by the internet and will return an Invalid Key error (this is ok, continue to step 7)

    7)    Click the Start button

    8)    Type: slui.exe 4 and hit the Enter key

    9)    Select your location in the drop down menu and click the Next button

    10) The next screen provides the number to call to Activate by Phone

     

    NOTE: when you call that number, you will first hear an Automated Voice. If the Automated Voice gives you an option to talk to a Live Activation Rep., select that option. If not, do not enter any numbers. This should force the Automated Voice to transfer you to a Live Activation Rep. Trying to Activate thru the Automated Voice will not work, in your case; only thru the Live Activation Rep. will your Activation be successful.

     Thank you,


    Darin MS
    Monday, March 29, 2010 9:43 PM

All replies

  • Hello jakscrakers,

    Computers, which are built by large manufactures that come with Windows Pre-Installed, come with two (2) Product Keys:

    A)   OEM SLP: This key comes pre-installed in Windows, when it comes from the Factory. This key is geared to work with the OEM Bios Flag found only on that Manufacturer's computer hardware. So when Windows was installed using the OEM SLP key (at the factory) Vista looks at the motherboard's Bios and sees the OEM Bios Flag and Self-Activates. (that's why you did not need to Activate your computer after you brought it home)

     

    B)    COA SLP: This is the Product key that you see on the sticker on the side (or bottom) of your computer.The COA SLP key is a 'Back up' to the OEM SLP key in events where the OEM SLP key stops self-activating because it can no longer see the OEM Bios Flag. The key must be activated by Phone.

    (Note: All manufacturers that use the OEM SLP system are required by contract to include a Certificate of Authenticity (COA) sticker, that has a COA SLP key, on the computer).

     

       Your Windows is using an OEM SLP key, but (because you flashed the Bios) cannot see the OEM Bios Flag in the computer’s motherboard and is unable to Self-Activate.

      To fix the issue, you will need to change out the OEM SLP key with the COA SLP key.  The normal way to do this is to click the ‘Start’ button, right-click ‘Computer’, select ‘Properties’ and then click ‘Change Product Key’ (located in the lower right-hand side of the window). Enter the COA SLP key and follow the instructions in the Change Product Key Wizard.

     

    Alternate steps to change the product key

     

    1)    Click the Start button

    2)    Type: slui.exe 3 and hit the Enter key

    3)    Type in the Product key from the sticker on your computer

    4)    Click the Next button.

    5)    You will be asked if want to Activate, click ok

    6)    It will attempt to Activate by the internet and will return an Invalid Key error (this is ok, continue to step 7)

    7)    Click the Start button

    8)    Type: slui.exe 4 and hit the Enter key

    9)    Select your location in the drop down menu and click the Next button

    10) The next screen provides the number to call to Activate by Phone

     

    NOTE: when you call that number, you will first hear an Automated Voice. If the Automated Voice gives you an option to talk to a Live Activation Rep., select that option. If not, do not enter any numbers. This should force the Automated Voice to transfer you to a Live Activation Rep. Trying to Activate thru the Automated Voice will not work, in your case; only thru the Live Activation Rep. will your Activation be successful.

     Thank you,


    Darin MS
    Monday, March 29, 2010 9:43 PM
  • Hi Darin

     

    Thanks for your reply. Only needed to go as far as step 5 and it accepted the activation code. 

     

    Problem solved. Thanks again.

     

    Ian.

    Wednesday, March 31, 2010 3:08 PM