Answered by:
Any thoughts on fixing this?

Question
-
I bought Windowx XP Professional (through my employer) along with my Dell back in 2002. I am having a the same probelm as most others. I did the diagnostic test and this is the result. Please let me know if I can fix this. Thank you.
Diagnostic Report (1.7.0095.0):
-----------------------------------------
WGA Data-->
Validation Status: Cryptographic Errors Detected
Validation Code: 0
Online Validation Code: N/A
Cached Validation Code: N/A
Windows Product Key: *****-*****-T6DFB-Y934T-YD4YT
Windows Product Key Hash: 3g4CZGFEDgbKmn/oB4pa2FZsssU=
Windows Product ID: 55274-OEM-2211906-00102
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 5.1.2600.2.00010100.2.0.pro
CSVLK Server: N/A
CSVLK PID: N/A
ID: {DE1226DE-27EE-47D1-B534-A310BFC36D72}(3)
Is Admin: Yes
TestCab: 0x0
WGA Version: Registered, 1.5.540.0
Signed By: N/A, hr = 0x80004005
Product Name: N/A
Architecture: N/A
Build lab: N/A
TTS Error: N/A
Validation Diagnostic: 025D1FF3-171-1
Resolution Status: Cryptographic Errors DetectedWgaER Data-->
ThreatID(s): N/A
Version: N/AWGA Notifications Data-->
Cached Result: 5
File Exists: Yes
Version: 1.5.540.0
WgaTray.exe Signed By: N/A, hr = 0x80004005
WgaLogon.dll Signed By: N/A, hr = 0x80004005OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
WGATray.exe Signed By: N/A, hr = 0x80004005
OGAAddin.dll Signed By: N/A, hr = 0x80070002OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-171-1Browser 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: Allowed
Download unsigned ActiveX controls: Prompt
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Prompt
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: AllowedFile Scan Data-->
File Mismatch: C:\WINDOWS\system32\winlogon.exe[5.1.2600.2180]
File Mismatch: C:\WINDOWS\system32\licdll.dll[5.1.2600.2180]
File Mismatch: C:\WINDOWS\system32\ntoskrnl.exe[5.1.2600.3093]
File Mismatch: C:\WINDOWS\system32\ntdll.dll[5.1.2600.2180]
File Mismatch: C:\WINDOWS\system32\kernel32.dll[5.1.2600.3119]
File Mismatch: C:\WINDOWS\system32\crypt32.dll[5.131.2600.2180]
File Mismatch: C:\WINDOWS\system32\advapi32.dll[5.1.2600.2180]
File Mismatch: C:\WINDOWS\system32\setupapi.dll[5.1.2600.2180]
File Mismatch: C:\WINDOWS\system32\oembios.bin[hr = 0x80070714]
File Mismatch: C:\WINDOWS\system32\oembios.dat[hr = 0x80070714]
File Mismatch: C:\WINDOWS\system32\oembios.sig[hr = 0x80070714]
File Mismatch: C:\WINDOWS\system32\syssetup.dll[5.1.2600.2180]Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{DE1226DE-27EE-47D1-B534-A310BFC36D72}</UGUID><Version>1.7.0095.0</Version><OS>5.1.2600.2.00010100.2.0.pro</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-YD4YT</PKey><PID>55274-OEM-2211906-00102</PID><PIDType>2</PIDType><SID>S-1-5-21-1060284298-1606980848-725345543</SID><SYSTEM><Manufacturer>Dell Computer Corporation</Manufacturer><Model>OptiPlex GX260 </Model></SYSTEM><BIOS><Manufacturer>Dell Computer Corporation</Manufacturer><Version>A05</Version><SMBIOSVersion major="2" minor="3"/><Date>20030226000000.000000+000</Date><SLPBIOS>Dell System,Dell Computer,Dell System,Dell System</SLPBIOS></BIOS><HWID>B1E53B4F01842052</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/><BRT/></MachineData> <Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>Saturday, May 17, 2008 3:02 AM
Answers
-
Ketling,
I am glad to hear that the issue has been fixed.
Lori MS
Monday, May 19, 2008 10:13 PM
All replies
-
Nevermind. I just did a search and found my answer and it fixed the problem. I went to the system32 directory in Windows and deleted the LegitCheckControl.dll file and then went back to the Genuine sight to validate. It worked.
Saturday, May 17, 2008 3:14 AM -
Ketling,
I am glad to hear that the issue has been fixed.
Lori MS
Monday, May 19, 2008 10:13 PM