none
Vista Error - 0xc004d401 RRS feed

  • Question

  • Error on Vista. No new programs installed unless Synmanted downloaded updates.

     

    Here is my error report:

     

    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: *****-*****-2BXGW-B3XD4-8732Q
    Windows Product Key Hash: /2PlEVpt93FUZcJsa12bz/tyTT8=
    Windows Product ID: 89578-022-6974135-71726
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.0.6000.2.00010300.0.0.003
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {151B88B4-5932-4E26-ADB8-50A0A0814168}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.7.59.1
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6000.vista_gdr.071009-1548
    TTS Error: K:20080104094514981-M:20080103193502089-
    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

    OGA Data-->
    Office Status: 100 Genuine
    OGA Version: Registered, 1.6.21.0
    Signed By: Microsoft
    Office Diagnostics: 025D1FF3-282-80041010_025D1FF3-170-80041010_025D1FF3-171-1_025D1FF3-434-80040154_025D1FF3-178-80040154_025D1FF3-179-2_025D1FF3-185-80070002_025D1FF3-199-3

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

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{151B88B4-5932-4E26-ADB8-50A0A0814168}</UGUID><Version>1.7.0066.0</Version><OS>6.0.6000.2.00010300.0.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-8732Q</PKey><PID>89578-022-6974135-71726</PID><PIDType>5</PIDType><SID>S-1-5-21-423874257-1291142265-2262993464</SID><SYSTEM><Manufacturer>INTEL_</Manufacturer><Model>D975XBX2</Model></SYSTEM><BIOS><Manufacturer>Intel Corp.</Manufacturer><Version>BX97520J.86A.2802.2007.1024.1947</Version><SMBIOSVersion major="2" minor="4"/><Date>20071024000000.000000+000</Date></BIOS><HWID>9B323507018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><BRT/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0012-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Standard 2007</Name><Ver>12</Ver><Val>83E33037FEC2F0C</Val><Hash>KAeGgS1m7hETliyCRcsmuBcpGeI=</Hash><Pid>81607-902-0428626-64470</Pid><PidType>1</PidType></Product></Products></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAK/StgAAAAAAWmICADAgAACSaqWkaU7IARhDs/4hWdo7Xkl9D+HKpngBafXpiELJN81Mm3KH+aqJ7RJ8szRaqS91UzVn9bkiJFF0H9Oh+hJEw7XKSAShRbfiKPA5Qnlr3gCEpM+IbkvZ1mjkjzXhcq94m48ceJqGOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y0OKm53Bw867hHNE43WvZqUI0Rf1MqA3D5sWfEw7WeNfzOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

     

    Darren, can you tell me what to do to correct this error?

     

    Thanks,

     

    Ron

     

    Friday, January 4, 2008 5:43 PM

Answers

  •  

    Hello Ron,

     

      Your Vista is in, what is known as 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, your issue is an In Memory Mod-Auth. This means there is a program install and Running that is trying to access parts of the OS that Vista does not allow which, by definition, means it 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:2008       01      03         1935                02089

    In your case, there is also a 'K' type TTS listed (K:20080104094514981) A 'K' type tamper is also know as a Kernel Mod tamper and it is a minor issue I beleive this tamper can be directly attributed to the Mod-Auth tamper and once that is fixed, the kernel mod tamper should disappear.


    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 01/03

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 01/03/2008"

    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 01/02/2008, 01/01/2008 and 12/31/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 01/03/2008, 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, in addition to the list of incompatible programs found un the URL above, 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 updateing to the most recent version.

     

    Thank you,

    Darin Smith

    WGA Forum Manager

    Friday, January 4, 2008 6:13 PM
  • Darin,

     

    Thanks for the assistance.  I've uninstalled the following:

     

    Glary Utilities - Installed but rarely used humm???

     

    HP Bluetooth Adaptor - Installed but rarely used

     

    Windows Live - A whole suite of recently installed Windows Live programs and tools

     

    LinkedIn Outlook, IE toolbars

     

    Rebooted the machine and the issue seems to have gone away, or at least not reappeared in the past 3-4 hours.

     

    Not sure which program actually fixed the issue, but my money was on the Bluetooth or Glary Utilities.

     

    Thanks again,

     

    Ron

    Friday, January 4, 2008 9:48 PM

All replies

  •  

    Hello Ron,

     

      Your Vista is in, what is known as 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, your issue is an In Memory Mod-Auth. This means there is a program install and Running that is trying to access parts of the OS that Vista does not allow which, by definition, means it 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:2008       01      03         1935                02089

    In your case, there is also a 'K' type TTS listed (K:20080104094514981) A 'K' type tamper is also know as a Kernel Mod tamper and it is a minor issue I beleive this tamper can be directly attributed to the Mod-Auth tamper and once that is fixed, the kernel mod tamper should disappear.


    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 01/03

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 01/03/2008"

    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 01/02/2008, 01/01/2008 and 12/31/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 01/03/2008, 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, in addition to the list of incompatible programs found un the URL above, 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 updateing to the most recent version.

     

    Thank you,

    Darin Smith

    WGA Forum Manager

    Friday, January 4, 2008 6:13 PM
  • Darin,

     

    No programs i9nstalled that are listed in the http://support.microsoft.com/kb/931699/ article.

     

    Went to the Reliability monitor and here's what was installed since 12/15/7:

     

    QuickTime v7.3.1.70 on 12/30/7

     

    Office SP1 on 12/27/7

    DEfinition Update for Windows Defender on 12/28 and 12/21

     

    HP Bluetooth USB Adapter on 12/16/7

     

    Not a clue as to which program could be causing this.  I'll uninstall the Quicktime and HP USB programs to see if they are at fault. 

     

    I'm assuming the Office SP1 service pack would NOT cause this.  Correct? 

     

    Any other thoughts?  Might be nice if this error would throw out the offending culprits name in the dump/message...

     

    Thanks,

     

    Ron

    Friday, January 4, 2008 6:31 PM
  • Ron,

     

    "Might be nice if this error would throw out the offending culprits name in the dump/message..."

    I completely agree, not only would it make my job easier, it would help customers resolve their issue faster.  My Dev team has tried to explain to me why it's not possible to do this, but it far more technical then I could understand.  I will still keep pushing for it untill they figure out how to do it.

     

     

      I do not believe QuickTime is to blame as we would have alot of people with this issue, but in reality, Mod-Auths are a relatively rare occurance. But just in case, make sure you have the most current version of QuickTime that is made for Vista.

     

      Updates (such as Definition Update and SP1) are very unlikely to be the cause of an In Memory Mod-Auth tamper because In Memory Mod-Auth tampers can only occure when the offending program is Running. And since Updates usually only run once, if they had been the cause, then your mod-auth tamper would have only happened once and then gone away. But for On Disk Mod-Auths, update, viruses/malware, random file corruption and manual manipulation of the system files, would be the most likely causes. 

     

      My money is on either the HP Bluetooth USB Adapter or another program that was install in the past (more the 3 days ago) but that you started using just recently.

     

      Please uninstall the HP Bluetooth USB Adapter first, reboot, and see it that resolves the problem. If not, take a look and see what programs are running when the Mod-Auth tamper next occures.

     

      The best workflow for uninstalling programs (to fix the in memory mod-auth tamper) is to uninstall only one program at a time, reboot, then wait a bit till the Mod-Auth returns and then try uninstalling the next program. This way you can clearly identify the offending program and know what not to reinstall it in the future (and also tell me which program it was, so I can share the information with other users)

     

    Darin
    Friday, January 4, 2008 9:21 PM
  • Darin,

     

    Thanks for the assistance.  I've uninstalled the following:

     

    Glary Utilities - Installed but rarely used humm???

     

    HP Bluetooth Adaptor - Installed but rarely used

     

    Windows Live - A whole suite of recently installed Windows Live programs and tools

     

    LinkedIn Outlook, IE toolbars

     

    Rebooted the machine and the issue seems to have gone away, or at least not reappeared in the past 3-4 hours.

     

    Not sure which program actually fixed the issue, but my money was on the Bluetooth or Glary Utilities.

     

    Thanks again,

     

    Ron

    Friday, January 4, 2008 9:48 PM
  • Hi Ron,

     

       I had hoped that you would uninstall the programs, one at a time, so you could learn what not to re-install in the future and I could know what might be the cause of a future customer's issue.

     

      But your issue appears to be resolved and that's the importent thing

     

    I'm glad I could be of help!

     

    May your computing be trouble free,

    Darin

    Friday, January 4, 2008 11:13 PM
  • 0xc004d401 caused by Glary Utilities not compatible with Windows Vista Home Premium, system 32, in my case
    Monday, December 28, 2009 9:08 AM
  • 0xc004d401 caused by Glary Utilities not compatible with Windows Vista Home Premium, system 32, in my case
    Monday, December 28, 2009 9:08 AM
  • Darin,

     

    Thanks for the assistance.  I've uninstalled the following:

     

    Glary Utilities - Installed but rarely used humm???

     

    HP Bluetooth Adaptor - Installed but rarely used

     

    Windows Live - A whole suite of recently installed Windows Live programs and tools

     

    LinkedIn Outlook, IE toolbars

     

    Rebooted the machine and the issue seems to have gone away, or at least not reappeared in the past 3-4 hours.

     

    Not sure which program actually fixed the issue, but my money was on the Bluetooth or Glary Utilities.

     

    Thanks again,

     

    Ron

    0xc004d401 caused by Glary Utilities not compatible with Windows Vista Home Premium, system 32, in my case
    Monday, December 28, 2009 9:08 AM