Hi Rob,
My apologies, I misread your error code. This is a common error caused by a incompatible program conflicting with Vista.
You state that you do not have any of the programs that are known to cause this error, but I just want to confirm specifically that you do not have any of the below software installed:
- Blumentals Software iNET Protector (all versions)
-"nProtect GameGuard" protection from INCA Internet Co., LTD, when this protection is used in association with a currently installed game (Note A game that uses nProtect GameGuard shows a GameGuard splash screen when you start the game.)
-PC Tools Spyware Doctor (versions earlier than 4.0)
-Trend Micro PC-cillin Internet Security (versions earlier than 14.56)
-Trend Micro OfficeScan (versions earlier than 8.0)
-TuneUp Utilities (versions released earlier than 2007)
-Maplestory (Current versions are compatable)
-9 Dragons (Current versions are compatable)
-Flyff (Current versions are compatable)
(Other applications may also be incompatible with Windows Vista.)
If you do nothave any of the above software installed, then we will need to identify the software that is causing the problem
What's happening is called a Tamper State. There is a program that is incompatible with Vista and when that program does something that Vista doesn't allow, Vista goes into a No-genuine state.
There is two types of programs that cause a Tamper State
a) A program that can be launched at any time, by the user (such as a game or application)
b) A program that launches at Start up and that contently runs (such as an anti virus program)
For a) type programs, once you reboot, Vista goes back to a genuine state (because the program is no longer running)
For b) type programs, if you reboot, Vista is still in the tamper state because the program automatically re-launched after re-boot.
I believe you are experiencing a Tamper state caused by the a) type of programs since you seem to be popping back and forth between non-genuine and genuine. The key is identifying the offending program and either deleting it or upgrading is to a Vista compatible version.
In your Diagnostic report above, you can see the line that starts with 'TTS Error:' followed by a bunch of letters and numbers: K:20070926210903012- M:20070927093219045-
If you break down the numbers, you will get a time stamp:
(year) (month) (day) (time in 24format) (millisecond...I think)
K: 2007 09 26 2109 03012
M: 2007 09 27 0932 19045
In your case you have 2 tampers, and since they are different dates/times, It may be two programs causing the problems or it may be just one that did different things (that Vista didn't like) on two different days.
Now that we know the times of the tamper, you can now try to tie that tamper time with a program.
You do that by:
1) Click the 'Start' button
2) Right Click 'Computer'
3) Select 'Manage'
4) Continue thru the "Windows needs your permission to continue" window (if any)
5) Click the arrow next to 'Reliability and Performance'
6) Click the arrow next to 'Monitoring Tools'
7) Click on 'Reliability Monitor'
8) Click on the graph above the date 9/27/2007
9) Below the graph, look at the report titled "Software (Un)Installs for 9/27/2007"
10) Look for any program that shows "Application Install" in the 'Activity' column.
11) Repeat steps 8) thru 10) for date 9/26/2007
12) The time you installed the software may not be the time the tamper state started. This is because if can be up to 3 days between the times the proccess that detects tampers, runs. Because of this, you should also Repeat steps 8) thru 10) for date 9/25/2007, 9/24/2007 and 9/23/2007
This will tell you what programs were installed on the Tamper dates 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) until the tamper date(s), this process may not be helpful.
Please tell me if this helps you resolve the issue. If not, I will have additional steps for you to try.
Thank you,
Darin Smith
WGA Forum Manager
Update on error 0xC004D401
>
