When I logged in today there was an error about a change in my activation key and my copy of Windows is no longer genuine. When I go to re-activate it tells me the key is already in use.
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Status: Invalid License
Validation Code: 50
Cached Online Validation Code: 0xc004c4a8
Windows Product Key: *****-*****-48VGW-J9HH4-XC8P7
Windows Product Key Hash: F76AxlDt+IVaUQvyxVhnyLN9of4=
Windows Product ID: 89583-OEM-7359846-55424
Windows Product ID Type: 3
Windows License Type: OEM System Builder
Windows OS version: 6.0.6002.2.00010300.2.0.003
ID: {663B644E-5E67-4B7F-A8E1-D46D4D4E0289}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: Registered, 1.9.42.0
Signed By: Microsoft
Product Name: Windows Vista (TM) Home Premium
Architecture: 0x00000009
Build lab: 6002.vistasp2_gdr.100218-0019
TTS Error: T:20100705053838022-
Validation Diagnostic:
Resolution Status: N/A
OGA Data-->
Office Status: 103 Blocked VLK
Microsoft Office Professional Plus 2007 - 103 Blocked VLK
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
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-3
Partial Product Key: XC8P7
License Status: Unlicensed
You have a number of problems -
1) You definitely have a pirate copy of Office Professional copy of Office Pro Plus installed - it's a version that is not for sale to the general public, and it's using a Blocked Key.
2) You have a T-type Tamper.
Your best option to cure the tamper is to try a System Restore back to before it occured - in your case it is time-stamped
TTS Error: T:20100705053838022- (5th July at 05:38 a.m.)
This may only be the latest of a string - but it's the best date we are going to get, so try a System Restore back to before that date and time - if that fails to cure the tamper, then we'll need to go back another couple of days, as it may take up
to three days for the system to identify a tamper.
If that doesn't work, or you have no System Restore points, tehn you need to see if you can identify the culprit - which is usually a driver. What did you nstall during the three days before the tamper (2nd to 5th July)? Note that Drivers are used by Software
as well as hardware, so it may mean looking through the Event Viewer logs, as well as the Reliability Monitor logs for those three days to check what happened. Then try uninstalling any updated drivers, or new software.
If that doesn't cure the problem, the try a System File Check scan.
click on Start
type CMD.EXE in the Search box, and wait for the file to be found - right-click on it, and select Run as Administrator.
At the prompt, type
SFC /SCANNOW
and hit the Enter key
The scanner will start, and hopefully repair the file problems.
Once complete, run another MGADiag report, and paste it to your reply.
Noel Paton | Nil Carborundum Illegitemi |
CrashFixPC |
The Three-toed Sloth
