locked
Renaming pending.xml caused a "not genuine" notification to appear in Vista RRS feed

  • Question

  • Hi everyone,

    I have a HP dv6690ev running on vista and a few days ago I downloaded SP2. However, as my laptop was trying to install SP2, I kept receiving a "configuring updates stage 3 of 3. 0% complete" message which lead my computer into a reboot loop - couldn't go anywhere beyond 0%. I followed the advanced solution at http://support.microsoft.com/kb/949358/en-us and renamed the pending.xml file as it was asked.

    However, now I get a "Windows Vista Build 6002" notification followed by a "Not genuine" indication at the lower right corner of my desktop. I ran the diagnostics and I got:

    Diagnostic Report (1.9.0011.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50

    Cached 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: {B355A921-6BE1-4739-96C4-54CCE4094BEB}(3)
    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.lh_sp2rtm.090410-1830
    TTS Error:
    Validation Diagnostic:
    Resolution Status: N/A

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

    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: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 103 Blocked VLK
    Microsoft Office FrontPage 2003 - 100 Genuine
    Microsoft Office Enterprise 2007 - 103 Blocked VLK
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 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>{B355A921-6BE1-4739-96C4-54CCE4094BEB}</UGUID><Version>1.9.0011.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-3154667609-3131933434-1096497126</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Pavilion dv6500 Notebook PC    </Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.23     </Version><SMBIOSVersion major="2" minor="4"/><Date>20071003000000.000000+000</Date></BIOS><HWID>3C333507018400FA</HWID><UserLCID>0809</UserLCID><SystemLCID>0408</SystemLCID><TimeZone>Χειμερινή ώρα GTB(GMT+02: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>103</Result><Products><Product GUID="{90170409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office FrontPage 2003</Name><Ver>11</Ver><Val>5EA9C3672EB0500</Val><Hash>GZD+9sfb5ecL3RxyV4F75a86u2M=</Hash><Pid>72079-640-0000106-55169</Pid><PidType>14</PidType></Product><Product GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>103</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>ACD7202654E586</Val><Hash>fFic3JgCreGGRxyF8uMWB4R4Jcg=</Hash><Pid>89388-707-1528066-65200</Pid><PidType>14</PidType></Product></Products><Applications><App Id="17" Version="11" Result="100"/><App Id="15" Version="12" Result="103"/><App Id="16" Version="12" Result="103"/><App Id="18" Version="12" Result="103"/><App Id="19" Version="12" Result="103"/><App Id="1A" Version="12" Result="103"/><App Id="1B" Version="12" Result="103"/><App Id="44" Version="12" Result="103"/><App Id="A1" Version="12" Result="103"/><App Id="BA" Version="12" Result="103"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: 0x80070002

    Licensing Data-->



    HWID Data-->
    HWID Hash Current: PgAAAAEABgABAAEAAQABAAAABQABAAEAJJSkUBDePF7WdXB6kiQso0aDGH6o+/L0VCYLR5CzsmOsVpxuKoU=

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x20000
    OEMID and OEMTableID Consistent: yes
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            HP            30D2   
      FACP            HP            30CC   
      HPET            HP            30D2   
      BOOT            HP            30D2   
      MCFG            HP            30D2   
      TMOR            HP            30CC   
      APIC            HP            30D2   
      SLIC            HPQOEM        SLIC-MPC
      SSDT            HP            30D2   
      SSDT            HP            30D2   
      SSDT            HP            30D2   
      SSDT            HP            30D2   


    I tried to restore the license by typing cscript %windir%\System32\slmgr.vbs /ilc %windir%\System32\licensing\ppdlic\Security-Licensing-SLC-ppdlic.xrm-ms in the cmd window and rebooting twice, but nothing happened.

    I also typed sfc /scannow in the cmd window and vista detected destroyed files that couldn't be fixed. However, I have no access to the cbs.log file to see which files are these.

    Could you please help me on this?  I am not sure what to do? Reinstall?
    I would really appreciate your advise



    Wednesday, July 15, 2009 5:57 PM

Answers

  • Hi Darin.

    Thanks for answering!

    I tried to change the OEM key to the COA SLP, but it just couldn't recognize it as a valid key. Moreover, I started getting a DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen, which I didn't know if it was the symptom or the actual cause... So, I got so frustrated from the whole situation that I did reinstall vista.


    I didn't try however the activation by phone. It could have worked...


    Thank you so much for giving time on this Darin...
    Saturday, July 18, 2009 3:11 PM

All replies

  • Hello foteini,

      "Could you please help me on this?  I am not sure what to do? Reinstall?"

       Sometimes it's the only option, but I don't like to recommend Reinstalling untill I have exhausted any other possible alternatives. 

    On to the issue:

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

    A)   OEM SLP: This key comes pre-installed in Vista, when it comes from the Factory. This key is geared to work with the special instructions found only on that Manufacturer's computer hardware. So when Vista was installed using the OEM SLP key (at the factory) Vista looks at the motherboard and sees the special instructions 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. It is a valid product key, but should only be used in limited situations. 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 Vista is using an OEM SLP key.  I believe the possible issue is that (for whatever reason) Vista cannot see the special instructions in the computer’s motherboard and is unable to Self-Activate.

      So the first thing I would like you to try is 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.

    Tell me if that does the trick for you,
    Darin MS

    • Proposed as answer by Darin Smith MS Thursday, July 16, 2009 3:38 PM
    Thursday, July 16, 2009 3:38 PM
  • Hi Darin.

    Thanks for answering!

    I tried to change the OEM key to the COA SLP, but it just couldn't recognize it as a valid key. Moreover, I started getting a DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen, which I didn't know if it was the symptom or the actual cause... So, I got so frustrated from the whole situation that I did reinstall vista.


    I didn't try however the activation by phone. It could have worked...


    Thank you so much for giving time on this Darin...
    Saturday, July 18, 2009 3:11 PM