Answered by:
I have purchased a Dell Desktop that was pre-loaded with Windows Vista Home Basic

Question
-
My hard drive was defective and replaced, however I keep getting an error after I have loaded Windows Vista from my Microsoft Windows Vista Disk. Please find attached copy of the diagnostic that I have just ran. Please advise, Thanks
Diagnostic Report (1.7.0095.0):
-----------------------------------------
WGA Data-->
Validation Status: Invalid License
Validation Code: 50
Online Validation Code: 0xc004d401
Cached Validation Code: N/A, hr = 0x80004005
Windows Product Key: *****-*****-4WD8X-M9WM7-CH4CG
Windows Product Key Hash: EkdqJZ28Y9zyrh7DU/lHNjTXlQY=
Windows Product ID: 89572-OEM-7332166-00096
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.0.6000.2.00010300.0.0.002
CSVLK Server: N/A
CSVLK PID: N/A
ID: {C74F0005-9F94-4369-A1C4-F2EB1EB0C6B1}(1)
Is Admin: Yes
TestCab: 0x0
WGA Version: Registered, 1.7.69.2
Signed By: Microsoft
Product Name: Windows Vista (TM) Home Basic
Architecture: 0x00000000
Build lab: 6000.vista_gdr.071009-1548
TTS Error: M:20080816000224046-
Validation Diagnostic:
Resolution Status: N/AWgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002WGA 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
WGATray.exe Signed By: N/A, hr = 0x80070002
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-282-80041010_025D1FF3-170-80041010_025D1FF3-171-1_025D1FF3-434-80040154_025D1FF3-178-80040154_025D1FF3-179-2_025D1FF3-185-80070002_025D1FF3-199-3Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 7.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: AllowedFile Scan Data-->
File Mismatch: C:\Windows\system32\dbghelp.dll[6.0.6000.16386]
File Mismatch: C:\Windows\system32\linkinfo.dll[6.0.6000.16386]Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{C74F0005-9F94-4369-A1C4-F2EB1EB0C6B1}</UGUID><Version>1.7.0095.0</Version><OS>6.0.6000.2.00010300.0.0.002</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-CH4CG</PKey><PID>89572-OEM-7332166-00096</PID><PIDType>2</PIDType><SID>S-1-5-21-861510402-291499973-764793281</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>0207 </Version><SMBIOSVersion major="2" minor="4"/><Date>20070801000000.000000+000</Date></BIOS><HWID>35313507018400F6</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>ÿÿÿÿÿÿ</OEMID><OEMTableID>ÿÿÿÿÿÿÿÿ</OEMTableID></OEM><BRT/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>Spsys.log Content: U1BMRwEAAAAAAQAABAAAAPQHAAAAAAAAYWECANOQG6Hm/d8Ibv/IARhDs/4hWdo7Xkl9D+HKpnipbGUX2R81ETtJEUkO3zQ/4wBfNaXoDlGK7nMMToqxeRY3hlB6ccWFlfEC2sD/66Ispx7rhI9+r66ao3IE3HUJsEGnmR0ReJ9KlWCJouxq6PAIwHwHVMfvNauSbFvmaTCDPKtQZQFIQcDXIAwFGl6D9S/GUDYecePFRKM/leS97bxOVVm9fICZUkfHdDNbo725QzYM7NoLIP6BsYz9FHAia30CP0z0OYRuUWLuf4S5JTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=
Saturday, August 16, 2008 7:47 AM
Answers
-
Hello Oakes,
The core to your particular issue centers on the line in your Diagnostic Report, that reads:
File Scan Data-->
File Mismatch: C:\Windows\system32\dbghelp.dll[6.0.6000.16386]
File Mismatch: C:\Windows\system32\linkinfo.dll[6.0.6000.16386]
This line means that these critical system files have either:
a) Been tampered/modified/become corrupt to the point that its Signature Hash no longer matches the Signature Hash listed in Vista's System Catalog.
Or
b) Been updated but the file's Signature Hash was not updated, in Vista's System Catalog to reflect the updated file's new Signature Hash.
Vista compares a Critical System file's Signature Hash with the Signature Hash listed in its System Catalog to determine if that Critical System file has been tampered with. When this happens, depending on the file that has been tampered, Vista may show as Genuine or Non-Genuine, but either way, Vista won't Validate correctly and may also exhibit other strange behavior.
To resolve your issue, we need to replace or repair the file so it's Signature Hash matches what is listed in Vista System Catalog. I can provide a couple of suggestions to do this:
A) Install Service Pack 1 for Vista (found at http://www.microsoft.com/downloads/details.aspx?FamilyID=b0c7136d-5ebb-413b-89c9-cb3d06d12674&DisplayLang=en). These files may be included in the SP1 install and if so, SP1 will overwrite the bad files with a Known-Good copy.
(Note: this is the simpler way to resolve, but be aware that I have not received confirmation that these files are, in fact, included in SP1. So if this option does not resolve the issue, please see option B).
B) Repair Windows using System Restore:
1) Reboot Vista into Safe Mode
2) Go to Control Panel
3) On the left hand side of the Control Panel window, Click on "Classic View"
4) Double-click "Backup and Restore Center"
5) On the left hand side of the window, click "Repair Windows using system restore"
6) 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 the date Before you first noticed the issue.
7) Click the "Next" button.
8) Reboot back into Normal mode
9) Vista should no longer be in Reduced Functionality mode
If neither of these solutions resolves your issue, the last resort, that I can provide, is to reinstall Vista. But before you do that, create a (no cost) support request at http://go.microsoft.com/fwlink/?linkid=52029 and see if they can provide any alternatives.
Thank you,
Darin Smith
WGA Forum Manager
Attention Forum All Users: Please Do Not post your issue in someone else's Thread...Create your own.- Marked as answer by Darin Smith MS Monday, August 18, 2008 8:31 PM
Monday, August 18, 2008 8:28 PM
All replies
-
Was the motherboard replaced as well? The area of your report below shows to be a retail motherboard and not a Dell OEM branded board. The CD key from your report is correct for Dell OEM SLP, but without the bios branding in the board, it wont activate with that SLP key.
If the motherboard has been replaced with a non-Dell you will need to phone activate with the COA sticker key on the case or replace the board with the correct Dell part number.
<Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.
<OEM><OEMID>ÿÿÿÿÿÿ</OEMID><OEMTableID>ÿÿÿÿÿÿÿÿ</OEMTableID>
- Edited by SuSe Saturday, August 16, 2008 6:34 PM edit
Saturday, August 16, 2008 6:30 PM -
Hello Oakes,
The core to your particular issue centers on the line in your Diagnostic Report, that reads:
File Scan Data-->
File Mismatch: C:\Windows\system32\dbghelp.dll[6.0.6000.16386]
File Mismatch: C:\Windows\system32\linkinfo.dll[6.0.6000.16386]
This line means that these critical system files have either:
a) Been tampered/modified/become corrupt to the point that its Signature Hash no longer matches the Signature Hash listed in Vista's System Catalog.
Or
b) Been updated but the file's Signature Hash was not updated, in Vista's System Catalog to reflect the updated file's new Signature Hash.
Vista compares a Critical System file's Signature Hash with the Signature Hash listed in its System Catalog to determine if that Critical System file has been tampered with. When this happens, depending on the file that has been tampered, Vista may show as Genuine or Non-Genuine, but either way, Vista won't Validate correctly and may also exhibit other strange behavior.
To resolve your issue, we need to replace or repair the file so it's Signature Hash matches what is listed in Vista System Catalog. I can provide a couple of suggestions to do this:
A) Install Service Pack 1 for Vista (found at http://www.microsoft.com/downloads/details.aspx?FamilyID=b0c7136d-5ebb-413b-89c9-cb3d06d12674&DisplayLang=en). These files may be included in the SP1 install and if so, SP1 will overwrite the bad files with a Known-Good copy.
(Note: this is the simpler way to resolve, but be aware that I have not received confirmation that these files are, in fact, included in SP1. So if this option does not resolve the issue, please see option B).
B) Repair Windows using System Restore:
1) Reboot Vista into Safe Mode
2) Go to Control Panel
3) On the left hand side of the Control Panel window, Click on "Classic View"
4) Double-click "Backup and Restore Center"
5) On the left hand side of the window, click "Repair Windows using system restore"
6) 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 the date Before you first noticed the issue.
7) Click the "Next" button.
8) Reboot back into Normal mode
9) Vista should no longer be in Reduced Functionality mode
If neither of these solutions resolves your issue, the last resort, that I can provide, is to reinstall Vista. But before you do that, create a (no cost) support request at http://go.microsoft.com/fwlink/?linkid=52029 and see if they can provide any alternatives.
Thank you,
Darin Smith
WGA Forum Manager
Attention Forum All Users: Please Do Not post your issue in someone else's Thread...Create your own.- Marked as answer by Darin Smith MS Monday, August 18, 2008 8:31 PM
Monday, August 18, 2008 8:28 PM