Answered by:
WGA Invalid Key

Question
-
I am trying to update an old Windpws XP Pro machine, but in the windows update site I am getting an error with the key validation.
I have runned th WGA Support tool and got the following status n the windows key:
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Status: Invalid Product Key
Validation Code: 8
Cached Validation Code: N/A
Windows Product Key: *****-*****-6VDBY-4BQ36-FFRDQ
Windows Product Key Hash: EY0j7hfw+eTeSNp1fMt3Xeh+zaU=
Windows Product ID: 55274-640-3495653-23599
Windows Product ID Type: 1
Windows License Type: Volume
Windows OS version: 5.1.2600.2.00010100.3.0.pro
ID: {F85C623E-BB92-42FE-8986-EE9007B87B2B}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: Registered, 1.9.42.0
Signed By: Microsoft
Product Name: N/A
Architecture: N/A
Build lab: N/A
TTS Error: N/A
Validation Diagnostic: 025D1FF3-230-1
Resolution Status: N/AVista WgaER Data-->
ThreatID(s): N/A
Version: N/AWindows XP 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 = 0x80070002OGA 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 = 0x80070002OGA Data-->
Office Status: 103 Blocked VLK
Microsoft Office Enterprise 2007 - 103 Blocked VLK
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-230-1Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Win32)
Default Browser: C:\Arquivos de programas\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: AllowedFile Scan Data-->
File Mismatch: C:\WINDOWS\system32\oembios.bin[Hr = 0x800b0003]
File Mismatch: C:\WINDOWS\system32\oembios.dat[Hr = 0x800b0003]
File Mismatch: C:\WINDOWS\system32\oembios.sig[Hr = 0x800b0003]Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{F85C623E-BB92-42FE-8986-EE9007B87B2B}</UGUID><Version>1.9.0027.0</Version><OS>5.1.2600.2.00010100.3.0.pro</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-FFRDQ</PKey><PID>55274-640-3495653-23599</PID><PIDType>1</PIDType><SID>S-1-5-21-1645522239-113007714-854245398</SID><SYSTEM><Manufacturer>P4M80P</Manufacturer><Model>AWRDACPI</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F3</Version><SMBIOSVersion major="2" minor="3"/><Date>20060112000000.000000+000</Date></BIOS><HWID>64F335F70184226D</HWID><UserLCID>0416</UserLCID><SystemLCID>0416</SystemLCID><TimeZone>Hora oficial do Brasil(GMT-03:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>103</Result><Products><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-65678</Pid><PidType>14</PidType></Product></Products><Applications><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>Licensing Data-->
N/AWindows Activation Technologies-->
N/AHWID Data-->
N/AOEM Activation 1.0 Data-->
BIOS string matches: yes
Marker string from BIOS: 140E0:SYNNEX TECHNOLOGY INTERNATIONAL CORP|140E0:SYNNEX TECHNOLOGY INTERNATIONAL CORP|140E0:SYNNEX TECHNOLOGY INTERNATIONAL CORP
Marker string from OEMBIOS.DAT: N/A, hr = 0x80004005OEM Activation 2.0 Data-->
N/AI hope I can get some directions to solve this.
Regards,
Jean Araujo
Jean Araujo // Consultor - Unisys Brasil- Changed type Darin Smith MS Wednesday, June 29, 2011 10:31 PM
Tuesday, June 28, 2011 8:06 PM
Answers
-
"Jean Araujo" wrote in message news:805607ad-091b-415c-8ba5-cac03c7a16a2...
I am trying to update an old Windpws XP Pro machine, but in the windows update site I am getting an error with the key validation.
I have runned th WGA Support tool and got the following status n the windows key:
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Status: Invalid Product Key
Validation Code: 8
Cached Validation Code: N/A
Windows Product Key: *****-*****-6VDBY-4BQ36-FFRDQ
Windows Product Key Hash: EY0j7hfw+eTeSNp1fMt3Xeh+zaU=
Windows Product ID: 55274-640-3495653-23599
Windows Product ID Type: 1
Windows License Type: Volume
Windows OS version: 5.1.2600.2.00010100.3.0.pro
OGA Data-->
Office Status: 103 Blocked VLK
Microsoft Office Enterprise 2007 - 103 Blocked VLK
File Scan Data-->
File Mismatch: C:\WINDOWS\system32\oembios.bin[Hr = 0x800b0003]
File Mismatch: C:\WINDOWS\system32\oembios.dat[Hr = 0x800b0003]
File Mismatch: C:\WINDOWS\system32\oembios.sig[Hr = 0x800b0003]Other data-->
SYSTEM><Manufacturer>P4M80P</Manufacturer><Model>AWRDACPI</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F3</Version><SMBIOSVersion major="2" minor="3"/><Date>20060112000000.000000+000</Date></BIOSRegards,
Jean Araujo
Jean Araujo // Consultor - Unisys Brasil
You have some interesting results - none of which are good :(1) Your Windows Key is a Volume License Key which has been blocked for abuse2) Your Office installation has also been blocked for abuse3) There appears to be some form of malware present that is attempting to 'correct' the situation with the above two problems.You need to revert your system to the originally-installed (ex=factory) OS that came with the system, and then access the data properly.Your data will NOT survive such a process unless you back it up to external media first.
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth- Marked as answer by Darin Smith MS Wednesday, June 29, 2011 10:31 PM
Tuesday, June 28, 2011 9:37 PMModerator
All replies
-
"Jean Araujo" wrote in message news:805607ad-091b-415c-8ba5-cac03c7a16a2...
I am trying to update an old Windpws XP Pro machine, but in the windows update site I am getting an error with the key validation.
I have runned th WGA Support tool and got the following status n the windows key:
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Status: Invalid Product Key
Validation Code: 8
Cached Validation Code: N/A
Windows Product Key: *****-*****-6VDBY-4BQ36-FFRDQ
Windows Product Key Hash: EY0j7hfw+eTeSNp1fMt3Xeh+zaU=
Windows Product ID: 55274-640-3495653-23599
Windows Product ID Type: 1
Windows License Type: Volume
Windows OS version: 5.1.2600.2.00010100.3.0.pro
OGA Data-->
Office Status: 103 Blocked VLK
Microsoft Office Enterprise 2007 - 103 Blocked VLK
File Scan Data-->
File Mismatch: C:\WINDOWS\system32\oembios.bin[Hr = 0x800b0003]
File Mismatch: C:\WINDOWS\system32\oembios.dat[Hr = 0x800b0003]
File Mismatch: C:\WINDOWS\system32\oembios.sig[Hr = 0x800b0003]Other data-->
SYSTEM><Manufacturer>P4M80P</Manufacturer><Model>AWRDACPI</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F3</Version><SMBIOSVersion major="2" minor="3"/><Date>20060112000000.000000+000</Date></BIOSRegards,
Jean Araujo
Jean Araujo // Consultor - Unisys Brasil
You have some interesting results - none of which are good :(1) Your Windows Key is a Volume License Key which has been blocked for abuse2) Your Office installation has also been blocked for abuse3) There appears to be some form of malware present that is attempting to 'correct' the situation with the above two problems.You need to revert your system to the originally-installed (ex=factory) OS that came with the system, and then access the data properly.Your data will NOT survive such a process unless you back it up to external media first.
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth- Marked as answer by Darin Smith MS Wednesday, June 29, 2011 10:31 PM
Tuesday, June 28, 2011 9:37 PMModerator -
Hi Noel,
Thanks for your directions. It helped me to understand better what is happening in this machine.
Regards,
Jean Araujo
Jean Araujo // Consultor - Unisys BrasilThursday, June 30, 2011 1:10 AM