locked
Pls help me! Windows XP not genuine! RRS feed

  • Question

  • Why my windows is not genuine???

    Diagnostic Report (1.5.0717.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Cryptographic Errors Detected
    Windows Product Key: *****-*****-T6DFB-Y934T-YD4YT
    Windows Product Key Hash: 3g4CZGFEDgbKmn/oB4pa2FZsssU=
    Windows Product ID: 76487-OEM-2211906-00102
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 5.1.2600.2.00010100.2.0.pro
    ID: e5c115b7-2f55-4ae2-bc53-7643295b1780
    Is Admin: Yes
    AutoDial:
    Registry: 0x0
    WGA Version: Registered, 1.5.540.0
    Signed By: N/A, hr = 0x80096005
    Validation Diagnostic:
    Resolution Status: N/A

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

    Notifications Data-->
    Cached Result: 5
    File Exists: Yes
    Version: 1.5.540.0
    WgaTray.exe Signed By: N/A, hr = 0x80096005
    WgaLogon.dll Signed By: N/A, hr = 0x80096005

    OGA Data-->
    Office Status: 114
    Office Diagnostics:

    Browser Data-->
    Proxy settings: hq-proxy-02:8080
    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: 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-->
    File Mismatch: c:\windows\system32\winlogon.exe
    File Mismatch: c:\windows\system32\licdll.dll
    File Mismatch: c:\windows\system32\dpcdll.dll
    File Mismatch: c:\windows\system32\ntoskrnl.exe
    File Mismatch: c:\windows\system32\ntdll.dll
    File Mismatch: c:\windows\system32\kernel32.dll
    File Mismatch: c:\windows\system32\crypt32.dll
    File Mismatch: c:\windows\system32\advapi32.dll
    File Mismatch: c:\windows\system32\setupapi.dll
    File Mismatch: c:\windows\system32\pidgen.dll
    File Mismatch: c:\windows\system32\oembios.bin
    File Mismatch: c:\windows\system32\oembios.dat
    File Mismatch: c:\windows\system32\oembios.sig
    File Mismatch: c:\windows\system32\syssetup.dll

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>e5c115b7-2f55-4ae2-bc53-7643295b1780</UGUID><Version>1.5.0717.0</Version><OS>5.1.2600.2.00010100.2.0.pro</OS><PKey>*****-*****-*****-*****-YD4YT</PKey><PID>76487-OEM-2211906-00102</PID><PIDType>2</PIDType><SID>S-1-5-21-1614895754-436374069-725345543</SID><SYSTEM><Manufacturer>Dell Inc.                </Manufacturer><Model>Precision WorkStation 380    </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.                </Manufacturer><Version>A02</Version><SMBIOSVersion major="2" minor="3"/><Date>20050524000000.000000+000</Date><SLPBIOS>Dell System,Dell Computer,Dell System,Dell System</SLPBIOS></BIOS><HWID>AEEB3E1F0184E05C</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>SE Asia Standard Time(GMT+07:00)</TimeZone><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID></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-57231</Pid><PidType>14</PidType></Product></Products></Office></Software></GenuineResults> 

     

    Thursday, November 23, 2006 3:16 AM

Answers

  • Thangtx,

    Rerun the mgadiag utility (the program that generated the report you posted).  After it runs and displays results, look on the Windows tab, in the lower left, for the "Resolve" button.  Click it, let it do its thing, and no matter what the result or message, when it is done, restart the computer.  The "Resolve" button runs a script that can correct the "cryptographic errors detected" condition.

    Upon restart and login, go to http://www.microsoft.com/genuine/default.mspx?displaylang=en and run validation once more.

    Finally restart and login. Let us know how you do

    Also, some bad news:  Your Office 2003 Pro installation is showing as Nongenuine (Office status=114 means nongenuine).  If this comes as a surprise to you, please go back to where you purchased the installed copy of Office and let them know that it is a counterfeit copy and that you would like a genuine copy or a refund.

    Thursday, November 23, 2006 3:20 AM

All replies

  • Thangtx,

    Rerun the mgadiag utility (the program that generated the report you posted).  After it runs and displays results, look on the Windows tab, in the lower left, for the "Resolve" button.  Click it, let it do its thing, and no matter what the result or message, when it is done, restart the computer.  The "Resolve" button runs a script that can correct the "cryptographic errors detected" condition.

    Upon restart and login, go to http://www.microsoft.com/genuine/default.mspx?displaylang=en and run validation once more.

    Finally restart and login. Let us know how you do

    Also, some bad news:  Your Office 2003 Pro installation is showing as Nongenuine (Office status=114 means nongenuine).  If this comes as a surprise to you, please go back to where you purchased the installed copy of Office and let them know that it is a counterfeit copy and that you would like a genuine copy or a refund.

    Thursday, November 23, 2006 3:20 AM
  • I have do steps you show but when I run validation windows say not allow to run ActiveX because invalid publisher. I turn off this option in Internet Explorer allow file to run event if signature is invalid, windows say that Validation Complete and I can access resources for genuine Windows users but it still have a notify me that my windows is not genuine. What can i do now?
    Thursday, November 23, 2006 5:49 AM