locked
Vista Activation Error 0XC004E003 RRS feed

  • Question

  • My laptop was in working order a few weeks ago. IDK really what happened. I stopped some services so it could speed up, and the next thing I know, I couldn't start it up. Then after a series of turning it on and off, I could finally access my computer. Then it said it needed to do a volume check on the C drive..after that, this is when the activation window started popping up. After putting in my Product Key, I then got the 0XC004E003 error. Hopefully, someone can help me with this problem. Here are the results of the Diagnostics:

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

    Cached Validation Code: 0xc004c4a8
    Windows Product Key: *****-*****-PFR9Q-2DKGJ-RR4TD
    Windows Product Key Hash: 8ocFgCygpLMaZC9mAUHwwIZwvcM=
    Windows Product ID: 89578-OEM-7332157-00174
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6001.2.00010300.1.0.003
    ID: {BD586E8D-EB95-4250-88CC-29B68F0D6CA1}(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: 6001.vistasp1_gdr.091208-0542
    TTS Error: T:20100313201819265-
    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: 2.0.48.0
    OGAExec.exe Signed By: Microsoft
    OGAAddin.dll Signed By: Microsoft

    OGA Data-->
    Office Status: 108 Invalid VLK
    Microsoft Office Enterprise 2007 - 108 Invalid VLK
    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

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\iexplore.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>{BD586E8D-EB95-4250-88CC-29B68F0D6CA1}</UGUID><Version>1.9.0019.0</Version><OS>6.0.6001.2.00010300.1.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-RR4TD</PKey><PID>89578-OEM-7332157-00174</PID><PIDType>2</PIDType><SID>S-1-5-21-2868385601-2202416375-1695292603</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Pavilion dv5 Notebook PC</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.07</Version><SMBIOSVersion major="2" minor="4"/><Date>20080717000000.000000+000</Date></BIOS><HWID>D9333507018400F6</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>HPQOEM</OEMID><OEMTableID>SLIC-MPC</OEMTableID></OEM><GANotification><File Name="OGAAddin.dll" Version="2.0.48.0"/></GANotification></MachineData><Software><Office><Result>108</Result><Products><Product GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>108</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>1BF8D8A9C9ACD86</Val><Hash>9g2cFime44GimOJ+Wlk57pXf6gQ=</Hash><Pid>89388-707-8166527-65579</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="12" Result="108"/><App Id="16" Version="12" Result="108"/><App Id="18" Version="12" Result="108"/><App Id="19" Version="12" Result="108"/><App Id="1A" Version="12" Result="108"/><App Id="1B" Version="12" Result="108"/><App Id="44" Version="12" Result="108"/><App Id="A1" Version="12" Result="108"/><App Id="BA" Version="12" Result="108"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAJ02AAAAAAAAYWECAARw6YbzMOcKFMPKAbMbMLOKGrSIP23t0mx8luyFQfAqibhY/JY5MT3h4Y6FvFZ8dT5pgPcgoK/LxJpC4jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAyJx6iwmlhc0eFuUBMYcqaPlPDMhLZIrGjnOH8DSAPddbnq1r+2Iuz4CmJpmCpezo0zkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM

    Licensing Data-->
    C:\Windows\system32\slmgr.vbs(1648, 9) (null): Catastrophic failure

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: PAAAAAIAAgABAAEABAACAAAAAwABAAEAJJS8sxU/mtRkFhAzcA24YZ7u8vR39uCP6kWi+Z7ddpSsVn4o

    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            30F2   
      FACP            HP            30F2   
      HPET            HP            30F2   
      BOOT            HP            30F2   
      MCFG            HP            30F2   
      SLIC            HPQOEM        SLIC-MPC
      SSDT            AMD           PowerNow



    Sunday, March 28, 2010 10:09 PM

Answers

  • Hello AnimeSuki,

     Your Diagnostic Report is telling me that you Vista is suffering from a Trusted Store Tamper.  There are files, in Windows, that have what is known as a Digital Signature. A Digital Signature is an industry standard that ensures that a file is, in fact, from the specified source

    Example: lets say you get a Printer Driver that is Digitally Signed from HP. Since the Digital Signature was created by a Trusted Source a Certificate is created within Window's Trusted Store. The Digital Signature is dependent on the file's Hash (think fingerprint) so if the file is changed in any way it's Digital Signature then becomes invalid.  So lets say that the HP Driver got modified by some sort of Malware. The File's Hash would no longer match the hash listed in the Digitally Signature (or the Signature may not even be readable at that point). The Digital Signature become invalid because windows now don't know what has been done to that file, so the file can no longer be trusted. This in turn invalidates the corresponding Certificate within the Trusted Store.

      What I have described in the above example is basically what is happening with your Vista.  Some Digitally Signed file has been modified in some way (replaced, rewritten or just become corrupt) and the Certificate within Windows's Trusted Store has become invalid (i.e. no longer trusted) and that is what has triggered the Non-Genuine messaging. (This issue also seems to cause the inability to Activate, as well)

      Unfortunatly, none of my tools are able to pinpoint which file/signature/certificate is causing the problem. However there are a few thing you can try that may correct the issue.


      1) First off not all Digitally Signed files are Drivers, but from experience we have found that this issue seems to occure the most with Drivers.  So my first suggestion is to confirm that all your hardware drivers are up to date. Note: Figuring out id a Driver is up to date and/or replacing a driver with a more current one can sometimes take semi-advanced computer knowledge and me explaining the process is outside the scope of this forum. If you do not know how to work with Drivers seak assistance or skip down to #2 or #3 below

      2) Restore Windows back to a past System Restore Point.

    1) Reboot Vista into Safe Mode
    2) Click the ‘Start’ button
    3) In the Start Search field, type: System Restore and hit “Enter” keyboard key
    4) Select "Choose Different Restore Point", Put a check in the box that says "Show restore points older than 5 days", select the restore point that corresponds to a date Before you first noticed the issue.
    5) Click the "Next" button.
    6) Reboot back into Normal mode

      3) Repair Windows using the 'sfc /scannow' command

    The Scan Now will look for any bad Windows files and attempt to repair them, if possible (it isn't always able to)

    1) Login to Vista in Normal Mode (not safe mode)
    2) Launch an Internet Browser
    3) Type: %windir%\system32\ in the browser's address field
    4) Scroll down till you find the file cmd.exe
    5) Right-click the file and select Run as Administrator
    6) In the CMD window, type: sfc /scannow
    7) Reboot twice and see if that resolves the issue.

    If none of my suggestions resolves the issue, then the only other thing I can suggest is to either create a (no cost) support request at http://support.microsoft.com/gp/contactwga or reinstall Vista.

    Thank you,


    Darin MS
    Monday, March 29, 2010 10:04 PM