Answered by:
Windows Vista Activation

Question
-
Hi,
I keep getting the Windows Activation Error everytime I start my computer. I ran the Microsoft Genuine diagnostic test, which is posted below, and shows my copy is Genuine. My computer is also very slow, and I can not open control panel nor Windows update.
I appreciate your help.
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Status: Genuine
Validation Code: 0
Cached Online Validation Code: N/A, hr = 0x80004005
Windows Product Key: *****-*****-9D3HG-QXTGC-GM8FK
Windows Product Key Hash: mvBMowq25pNe2zCYwaFEnQYOuh4=
Windows Product ID: 89578-OEM-7318072-02609
Windows Product ID Type: 3
Windows License Type: OEM System Builder
Windows OS version: 6.0.6000.2.00010300.0.0.003
ID: {F4C043F0-88FC-4E5D-B10A-086110F08C96}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: Registered, 1.9.42.0
Signed By: Microsoft
Product Name: Windows Vista (TM) Home Premium
Architecture: 0x00000000
Build lab: 6000.vista_gdr.100218-0019
TTS Error: T:20100902060914531-
Validation Diagnostic:
Resolution Status: N/AVista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002Windows 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: 108 Invalid VLK
Microsoft Office Enterprise 2007 - 108 Invalid VLK
OGA Version: Registered, 2.0.48.0
Signed By: Microsoft
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Win32)
Default Browser: C:\Users\Amir\AppData\Local\Google\Chrome\Application\chrome.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-->
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{F4C043F0-88FC-4E5D-B10A-086110F08C96}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6000.2.00010300.0.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-GM8FK</PKey><PID>89578-OEM-7318072-02609</PID><PIDType>3</PIDType><SID>S-1-5-21-3447687706-1720876576-1197932123</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Inspiron 1501 </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>2.6.3 </Version><SMBIOSVersion major="2" minor="4"/><Date>20071207000000.000000+000</Date></BIOS><HWID>29303507018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Iran Standard Time(GMT+03:30)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL </OEMID><OEMTableID>M08 </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>108</Result><Products><Product GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>108</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>64BC76978749586</Val><Hash>GW6PzcEVEDTVKeO5Ym5UUm41dBk=</Hash><Pid>89388-707-0441865-65221</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="12" Result="108"/><App Id="16" Version="12" Result="108"/><App Id="18" Version="12" Result="108"/><App Id="19" Version="12" Result="108"/><App Id="1A" Version="12" Result="108"/><App Id="1B" Version="12" Result="108"/><App Id="44" Version="12" Result="108"/><App Id="A1" Version="12" Result="108"/><App Id="BA" Version="12" Result="108"/></Applications></Office></Software></GenuineResults>Spsys.log Content: U1BMRwEAAAAAAQAABAAAAFYQAAAAAAAAWmICADAgAAB6fJ2hP0rLAdKUkVDxCoM358lePs/mGn33kCl699N+B/5kcRUcRT8tMco8rc+2sVB4aJ08aIJcsDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAyuPJYEjuzrM7pi8z8IgTuM6LOneidtApN39hgIbVhCujy1BzfTwVh1q1HDg6XcP5YzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM
Licensing Data-->
Software Licensing service is not running.Windows Activation Technologies-->
N/AHWID Data-->
HWID Hash Current: NgAAAAEABAABAAEAAQABAAAAAwABAAEAJJSARnDbNpvya7iRkKYOmQDB8vTo0OhW6J2sVvr8OEM Activation 1.0 Data-->
N/AOEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no Windows marker
Windows marker version: N/A
OEMID and OEMTableID Consistent: yes
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC PTLTD APIC
FACP ATI Bowfin
MCFG PTLTD MCFG
TCPA AMD
SSDT PTLTD POWERNOW
SLIC DELL M08Tuesday, September 7, 2010 5:17 PM
Answers
-
Hello Soltanamir1,
TTS Error: T:20100902060914531-
Your Diagnostic Report is telling me that your Windows is suffering from a Trusted Store Tamper. In Windows, there are files that have, what is known as, a Digital Signature. A Digital Signature is an industry standard that ensures that a file is, in fact, from the specified source. If a file is modified, in any way, the Diagital Signature is broken.
Example: lets say you get a Printer Driver that is Digitally Signed from HP. Since the Digital Signature was created by a Trusted Source (HP) a Certificate is created within Window's Trusted Store. The Digital Signature is dependent on the file's Hash (think fingerprint) so if the file is changed in any way, it's Digital Signature is broken and becomes invalid. So lets say that the HP Driver got modified by some sort of Malware. The File's Hash would no longer match the hash listed in the Digitally Signature (or the Signature may not even be readable at that point). The Digital Signature become invalid because windows now don't know what has been done to that file, so the file can no longer be trusted. This in turn invalidates the corresponding Certificate within the Trusted Store.
What I have described in the above example is basically what is happening with your Windows. Some Digitally Signed file has been modified in some way and the Certificate within Windows's Trusted Store has become invalid (i.e. no longer trusted) which invalidates the Certificate in the Trusted Store and that is what has triggered the Non-Genuine messaging.
Unfortunatly, none of my tools are able to pinpoint which file/signature/certificate is causing the problem. However there are a few thing you can try that may correct the issue.
1) First off not all Digitally Signed files are Drivers, but from experience we have found that this issue seems to occure the most with Drivers. So my first suggestion is to confirm that all your hardware drivers are up to date. Note: Figuring out id a Driver is up to date and/or replacing a driver with a more current one can sometimes take semi-advanced computer knowledge and me explaining the process is outside the scope of this forum. If you do not know how to work with Drivers seak assistance or skip down to #2 or #3 below
2) Restore Windows back to a past System Restore Point.
1) Boot into Windows
2) Click the ‘Start’ button
3) In the Start Search field, type: System Restore and hit “Enter” keyboard key
4) 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 a date Before you first noticed the issue.
5) Click the "Next" button.
6) Reboot
3) Repair Windows using the 'sfc /scannow' command
The Scan Now will look for any bad Windows files and attempt to repair them, if possible (it isn't always able to)
1) Login to Windows
2) Click the Start button
3) Type: cmd.exe in the search field
4) Right-click the cmd.exe file and select Run as Administrator
5) In the CMD window, type: sfc /scannow
6) Reboot and see if that resolves the issue.
If none of my suggestions resolves the issue, then the only other thing I can suggest is to either create a (no cost) support request at http://support.microsoft.com/gp/contactwga or reinstall Windows.Note: Noel is correct that your Office was installed using a Volume License Key that is Invalid. Meaning it was not created by Microsoft.
Thank you,
Darin MS- Marked as answer by Darin Smith MS Tuesday, September 7, 2010 9:18 PM
Tuesday, September 7, 2010 9:16 PM
All replies
-
"Soltanamir1" wrote in message news:1827aa32-b2f0-4ac5-8fe5-3cc0cc36a69c...
Hi,
I keep getting the Windows Activation Error everytime I start my computer. I ran the Microsoft Genuine diagnostic test, which is posted below, and shows my copy is Genuine. My computer is also very slow, and I can not open control panel nor Windows update.
I appreciate your help.
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Status: Genuine
Validation Code: 0
Cached Online Validation Code: N/A, hr = 0x80004005
Windows Product Key: *****-*****-9D3HG-QXTGC-GM8FK
Windows Product Key Hash: mvBMowq25pNe2zCYwaFEnQYOuh4=
Windows Product ID: 89578-OEM-7318072-02609
Windows Product ID Type: 3
Windows License Type: OEM System Builder
Windows OS version: 6.0.6000.2.00010300.0.0.003
ID: {F4C043F0-88FC-4E5D-B10A-086110F08C96}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: Registered, 1.9.42.0
Signed By: Microsoft
Product Name: Windows Vista (TM) Home Premium
Architecture: 0x00000000
Build lab: 6000.vista_gdr.100218-0019
TTS Error: T:20100902060914531-
OGA Data-->
Office Status: 108 Invalid VLK
Microsoft Office Enterprise 2007 - 108 Invalid VLK
OGA Version: Registered, 2.0.48.0
Signed By: Microsoft
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3Your problem appears to be caused by Office, rather than by Windows - although you also have a tamper stamp that may be relevant, either because of a hacker's attempt to make your software look genuine, or for some other reason unconnected with your problem/I would suspect malware as a first cause - together with the non-genuine Office installation.When was the last time you ran a full system scan with an AV with up-to-date definitions? What AV are you using? what pother anti-malware software are you using?
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed SlothTuesday, September 7, 2010 7:17 PMModerator -
Hello Soltanamir1,
TTS Error: T:20100902060914531-
Your Diagnostic Report is telling me that your Windows is suffering from a Trusted Store Tamper. In Windows, there are files that have, what is known as, a Digital Signature. A Digital Signature is an industry standard that ensures that a file is, in fact, from the specified source. If a file is modified, in any way, the Diagital Signature is broken.
Example: lets say you get a Printer Driver that is Digitally Signed from HP. Since the Digital Signature was created by a Trusted Source (HP) a Certificate is created within Window's Trusted Store. The Digital Signature is dependent on the file's Hash (think fingerprint) so if the file is changed in any way, it's Digital Signature is broken and becomes invalid. So lets say that the HP Driver got modified by some sort of Malware. The File's Hash would no longer match the hash listed in the Digitally Signature (or the Signature may not even be readable at that point). The Digital Signature become invalid because windows now don't know what has been done to that file, so the file can no longer be trusted. This in turn invalidates the corresponding Certificate within the Trusted Store.
What I have described in the above example is basically what is happening with your Windows. Some Digitally Signed file has been modified in some way and the Certificate within Windows's Trusted Store has become invalid (i.e. no longer trusted) which invalidates the Certificate in the Trusted Store and that is what has triggered the Non-Genuine messaging.
Unfortunatly, none of my tools are able to pinpoint which file/signature/certificate is causing the problem. However there are a few thing you can try that may correct the issue.
1) First off not all Digitally Signed files are Drivers, but from experience we have found that this issue seems to occure the most with Drivers. So my first suggestion is to confirm that all your hardware drivers are up to date. Note: Figuring out id a Driver is up to date and/or replacing a driver with a more current one can sometimes take semi-advanced computer knowledge and me explaining the process is outside the scope of this forum. If you do not know how to work with Drivers seak assistance or skip down to #2 or #3 below
2) Restore Windows back to a past System Restore Point.
1) Boot into Windows
2) Click the ‘Start’ button
3) In the Start Search field, type: System Restore and hit “Enter” keyboard key
4) 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 a date Before you first noticed the issue.
5) Click the "Next" button.
6) Reboot
3) Repair Windows using the 'sfc /scannow' command
The Scan Now will look for any bad Windows files and attempt to repair them, if possible (it isn't always able to)
1) Login to Windows
2) Click the Start button
3) Type: cmd.exe in the search field
4) Right-click the cmd.exe file and select Run as Administrator
5) In the CMD window, type: sfc /scannow
6) Reboot and see if that resolves the issue.
If none of my suggestions resolves the issue, then the only other thing I can suggest is to either create a (no cost) support request at http://support.microsoft.com/gp/contactwga or reinstall Windows.Note: Noel is correct that your Office was installed using a Volume License Key that is Invalid. Meaning it was not created by Microsoft.
Thank you,
Darin MS- Marked as answer by Darin Smith MS Tuesday, September 7, 2010 9:18 PM
Tuesday, September 7, 2010 9:16 PM