An unauthorized change has been made to windows

All replies

• 

  

  0

  Sign in to vote

  Hello yesss,

  Vista is in, what we call 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 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)    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 a Mod-Auth  State and it could take some time for the Mod-Auth to be detected. The important point to note is that the moment Vista detects 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.
   
    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:2010    07    28      0117             41530-
  

   

  
  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 07/28

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

  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 07/27, 07/26 and 07/25 (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

  • Marked as answer by Darin Smith MS Wednesday, July 28, 2010 9:06 PM

  Wednesday, July 28, 2010 9:05 PM
• 

  

  0

  Sign in to vote

  I looked at the reliability monitor and the only thing that happened on 7/28 is an application failure for explorer.exe failure type stopped responding...I remember explorer crashed on me that day but it started working a bit after I end processed it, and then the unauthorized change thing started popping up...

  Thursday, July 29, 2010 5:17 PM
• 

  

  0

  Sign in to vote

  "yesss" wrote in message news:4dfd7599-932f-4939-bc19-c5d2c8debe4d...

  I looked at the reliability monitor and the only thing that happened on 7/28 is an application failure for explorer.exe failure type stopped responding...I remember explorer crashed on me that day but it started working a bit after I end processed it, and then the unauthorized change thing started popping up...

  
  

  Look back in the three days prior to the 28th - what else was installed or failed??

   

  
  --
  
  

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

  Thursday, July 29, 2010 6:19 PM

  Moderator
• 

  

  0

  Sign in to vote

  On the 27th I had two automatic updates I guess cause I didn't install anything. Skype toolbar had a configuration change and windows defender had a definition update(system update install). I managed to uninstall skype toolbar and the problem was fixed...for about a day. I have no new software installs. I didn't see windows defender in my programs/apps so I couldn't do anything about it.

  
  Actually this new scan says it's on the 29th, and for the 29th I have no installs, but I uninstalled skype and ask toolbars. I also have a svchost.exe_Dnscache stopped working on that day...
  
  
  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: *****-*****-4JJQP-TP64Y-RPFFV
  Windows Product Key Hash: W7I5PeTN2iJuvTTU9QmIXc6iQqY=
  Windows Product ID: 89578-OEM-7332157-00043
  Windows Product ID Type: 2
  Windows License Type: OEM SLP
  Windows OS version: 6.0.6001.2.00010300.1.0.003
  ID: {11378396-EFE1-44C5-912A-461B264961B8}(3)
  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: 0x00000000
  Build lab: 6001.vistasp1_gdr.100218-0019
  TTS Error: K:20100801130825447-M:20100729233928011-
  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 Enterprise 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
  
  Browser Data-->
  Proxy settings: N/A
  User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
  Default Browser: C:\Program Files\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>{11378396-EFE1-44C5-912A-461B264961B8}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6001.2.00010300.1.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-RPFFV</PKey><PID>89578-OEM-7332157-00043</PID><PIDType>2</PIDType><SID>S-1-5-21-3983338341-3541620162-2032902541</SID><SYSTEM><Manufacturer>ASUSTeK Computer Inc.        </Manufacturer><Model>N51Vf                </Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>301    </Version><SMBIOSVersion major="2" minor="5"/><Date>20090310000000.000000+000</Date></BIOS><HWID>CA323507018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>_ASUS_</OEMID><OEMTableID>Notebook</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>5D65FE14D58F586</Val><Hash>BAoDbPc0n8rFHidSDI0n88MWyd0=</Hash><Pid>89388-707-0270147-65625</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/><App Id="BA" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 
  
  Spsys.log Content: U1BMRwEAAAAAAQAABAAAABTvfwcAAAAAYWECAAQwXpJATROGAS7LAW4aG1/FHasdtBRBPRnxqCKdUSUlxqvBbu0MmyxV3qJC19UAU9sbzByWL4dMMpm6y1PKFrEeGZBwGER8sg9uEgr2WsBZYbIZJJLJezdT4XiJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agiavNRUhxmbjdJlea89eT9mYLxrN0L3JaiAnx9asXpkpTZlm8PeKjLvyc9qWVrNWaw9lrAWWGyGSSSyXs3U+F4iTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMbhobX8Udqx20FEE9GfGoIlwuBdVFziOeoqf+bs9mMQh8dmfV2fwHNn1xxOcryvbQU8oWsR4ZkHAYRHyyD24SCvZawFlhshkkksl7N1PheIkzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDG4aG1/FHasdtBRBPRnxqCJ1sq8twF3EYJHea9QRS9f7AhnjfFadiR31Z/7mnNxHG3SVLzILP/P30L2m4p+wuQb2WsBZYbIZJJLJezdT4XiJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=
  
  Licensing Data-->
  C:\Windows\system32\slmgr.vbs(1634, 5) (null): 0xC004D401
  
  Windows Activation Technologies-->
  N/A
  
  HWID Data-->
  HWID Hash Current: PgAAAAIABAABAAEAAgACAAAABAABAAEAeqgknLKS1yxyA7LkVGVQaejr3JCN7/L01psyWTuuAMiQHaxWRso=
  
  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            031009        APIC1541
    FACP            031009        FACP1541
    DBGP            031009        DBGP1541
    HPET            031009        OEMHPET
    BOOT            031009        BOOT1541
    MCFG            031009        OEMMCFG
    SLIC            _ASUS_        Notebook
    ECDT            031009        OEMECDT
    OEMB            031009        OEMB1541
    ATKG            022008        OEMATKG
    SSDT            PmRef        CpuPm
  
  
  

  Sunday, August 1, 2010 9:30 PM
• 

  

  0

  Sign in to vote

  "yesss" wrote in message news:823a8b7e-486e-4e63-abff-35e80146b585...

  On the 27th I had two automatic updates I guess cause I didn't install anything. Skype toolbar had a configuration change and windows defender had a definition update(system update install). I managed to uninstall skype toolbar and the problem was fixed...for about a day. I have no new software installs. I didn't see windows defender in my programs/apps so I couldn't do anything about it.

  
  Actually this new scan says it's on the 29th, and for the 29th I have no installs, but I uninstalled skype and ask toolbars. I also have a svchost.exe_Dnscache stopped working on that day...
  
  
  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: *****-*****-4JJQP-TP64Y-RPFFV
  Windows Product Key Hash: W7I5PeTN2iJuvTTU9QmIXc6iQqY=
  Windows Product ID: 89578-OEM-7332157-00043
  Windows Product ID Type: 2
  Windows License Type: OEM SLP
  Windows OS version: 6.0.6001.2.00010300.1.0.003
  

  
  

  I see from your new MGADiag that you have also developed a Kernel-type Mod-Auth Tamper!

  Here's Darin's usual 'spiel' on such situations...

  <quote>

  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)

  </quote>

  I would also suggest that you download, install, update and run a full system scan with Malwarebytes Anti-Malware (www.malwarebytes.org) and see whether it finds anything that the normal AV scans don't.

  If it finds anything significant, then you should also boot to Safe Mode, and run Quick scans in all user profiles on the machine.

  
  --
  
  

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

  Monday, August 2, 2010 6:49 AM

  Moderator