locked
Validation is gone ERROR:0XC004D401 RRS feed

  • Question

  • But I am infact using one of the products you mentioned!!!!
    Was working fine until todays afternoon.

    Diagnostic Report (1.7.0066.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0xc004d401
    Cached Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-4QKTD-M877R-Y7GR4
    Windows Product Key Hash: WPqhyJxirUbmRaTp2ZwR5z96osQ=
    Windows Product ID: 89576-009-8352656-71397
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.0.6000.2.00010100.0.0.006
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {3ED23529-2F3D-4FBD-8269-CC3795F2B611}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.7.36.0
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Business
    Architecture: 0x00000000
    Build lab: 6000.vista_gdr.071009-1548
    TTS Error: M:20071218163359215-
    Validation Diagnostic:
    Resolution Status: N/A

    Notifications Data-->
    Cached Result: N/A
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002

    Browser 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: Allowed

    File Scan Data-->

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAOEVAAAAAAAAWmICADAgAACH9isLhkHIAVMWKYGB4wMcsbz+lAen7WdbFbU8f/HznUWl8J6h6kCivlX+7GpIaF01L8jRld9QGe97BuxrKcj+9gzTrUJt+r2/sTYKYqfZu1RCiDwdZ3XKnKfOZv/AmB9uvmxWADGc/AFrdnzWO+jF8eq69LRpcSiTN/jEi/pgsTdkQKOEZadnYeIFmHEs83923aEKqaV7o+zn9064UC3nw4H6gZCOU0khLRUSI+U3SBDxSocUJDOz74TgJfOd1LfEdWT9Qb1zuiT+h08wRI5b3Ii0HwoRaNfY7o+X32CpOdJhHiPQVqyFM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxTFimBgeMDHLG8/pQHp+1nACpb75OPmO14RY7ML9E3JgXxfvVLUwvWJCzOu5+sAxnvewbsaynI/vYM061Cbfq9rI6tM/9F09oUCTMlyUTyIZynzmb/wJgfbr5sVgAxnPwBa3Z81jvoxfHquvS0aXEokzf4xIv6YLE3ZECjhGWnZ2HiBZhxLPN/dt2hCqmle6Ps5/dOuFAt58OB+oGQjlNJIS0VEiPlN0gQ8UqHFCQzs++E4CXzndS3xHVk/UG9c7ok/odPMESOW9yItB8KEWjX2O6Pl99gqTnSYR4j0FashTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMUxYpgYHjAxyxvP6UB6ftZzG54TBexhDX4bvf3JMR6y9LYdIayOs9fubB3IB/kt1h73sG7GspyP72DNOtQm36vRAq/uLZxjY6NhBSh5ubSUWcp85m/8CYH26+bFYAMZz8AWt2fNY76MXx6rr0tGlxKJM3+MSL+mCxN2RAo4Rlp2dh4gWYcSzzf3bdoQqppXuj7Of3TrhQLefDgfqBkI5TSSEtFRIj5TdIEPFKhxQkM7PvhOAl853Ut8R1ZP1BvXO6JP6HTzBEjlvciLQfChFo19juj5ffYKk50mEeI9BWrIUzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDA==


    Tuesday, December 18, 2007 4:00 PM

Answers

  • Hello Imax22,

     

    What is happening is called a Tamper State. A Tamper State occurs in Vista when an unauthorized change/modification was made to a Critical System file, in memory or on disk. There are 3 know ways that this could happen.
     
    1) A legitimate program was installed on the computer, which is incompatible with Vista (such as a Game or an Anti-Virus program). <-Most Common

    2)  A non-legitimate program was installed on the computer, which is incompatible with Vista (such as a Spyware or Malware program).

    3) Manual manipulation of the Critical System file by either one of the users of the computer or a Pirate that changed the files, burned them to a disk and sold it as Genuine Windows Vista.
     
     In addition to why a Tamper occurs, we need to also 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 yours breaks down like this:

        (year)  (month) (day) (time in 24format) (millisecond)
    M: 2007      12       18          1633                59215


    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/18

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 12/18/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/17/2007, 12/16/2007 and 12/15/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/18/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.

     

     

    Thank you,

    Darin Smith

    WGA Forum Manager

    Tuesday, December 18, 2007 6:04 PM
  • Hi Imax22,

     

    I beleive running a Repair from your Vista DVD should reinstall the Windows Installer that originaly came with Vista.

     

    I normally do not like to direct people to non-Microsoft information on the internet, but there are no Microsoft support docs with steps by step instuction on how to use the Windows Repair option. Therefore I did a search and found a very complete and user friendly write-up on how to use the Windows Repair option at http://www.bleepingcomputer.com/tutorials/tutorial148.html

     

    Thanks,

    Darin

     

    Thursday, December 20, 2007 9:26 PM

All replies

  • Hello Imax22,

     

    What is happening is called a Tamper State. A Tamper State occurs in Vista when an unauthorized change/modification was made to a Critical System file, in memory or on disk. There are 3 know ways that this could happen.
     
    1) A legitimate program was installed on the computer, which is incompatible with Vista (such as a Game or an Anti-Virus program). <-Most Common

    2)  A non-legitimate program was installed on the computer, which is incompatible with Vista (such as a Spyware or Malware program).

    3) Manual manipulation of the Critical System file by either one of the users of the computer or a Pirate that changed the files, burned them to a disk and sold it as Genuine Windows Vista.
     
     In addition to why a Tamper occurs, we need to also 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 yours breaks down like this:

        (year)  (month) (day) (time in 24format) (millisecond)
    M: 2007      12       18          1633                59215


    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/18

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 12/18/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/17/2007, 12/16/2007 and 12/15/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/18/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.

     

     

    Thank you,

    Darin Smith

    WGA Forum Manager

    Tuesday, December 18, 2007 6:04 PM
  • It looks like my Windows Installer was overwritten / destroyed / changed by the Installation od an University Programm.

    I can remember that i was asked if that is ok.

    the programm is called Rational Rose.

    Its an UML Editor.

    How can i now reinstall / deinstall and new install the Windows Installer 4.0???
    Can't find a standalone Instllation of this programm in the web?

    Or is an installtion from the Disk possible?

    Because reinstall the whole system is not an option!!!

    Hope you can help me.

    Wednesday, December 19, 2007 4:47 PM
  • Hi Imax22,

     

    I beleive running a Repair from your Vista DVD should reinstall the Windows Installer that originaly came with Vista.

     

    I normally do not like to direct people to non-Microsoft information on the internet, but there are no Microsoft support docs with steps by step instuction on how to use the Windows Repair option. Therefore I did a search and found a very complete and user friendly write-up on how to use the Windows Repair option at http://www.bleepingcomputer.com/tutorials/tutorial148.html

     

    Thanks,

    Darin

     

    Thursday, December 20, 2007 9:26 PM