locked
error - an unauthorized change was made to windows RRS feed

  • Question

  • Vista home edition come with DELL laptop.

    This problem appeared two days ago.

     

    The following info is a copy of the result from MGA Diagnostic Tool.

     

    THX

     

    Diagnostic Report (1.7.0069.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0xc004d401
    Cached Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-VXHW3-FXBVF-DH9KF
    Windows Product Key Hash: DlJ9vROJ1jvEOADL5LcnfCNJ1Oo=
    Windows Product ID: 89578-OEM-7318135-22936
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.0.6000.2.00010300.0.0.003
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {904CA6E1-692C-4E67-BA09-0BFC20EB4D7C}(1)
    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.071023-1545
    TTS Error: K:20080220141006371-M:20080220120340388-
    Validation Diagnostic:
    Resolution Status: N/A

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

    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: 114 Blocked VLK 2
    OGA Version: Registered, 1.6.28.0
    Signed By: Microsoft
    Office Diagnostics: 025D1FF3-282-80041013_025D1FF3-170-80041013_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>{904CA6E1-692C-4E67-BA09-0BFC20EB4D7C}</UGUID><Version>1.7.0069.0</Version><OS>6.0.6000.2.00010300.0.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-DH9KF</PKey><PID>89578-OEM-7318135-22936</PID><PIDType>3</PIDType><SID>S-1-5-21-776561741-842925246-839522115</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>MM061                           </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A12</Version><SMBIOSVersion major="2" minor="4"/><Date>20061218000000.000000+000</Date></BIOS><HWID>F98F3607018400FA</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><OEMID>DELL  </OEMID><OEMTableID>M07    </OEMTableID></OEM><BRT/></MachineData><Software><Office><Result>114</Result><Products><Product GUID="{90110409-6000-11D3-8CFE-0150048383C9}"><LegitResult>114</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>59D1605114E3500</Val><Hash>vfZmaSmFPIYrLWTcZSZErUQg+Fo=</Hash><Pid>73931-640-0000106-57881</Pid><PidType>14</PidType></Product><Product GUID="{90510409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Visio Professional 2003</Name><Ver>11</Ver><Val>5EA9C3672EB0500</Val><Hash>GZD+9sfb5ecL3RxyV4F75a86u2M=</Hash><Pid>72085-640-0000106-55894</Pid><PidType>14</PidType></Product></Products></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAElQAAAAAAAAYWECADAgAAB6e13QTnLIAW4aG1/FHasdtBRBPRnxqCIKivTO0Uv3r2veOEPuM08dDfcLAW0UHOSoUaAVrsVYhHqA49FE4GFdxw/X6PalIwx/ZBVpBA9g3kxnHq9T8Cm8M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agiCor0ztFL969r3jhD7jNPHQ33CwFtFBzkqFGgFa7FWIR6gOPRROBhXccP1+j2pSMMf2QVaQQPYN5MZx6vU/ApvDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMbhobX8Udqx20FEE9GfGoIgqK9M7RS/eva944Q+4zTx0N9wsBbRQc5KhRoBWuxViEeoDj0UTgYV3HD9fo9qUjDH9kFWkED2DeTGcer1PwKbwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDG4aG1/FHasdtBRBPRnxqCIKivTO0Uv3r2veOEPuM08dDfcLAW0UHOSoUaAVrsVYhHqA49FE4GFdxw/X6PalIwx/ZBVpBA9g3kxnHq9T8Cm8M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agiCor0ztFL969r3jhD7jNPHQ33CwFtFBzkqFGgFa7FWIR6gOPRROBhXccP1+j2pSMMf2QVaQQPYN5MZx6vU/ApvDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMbhobX8Udqx20FEE9GfGoIgqK9M7RS/eva944Q+4zTx0N9wsBbRQc5KhRoBWuxViEeoDj0UTgYV3HD9fo9qUjDH9kFWkED2DeTGcer1PwKbwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDG4aG1/FHasdtBRBPRnxqCIKivTO0Uv3r2veOEPuM08dDfcLAW0UHOSoUaAVrsVYhHqA49FE4GFdxw/X6PalIwx/ZBVpBA9g3kxnHq9T8Cm8M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYQ7P+IVnaO15JfQ/hyqZ4MaHlMtFokrgBwGpaKI0sADngVz/GPJM7ALbfKYyL2jxRdB/TofoSRMO1ykgEoUW3MULMITTRtrA7Kbffya6F4NZo5I814XKveJuPHHiahjj7tVLwe28YiH1BLYCERqYZDkmvhBlGHDl+f1L5AB51ccqVKU2BSf+UPRIXRoSSmEybGyYrHLwGFoM8hWdM+/ctDipudwcPOu4RzRON1r2alCNEX9TKgNw+bFnxMO1njX8zkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGEOz/iFZ2jteSX0P4cqmeB1qCBTNcPZMhHhQQw4d6sqGziV2712nRTHyg8EJAuX0UXQf06H6EkTDtcpIBKFFtyOmXN6NFpJN4UcJH9AtdUvWaOSPNeFyr3ibjxx4moY4+7VS8HtvGIh9QS2AhEamGQ5Jr4QZRhw5fn9S+QAedXHKlSlNgUn/lD0SF0aEkphMmxsmKxy8BhaDPIVnTPv3LQ4qbncHDzruEc0Tjda9mpQjRF/UyoDcPmxZ8TDtZ41/M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDA==

     

    Wednesday, February 20, 2008 9:27 PM

Answers

  •  

    Hello Yi Lu,

     

      Vista is in, what is called 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 and so on), by manual file modification (by a user of the system) or thru random file corruption.  

     

    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 are No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, Your issue is am In Memory Mod-Auth.  Basically a program that wasn't writen for Vista, is trying to access areas of the OS that Vista does not allow. 

     

    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        02      20          1203                 40388

     

    Note, I also see a "K" type Tamper Time Stamp. The K stands for Kermel Mode tamper. This is a minor tamper and is most likey directly related to the Mod-Auth tamper. Once you remove the program that is causing the Mod-Auth tamper, I believe that the Kernel mode tamper will stop as well.


    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 02/20

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 02/20/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 02/19/2008, 02/18/2008 and 02/17/2008

      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 (say) on 09/01/2007, but you didn't run (and, hence, prompted the tamper state)  till 02/20/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, 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 updating to the most recent version.

     

    Thank you,

    Darin Smith

    WGA Forum Manager

     

     

    Wednesday, February 20, 2008 11:36 PM
  • Darin,

     

    Thank you so much.

    The error has to be fixed according to your steps and WGA is passed also. The reason is system file corruption I think (fixed by chkdsk).

     

    Thanks again.

     

    Yi

     

    Thursday, February 21, 2008 2:56 PM

All replies

  •  

    Hello Yi Lu,

     

      Vista is in, what is called 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 and so on), by manual file modification (by a user of the system) or thru random file corruption.  

     

    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 are No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, Your issue is am In Memory Mod-Auth.  Basically a program that wasn't writen for Vista, is trying to access areas of the OS that Vista does not allow. 

     

    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        02      20          1203                 40388

     

    Note, I also see a "K" type Tamper Time Stamp. The K stands for Kermel Mode tamper. This is a minor tamper and is most likey directly related to the Mod-Auth tamper. Once you remove the program that is causing the Mod-Auth tamper, I believe that the Kernel mode tamper will stop as well.


    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 02/20

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 02/20/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 02/19/2008, 02/18/2008 and 02/17/2008

      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 (say) on 09/01/2007, but you didn't run (and, hence, prompted the tamper state)  till 02/20/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, 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 updating to the most recent version.

     

    Thank you,

    Darin Smith

    WGA Forum Manager

     

     

    Wednesday, February 20, 2008 11:36 PM
  • Darin,

     

    Thank you so much.

    The error has to be fixed according to your steps and WGA is passed also. The reason is system file corruption I think (fixed by chkdsk).

     

    Thanks again.

     

    Yi

     

    Thursday, February 21, 2008 2:56 PM