none
Another unauthorized change issue RRS feed

  • Question

  • I didn't have any problems until I tried to install Vista SP1, it didn't work. Please advise

     

    Thank you,

    Jimmie

     

    Diagnostic Report (1.7.0095.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0xc004d401
    Cached Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-VRCTY-3V3RH-WRMG7
    Windows Product Key Hash: l2HYuM058SkcIU57PqWaCOL7rEU=
    Windows Product ID: 89576-OEM-7332141-00054
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6000.2.00010100.0.0.006
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {9CCB87C1-8BB7-4908-94EA-17EDAC4C3FC9}(1)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.7.69.2
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Business
    Architecture: 0x00000000
    Build lab: 6000.vista_gdr.071023-1545
    TTS Error: M:20080430145140335-
    Validation Diagnostic:
    Resolution Status: N/A

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

    WGA 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
    WGATray.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 100 Genuine
    Microsoft Office Project Standard 2007 - 100 Genuine
    2007 Microsoft Office system - 100 Genuine
    OGA Version: Registered, 1.6.28.0
    Signed By: Microsoft
    Office Diagnostics: 77F760FE-153-80070002_7E90FEE8-175-80070002_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>{9CCB87C1-8BB7-4908-94EA-17EDAC4C3FC9}</UGUID><Version>1.7.0095.0</Version><OS>6.0.6000.2.00010100.0.0.006</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-WRMG7</PKey><PID>89576-OEM-7332141-00054</PID><PIDType>2</PIDType><SID>S-1-5-21-1532128225-819899279-2317274697</SID><SYSTEM><Manufacturer>Dell Inc.                </Manufacturer><Model>OptiPlex 320                 </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.                </Manufacturer><Version>1.1.11 </Version><SMBIOSVersion major="2" minor="3"/><Date>20071126000000.000000+000</Date></BIOS><HWID>F8333507018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL  </OEMID><OEMTableID>B8K    </OEMTableID></OEM><BRT/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-003A-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Project Standard 2007</Name><Ver>12</Ver><Val>9772A28614E1586</Val><Hash>Vo/HmSGlEahqacWwdPuwcAjX/H0=</Hash><Pid>89402-707-3584546-63566</Pid><PidType>14</PidType></Product><Product GUID="{91120000-0031-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>2007 Microsoft Office system</Name><Ver>12</Ver><Val>23C54B84A4245AE</Val><Hash>BfzNPPKdynHYLjwN4Pw7YQqOxso=</Hash><Pid>89451-OEM-6672777-49596</Pid><PidType>4</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="3A" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAFd4GwAAAAAAYWECADAgAAAiUI6b+6rIARhDs/4hWdo7Xkl9D+HKpniF+//FwVmKz4+RTHAQ3IBUch5fXMBoUBVp8nlDKOSzH1F0H9Oh+hJEw7XKSAShRbduR/qiV6zyzlETusfkeGkA1mjkjzXhcq94m48ceJqGOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxUFe/CarAhO73oJwYTKgykpsbJiscvAYWgzyFZ0z79y0OKm53Bw867hHNE43WvZqUI0Rf1MqA3D5sWfEw7WeNfzOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

     

    Wednesday, April 30, 2008 8:04 PM

Answers

  • Hello JimmieJ,

     

     

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

     

      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.

     

      I do not believe that SP1 is the cause of this In Memory Mod-Auth issue. The reason is:

     

    a) From your post,  the issue appears to have been going on for some time.

    b) In Memory Mod-Auth can Only be caused by a program Running in system memory.

    c) Updates (including SP1) generally only run once.

     

    So unless SP1 is continually running, it is extreamly unlikely that SP1 caused this issue.

     

     A more likely scenario would be that you may have recently installed and ran (or installed some time ago, but only recently ran, for the first time) an Incompatible Program, around  the same time (within around 3-4 days) as installing SP1.

     

    Below I have provided a number of steps to help you identify the incompatible 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 shows the Last time the tamper event occured.

     

    It breaks down like this:

     

        (year)  (month) (day) (time in 24format) (millisecond)
    M:2008      04        30          1451                        40335

     


    Now that you know the time of the last 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 04/30 

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 04/30/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 04/29/2008, 04/28/2008 and 04/27/2008

     

    If the above does not help, try to think back to the date the issue first occured and replace the above dates with the date the issue first occured.

     

      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/26/2008[C6] , 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

    Wednesday, April 30, 2008 11:13 PM
  •   My last suggestion that may possibly resolve the issue is to install Service Pack 1 for Vista. SP1 resolve some compatibility issue. I am unsure, however, if it would resolve the compatibility issue with whatever program that is causing your particular issue.

     

      Outside of that, the only other suggestion I can provide is to go to http://support.microsoft.com for additional support options.

     

    Sorry I couldn't be more help,

    Darin Smith

    WGA Forum Manager

     

    Friday, May 9, 2008 8:22 PM
  • Hi JimmieJ,

     

      This is outside my area of knowledge, I suggest reposting your question (regarding the tcpmon.ini file) to one of the general Vista Newsgroups at http://go.microsoft.com/fwlink/?linkid=42486. There should be a user or MVP that has knowledge of this file and/or this issue. 

     

    Thank you,
    Darin Smith
    WGA Forum Manager

     

    Tuesday, May 20, 2008 10:43 PM

All replies

  • Hello JimmieJ,

     

     

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

     

      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.

     

      I do not believe that SP1 is the cause of this In Memory Mod-Auth issue. The reason is:

     

    a) From your post,  the issue appears to have been going on for some time.

    b) In Memory Mod-Auth can Only be caused by a program Running in system memory.

    c) Updates (including SP1) generally only run once.

     

    So unless SP1 is continually running, it is extreamly unlikely that SP1 caused this issue.

     

     A more likely scenario would be that you may have recently installed and ran (or installed some time ago, but only recently ran, for the first time) an Incompatible Program, around  the same time (within around 3-4 days) as installing SP1.

     

    Below I have provided a number of steps to help you identify the incompatible 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 shows the Last time the tamper event occured.

     

    It breaks down like this:

     

        (year)  (month) (day) (time in 24format) (millisecond)
    M:2008      04        30          1451                        40335

     


    Now that you know the time of the last 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 04/30 

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 04/30/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 04/29/2008, 04/28/2008 and 04/27/2008

     

    If the above does not help, try to think back to the date the issue first occured and replace the above dates with the date the issue first occured.

     

      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/26/2008[C6] , 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

    Wednesday, April 30, 2008 11:13 PM
  • Darin,

    I did What you suggested, I found 6 possible culprits. Silverlight, VMWare, Sonicwall, Logmein, MS Project, & Norton Ghost.  I removed Silverlight and Logmein with no improvements. I need the other 4 to do my job. Presuming one of the remaining programs is the trouble maker, How do I get updated and be able to keep programs I need?

     

    Thanks,

    Jimmiej

     

    Thursday, May 1, 2008 6:17 PM
  •   My suggestion would be to go to the website for each of the programs that you have installed (and that were running at the times the issue(s) occured) and confirm that you have the most up-to-date version of the software as well as confirm that the most up-to-date version is, in fact, compatible with Vista. You may also want to check to forums at the websites to see if anyone else has experienced similare issues using that software under Vista.

     

     Please see http://support.microsoft.com for additional Vista support options.

     

    Thank you,

    Darin

     

    Thursday, May 1, 2008 9:17 PM
  • I checked my other programs, went to the appropriate websites and downloaded and installed appropriate updates. That didn't help. I then tried to "roll back" my PC to a  recovery point before this issue happened. I chose a month old recovery point that I knew had worked. this was no help so I rolled back the roll back. I also unuinstalled those six programs that I had determined could possibly be causing the problem. still no help???

    Friday, May 9, 2008 2:40 PM
  •   My last suggestion that may possibly resolve the issue is to install Service Pack 1 for Vista. SP1 resolve some compatibility issue. I am unsure, however, if it would resolve the compatibility issue with whatever program that is causing your particular issue.

     

      Outside of that, the only other suggestion I can provide is to go to http://support.microsoft.com for additional support options.

     

    Sorry I couldn't be more help,

    Darin Smith

    WGA Forum Manager

     

    Friday, May 9, 2008 8:22 PM
  • Hi Darin,

    I have been trying to install SP1 for Vista and it failed 3 times. I tried downloading it each time in case the previous download had gotten corrupted. Is there anything I can check to tell me what to do to find out what I need to do to resolve the issue of SP1 not wanting to install?

     

    JimmieJ
    Tuesday, May 13, 2008 1:58 PM
  • Hi JimmieJ,

     

      The Vista Solution Center (http://support.microsoft.com/ph/11732#tab0) has information regarding a number of SP1 related issues as well as a link to the (Free) SP1 Phone, Email and Chat support.

     

     

    Darin

     

    Tuesday, May 13, 2008 8:41 PM
  • Thanks Darin,

    The proceedures you sent me to let me find what the problem is, however, I have searched all of Microsoft.com and can't find a solution. The problem is with tcpmon.ini

    This is the entry from SFC. any suggestions?

     

    2008-05-15 14:32:12, Info                  CSI    000000e4 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

     

     

    I appreciate your assistance,

     

    JimmieJ

    Friday, May 16, 2008 12:48 PM
  • Hi JimmieJ,

     

      This is outside my area of knowledge, I suggest reposting your question (regarding the tcpmon.ini file) to one of the general Vista Newsgroups at http://go.microsoft.com/fwlink/?linkid=42486. There should be a user or MVP that has knowledge of this file and/or this issue. 

     

    Thank you,
    Darin Smith
    WGA Forum Manager

     

    Tuesday, May 20, 2008 10:43 PM