Hello russlunn,
Vista is in, what is called a 'Mod-Auth' Tamper state. There are 2 types of Mod-Auth tampers.
1) A critical system file was modified On Disk - What this means is that the file, located on the hard drive, was modified in some way. This can be caused by random file corruption, a malicious program (spyware, malware, virus) or by manual file modification (by a user of the system). There is also a very small chance that an Update may fail in mid-update and cause this type of issue. As a safety mechanism, Updates are made so that if they fail, they roll back any updating that was done before the failure, but there is an off-chance that the roll back did not occure.
2) A critical system file was modified In Memory - What this means is the file itself (on the hard drive) is un-modified, but the code, from that file, running in the system, was modified in some way. and is usually caused by a running program that is incompatible with Vista.
Because there is No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, I beleive your issue is a In Memory Mod-Auth. Meaning that when Vista tells you it is non-genuine, there is a program Running that is attempting to do something that Vista does not allow (i.e. the program is incompatible with Vista)
In addition to why a Tamper occurs, it's also important to understand how Vista detects the Tamper event. There is a Service that runs in Vista that detects a Tamper to a Critical System file. But this Service runs randomly, so if you were to install an incompatible program and run it, Vista (most likely) would not immediately enter a Tamper State and it could take some time for the Tamper to be detected. The important point to note is that the moment Vista detects the Tamper, you know that the program that caused the tamper, is currently running.
Below I have provided a number of steps to help you identify the program that is causing the tamper:
First, go to http://support.microsoft.com/kb/931699/ and confirm that you do not have any of the programs known to cause this type of issue.
Second, in your Diagnostic report above, you can see the line that starts with 'TTS Error:' followed by a bunch numbers: M:xxxxxxxxxxxxxxxxx- This is the Tamper Time Stamp and it breaks down like this:
(year) (month) (day) (time in 24format) (millisecond)
M: 2007 12 29 1149 41977-
Note: I also see a "K" type Tamper Time Stamp. The K stands for Kermel Mode tamper. This is a minor tamper and is most likey directly related to the Mod-Auth tamper. Once you remove the program that is causing the Mod-Auth tamper, I believe that the Kernel mode tamper will stop as well.
Now that you know the time of the tamper, you can now try to connect that time with a program.
1) Login to Vista and select the option that launches an Internet Browser
2) Type into the browser address bar: %windir%\system32\perfmon.msc and hit Enter
3) When asked if you want to Open or Save this file, select Open
4) In the left hand panel, click Reliability Monitor
5) Click on the “System Stability Chart” above the date 12/29
6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 12/29/2007"
7) Look for any program that shows "Application Install" in the 'Activity' column.
8) Since the process that detects Tampers runs randomly, it can take up to 3 days for the process to detect the tamper and set Vista to a Tamper State. Because of this, please repeat steps 5) thru 7) for the dates 12/28/2007, 12/27/2007 and 12/26/2007
This could tell us what programs were installed on or around the Tamper date and should help you narrow down the possible programs that could be causing the issue . Unfortunately, if you installed the program (say) on 09/01/2007, but you didn't run (and, hence, prompted the tamper state) till 12/29/2007, this process may not be helpful. The removal of any application you may have installed recently could go a long way to troubleshooting this issues as well since it may fall outside of the 3 day time frame described above.
Lastly, I just received a confirmed report that PC Tools Firewall Plus version 3.0.0.52 (with Anti-Injection Protected option enabled) has been found to cause this type of issue. PC Tools has fixed the problem. On the PC Tools forums (http://www.pctools.com/forum/showthread.php?s=7e262d016b2a208f58a2d03143ba90a0&t=49501&page=2), they state:
In order to make sure you have the latest version, you can make a simple test after installation.
Test 1:
a. Restart the machine
b. Try to perform Smart Update (if no files appear then you have the latest)
Test 2:
a. Go to the FW directory (normally C:\Program Files\PC Tools Firewall Plus) and check that:
FirewallWrapper.dll version is 3.0.0.53
FWService.exe version is 3.0.0.53
FwHook.dll version is 1.0.44.0
sdwvhlp.dll version is 1.0.0.2
If the files version does not match try to Smart Update.
So if you have PC Tools Firewall Plus version 3.0.0.52 installed on your computer, please follow the above directions for updating to the most recent version.
Thank you,
Darin Smith
WGA Forum Manager
