none
need help RRS feed

  • Question

  • i just got a message that says that an unauthorized change was made to windows and that i will no longer receive notifications, including those about my license and activation. It gives me a link to find out how to fix the problem but i cannot acces. I got a laptop sony vaio with windows vista

    what can i do???

    The details shown are:

    Error: 0xC004D401

    Description: The security processor reported a system file mismatch error.

    thaks

    Wednesday, March 9, 2011 5:04 PM

Answers

  • Hi adiceleste,

      Well, the issue your Windows is experiencing is known as as In Memory Mod-Auth Tamper (also known as an AppCompat Tamper) I have provided a further description (and advice on pinpointing the cause) of what an In Memory Mod-Auth is, below, But, in a nutshell, an In Memory Mod-Auth is caused by an incomparable program (either a legitimate program that you installed or a malware program you didn't intend to install) that is doing something that Vista doesn't allow (specifically, hooking, shimming or otherwise modifying windows files, while they are running in system memory, in a way that may have been allowable in older versions of Windows, but are no longer allowed in Vista and Windows 7).

      So, given that the issue is caused by an incomparable program, your suggestion that the recently installed Fox Tab PDF Converterter may be the cause could very well be correct.  I am not familiar with that program, but if it wasn't written specifically for Vista or if you have an older version of the program that may not be compatible with Vista, then it would be highly likely that it could be the cause.

      I think your first step would be to completely uninstall that program and see if the issue goes away. 

       -If the issue does go away, then you know that program was the cause. In this case, if you still need a PDF Converter, look for a different one that is known to be compatible with Vista or maybe there is a newer version of that same software that is compatible.

      -If the issue does not go away, then you know something else is the cause and you should read below for more information on how to figure out what is the cause.

     

    Vista is in, what we call a 'Mod-Auth' Tamper state.  There are 2 types of Mod-Auth tampers.


    1)    On Disk: 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 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 occur.

    2)    In Memory: 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 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, we know that your issue is an In Memory Mod-Auth and therefore caused by an incompatible program. 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.


    NOTE: We have seen an increase in this type of issue and we believe it is unlikely that software writers are still making programs that are incompatible with Vista. Instead, we believe that a majority of the issues are being caused by Malware that are doing the same things (on purpose) as incompatible programs do (by accident).
     
      In addition to why a Mod-Auth occurs, it's also important to understand how Vista detects a Mod-Auth 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 go Non-Genuine and it could take some time for the Mod-Auth to be detected. The important point to note is that the moment Vista does detect the Mod-Auth, you know that the program that is causing the Mod-Auth, 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. (NOTE: this is not a full list, it is just the programs we have confirmed are not comparable.  There are too many programs out in the world for use to test every one)
     
      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:2011       03        09         1019                    14139-
     
    Note: I also see a "K" type Tamper Time Stamp. The “K“ stands for Kernel Mode tamper. Once you remove the program that is causing the In Memory Mod-Auth tamper, the Kernel Mode tamper may be resolved as well. But a Kernel Mode Tamper can sometime indicate a Malware infection. To be on the safe side, we strongly suggest scanning your system with the Anti-Virus program of your choice as well as with the OneCare Safety Scanner for Vista (http://onecare.live.com/site/en-us/center/whatsnew.htm

    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 03/09
    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 03/09/2011 "
    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 03/08/2011, 03/07/2011 and 03/06/2011  (or around the date the issue first occurred)


      This could tell you 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 at some time in the past, but didn’t run it till now, 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.

    Note: Since everyone has different programs installed on their computer, it is extremely hard for support to figure out what program is causing the problem, but if you still need assistance in identifying the Incompatible Program, please create a no cost support request at http://go.microsoft.com/fwlink/?linkid=52029


    Also Note: it has been found that Malware, such as Viruses and Trojans, can also be incompatible with Vista and can cause an In Memory Mod-Auth. A number of users (that were experiencing your same issue) have confirmed that a Malware infection was the cause. If you follow the above steps and cannot find a program that is causing the Mod-Auth, you may want to investigate if a Virus, Worm or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ (http://onecare.live.com/site/en-us/center/whatsnew.htm ) before contacting PC Safety.


    PC Safety:
    http://www.microsoft.com/protect/support/default.mspx
    http://onecare.live.com/site/en-us/center/whatsnew.htm

    Thank you,


    Darin MS
    Thursday, March 10, 2011 9:33 PM

All replies

  •   In order to receive the best support, we request all users initially download and run the Genuine Diagnostics tool (MGADiag.exe) at this link http://go.microsoft.com/fwlink/?linkid=52012 . Click "Continue", click the "Copy" button then “Paste” the report into a reply message in this thread.

     

    If you do not have access to the Start Button:

    1)    Login to Vista and click the option that brings up Internet Explorer.

    2)    Type: http://go.microsoft.com/fwlink/?linkid=52012 into the browser address bar.

    3)    A window will come up asking if you want to “Run” or “Save”, Select “Run”

    4)    When the program runs, click the “Continue” button, then click the “Copy” button.

    5)    Return to this thread http://social.microsoft.com/Forums/en-US/genuinevista/thread/81d7a392-d9b9-4353-9d0d-2754772d690e .

    6)    In a reply post, paste the Diagnostic Report.

     

    Thank you,


    Darin MS
    Wednesday, March 9, 2011 11:38 PM
  • Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-4GV68-6D8JB-G6MF9
    Windows Product Key Hash: Ua+OBZ1y48sKA/bWkfKXiuCrOjY=
    Windows Product ID: 89583-OEM-7332157-00203
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6001.2.00010300.1.0.003
    ID: {FA9A8246-3C8F-4C01-A74F-CD278CE4BE5D}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000009
    Build lab: 6001.vistasp1_gdr.101014-0432
    TTS Error: K:20110309111824353-M:20110309101914139-
    Validation Diagnostic:
    Resolution Status: N/A

    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002

    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    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 Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 100 Genuine
    Microsoft Office Home and Student 2007 - 100 Genuine
    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_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\Mozilla Firefox\firefox.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>{FA9A8246-3C8F-4C01-A74F-CD278CE4BE5D}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6001.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-G6MF9</PKey><PID>89583-OEM-7332157-00203</PID><PIDType>2</PIDType><SID>S-1-5-21-1237387997-2665524292-3644293864</SID><SYSTEM><Manufacturer>Sony Corporation</Manufacturer><Model>VGN-FW265D</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>R1090Y0</Version><SMBIOSVersion major="2" minor="4"/><Date>20080725000000.000000+000</Date></BIOS><HWID>61303507018400FA</HWID><UserLCID>1009</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time (Mexico)(GMT-06:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>Sony</OEMID><OEMTableID>VAIO</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><Val>1D6B908D5151F70</Val><Hash>YuxmLjUJ6Ngo7QpkYYdTzAcVXtI=</Hash><Pid>81602-952-0331322-68774</Pid><PidType>1</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>  

    Spsys.log Content: U1BMRwEAAAAAAQAACAAAABo09wAAAAAAYWECAAAAAAAAyBm7dd7LARhy9171jCizkdIEkQaJZ66ENxHy+3DqYKSojBl1OvByOpwp5mpvnZdRSXtMmNowOid7IPmIgITKmLNv1wD2WLaBDDRIxD6uqefsZFhG9pEjqaOcEd48HYsOntqnEBPIUIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsO7TtXiHJbmqvzuSde4tUlmcGxBpop0WwiuBXa5HXuzs1OU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

    Licensing Data-->
    C:\Windows\system32\slmgr.vbs(1634, 5) (null): 0xC004D401

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: OAAAAAEAAwABAAIAAQABAAAABAABAAEA6GHyuzBPgKykouJdmPI8qOpj8vQaPyugbgXU5KxWKoU=

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x20000
    OEMID and OEMTableID Consistent: yes
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            Sony        VAIO
      FACP            Sony        VAIO
      HPET            Sony        VAIO
      MCFG            Sony        VAIO
      SLIC            Sony        VAIO
      SSDT            Sony        VAIO


    Hey Darin, i did what you asked me to do, so what's next??

    thanks a lot for helping me out with this, i really appreciate it!!

    Thursday, March 10, 2011 6:23 AM
  • hey Darin i also wanted you to know that before this problem came up i installed a new program, the Fox Tab PDF Converterter

    and i was thinking that this may have been the invalid change, what do you think??

    Thursday, March 10, 2011 3:05 PM
  • Hi adiceleste,

      Well, the issue your Windows is experiencing is known as as In Memory Mod-Auth Tamper (also known as an AppCompat Tamper) I have provided a further description (and advice on pinpointing the cause) of what an In Memory Mod-Auth is, below, But, in a nutshell, an In Memory Mod-Auth is caused by an incomparable program (either a legitimate program that you installed or a malware program you didn't intend to install) that is doing something that Vista doesn't allow (specifically, hooking, shimming or otherwise modifying windows files, while they are running in system memory, in a way that may have been allowable in older versions of Windows, but are no longer allowed in Vista and Windows 7).

      So, given that the issue is caused by an incomparable program, your suggestion that the recently installed Fox Tab PDF Converterter may be the cause could very well be correct.  I am not familiar with that program, but if it wasn't written specifically for Vista or if you have an older version of the program that may not be compatible with Vista, then it would be highly likely that it could be the cause.

      I think your first step would be to completely uninstall that program and see if the issue goes away. 

       -If the issue does go away, then you know that program was the cause. In this case, if you still need a PDF Converter, look for a different one that is known to be compatible with Vista or maybe there is a newer version of that same software that is compatible.

      -If the issue does not go away, then you know something else is the cause and you should read below for more information on how to figure out what is the cause.

     

    Vista is in, what we call a 'Mod-Auth' Tamper state.  There are 2 types of Mod-Auth tampers.


    1)    On Disk: 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 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 occur.

    2)    In Memory: 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 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, we know that your issue is an In Memory Mod-Auth and therefore caused by an incompatible program. 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.


    NOTE: We have seen an increase in this type of issue and we believe it is unlikely that software writers are still making programs that are incompatible with Vista. Instead, we believe that a majority of the issues are being caused by Malware that are doing the same things (on purpose) as incompatible programs do (by accident).
     
      In addition to why a Mod-Auth occurs, it's also important to understand how Vista detects a Mod-Auth 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 go Non-Genuine and it could take some time for the Mod-Auth to be detected. The important point to note is that the moment Vista does detect the Mod-Auth, you know that the program that is causing the Mod-Auth, 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. (NOTE: this is not a full list, it is just the programs we have confirmed are not comparable.  There are too many programs out in the world for use to test every one)
     
      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:2011       03        09         1019                    14139-
     
    Note: I also see a "K" type Tamper Time Stamp. The “K“ stands for Kernel Mode tamper. Once you remove the program that is causing the In Memory Mod-Auth tamper, the Kernel Mode tamper may be resolved as well. But a Kernel Mode Tamper can sometime indicate a Malware infection. To be on the safe side, we strongly suggest scanning your system with the Anti-Virus program of your choice as well as with the OneCare Safety Scanner for Vista (http://onecare.live.com/site/en-us/center/whatsnew.htm

    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 03/09
    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 03/09/2011 "
    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 03/08/2011, 03/07/2011 and 03/06/2011  (or around the date the issue first occurred)


      This could tell you 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 at some time in the past, but didn’t run it till now, 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.

    Note: Since everyone has different programs installed on their computer, it is extremely hard for support to figure out what program is causing the problem, but if you still need assistance in identifying the Incompatible Program, please create a no cost support request at http://go.microsoft.com/fwlink/?linkid=52029


    Also Note: it has been found that Malware, such as Viruses and Trojans, can also be incompatible with Vista and can cause an In Memory Mod-Auth. A number of users (that were experiencing your same issue) have confirmed that a Malware infection was the cause. If you follow the above steps and cannot find a program that is causing the Mod-Auth, you may want to investigate if a Virus, Worm or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ (http://onecare.live.com/site/en-us/center/whatsnew.htm ) before contacting PC Safety.


    PC Safety:
    http://www.microsoft.com/protect/support/default.mspx
    http://onecare.live.com/site/en-us/center/whatsnew.htm

    Thank you,


    Darin MS
    Thursday, March 10, 2011 9:33 PM
  • hello Darin, thanks a lot for your help, i have read the message you sent and  i will follow all the steps, the thing is, im almos sure the program that is causing the problem is the one i mentioned to you the Fox Tab PDF Converter, because i was away for a long time and no one used my computer and that is the only program that has been installed lately. So tried to uninstall it and i get this box with a message that says im not allowed to uninstall the program, and that i should contact support, but if i go to the PDF Converter web page the buttons dont take me anywere so there's no one to actually talk about this issue!!

    what can i do to uninstalll the program???

    Thursday, March 10, 2011 10:51 PM
  • hello again!

    i have restored my computer and the program is not there anymore, do i need to validate my windows??

    because when i try to get to this web page

    www.microsoft.com/genuine/validate

    it sends me right away to this other one

    http://search.microsoft.com/?mkt=en-GB

    Friday, March 11, 2011 1:37 AM
  • I've run into the same error upon reinstalling Vista on VAIO VGN650N. I'd simply used recovery tools and rolled back to a previous restoring point.

    After reading these posts, I'd suspect that Paragon backup is the likely suspect for this issue, since it tries and lock files on OS in order to perform a backup.

    I did the backup, removed the program and the system keeps updating in a normal way since then.

    Oddly (or not), Microsoft does not offer ANY help on this issue, simply redirects you to a page where they sell Windows 7.

    You look at your laptop and that legitimate (and useless) 3D logo stamp of  authenticity stuck on the bottom and say -what?

    Thursday, April 28, 2011 11:27 AM