locked
Cryptographic Errors Detected RRS feed

  • Question

  • Here are details:

    Diagnostic Report (1.5.0545.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Cryptographic Errors Detected
    Windows Product Key: *****-*****-PMHTC-66XDB-HPFTB
    Windows Product Key Hash: LhnIZ7AXncmvT6dqpBau3nCbO6o=
    Windows Product ID: 76447-OEM-2266705-00560
    Windows Product ID Type: 3
    Windows License Type: COA/System Builder
    Windows OS version: 5.1.2600.2.00010100.2.0.pro
    ID: e01957a9-c149-44b7-99df-0288d34d1c25
    Is Admin: Yes
    AutoDial: No
    Registry: 0x0
    WGA Version: Registered, 1.5.708.0
    Signed By: N/A, hr = 0x800b0100
    Validation Diagnostic:
    Resolution Status: Cryptographic Errors Detected

    System Scan Data-->
    Scan: Complete
    Cryptography: Complete

    Notifications Data-->
    Cached Result: 5
    File Exists: Yes
    Version: 1.5.554.0
    WgaTray.exe Signed By: Microsoft
    WgaLogon.dll Signed By: Microsoft

    OGA Data-->
    Office Status: 109
    Office Diagnostics: B4D0AA8B-467-80070002

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Prompt
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Allowed
    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>e01957a9-c149-44b7-99df-0288d34d1c25</UGUID><Version>1.5.0545.0</Version><OS>5.1.2600.2.00010100.2.0.pro</OS><PKey>*****-*****-*****-*****-HPFTB</PKey><PID>76447-OEM-2266705-00560</PID><PIDType>3</PIDType><SID>S-1-5-21-448539723-1284227242-682003330</SID><SYSTEM><Manufacturer>NVIDIA</Manufacturer><Model>AWRDACPI</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F6</Version><SMBIOSVersion major="2" minor="3"/><Date>20051205000000.000000+000</Date></BIOS><HWID>223C365701845076</HWID><UserLCID>0415</UserLCID><SystemLCID>0415</SystemLCID><TimeZone>Środkowoeuropejski czas stand.(GMT+01:00)</TimeZone></MachineData>      <Software><Office><Result>109</Result><Products/></Office></Software></GenuineResults> 


    Friday, September 29, 2006 6:28 PM

Answers

  • Voytech,

    Re-run the diagnostic tool. After you click continue, you will see a button on the bottom left that says " resolve". Click that and reboot, no matter what the tool says. Run the diag tool one more time, and it should say that you are genuine.

    Friday, September 29, 2006 6:53 PM

All replies

  • Voytech,

    Re-run the diagnostic tool. After you click continue, you will see a button on the bottom left that says " resolve". Click that and reboot, no matter what the tool says. Run the diag tool one more time, and it should say that you are genuine.

    Friday, September 29, 2006 6:53 PM
  • I did it and it didn't help. I've also stop crupto servces, deleted system32/catroot2 dir, restarted services and this didn't help as well. I have removed any firewall, antyvir, etc.
    Friday, September 29, 2006 7:31 PM
  • All right. This worked for me:

    To resolve this issue, click start, then run, then type in "regsvr32 -u %windir%\system32\legitcheckcontrol.dll". Afterwards, go to your c:\windows\system32 directory and delete "legitcheckcontrol.dll".

     
    Afterwards, manually reinstall the latest version of WGA at http://go.microsoft.com/fwlink/?linkid=69498.


    It seemed that there was problem with digital signature of file "legitcheckcontrol.dll", after right clicking it I couldn't see digital certyficate of it, so I've run through steps above and it helped
    Friday, September 29, 2006 8:35 PM
  • Voytech:

     

    Where did you get the previous version of LegitCheckControl.dll? I'm interested to see why it was not signed by Microsoft.

     

    -phil

    Friday, September 29, 2006 10:28 PM
  • I don't know. I have automatic updates enabled and after recent update my problems started.

    Rgrds,
    Voytech
    Saturday, September 30, 2006 7:44 AM
  • thanks it help me....it is really very helpful for me.....
    Monday, September 20, 2010 4:55 PM