locked
an unauthorized change was made to windows...ZoneAlarm 7.1.078 RRS feed

  • Question

  • Hi,

     My OEM Vista works normal about year and then I install ZoneAlarm Free Firewall 7.1.078.000 which I download from Download.com.
    After month of work I start to receive crush messages - DCOM svhost crush & Plug&Play crush or something like that (translit of my Russian Vista messages).

    And then comes next - "an unauthorized change was made to windows"
    Error code 0xC004D401

    Then I find this http://support.microsoft.com/kb/935796
    This document dated march 2008 and I download ZA 7.1.078 from Download.com at november 2008! Thanks them a lot.

    Uninstalling of ZA doesn't resolve the problem.

    I find that if I restart the licensing service then Vista becomes genuine but after the restart of the system nongenuine again.
    What is wrong whis my Vista WGA?
    • Changed type Stephen Holm Thursday, December 18, 2008 8:08 PM
    • Changed type Stephen Holm Thursday, December 18, 2008 8:08 PM
    Thursday, December 18, 2008 5:04 PM

Answers

  • Dr. Yuri,


    Windows 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, and was modified in some way. This can be caused by a malicious program (malware) 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 Windows 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 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 Windows Vista does not allow which by definition means it is incompatible with Windows Vista.

     

    In addition to why a Tamper occurs, it's also important to understand how Windows Vista detects the Tamper event. There is a Service that runs in Windows 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, Windows 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 Windows 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:

     

    The following Knowledge Base (KB) article may help you confirm that you do not have any of the programs known to cause this type of issue.

     

    KB931699 - Error message when you use Windows Vista: "An unauthorized change was made to your license"

     

    http://support.microsoft.com/kb/931699/

     
    Second, in your Microsoft Genuine Diagnostic Tool (MGADT) 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       12             19               1653                          07070-
     

    Note: I also see a "K" type Tamper Time Stamp. The “K“stands for Kernel Mode tamper. This is a minor tamper and is most likely 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.


    (Year)       (Month)      (Day)      (Time in 24format)      (Millisecond) 

    K:2008       12             18             1905                             28657-





    Now that you know the time of the tamper, you can now try to connect that time with a program.

     

    1) Login to Windows Vista and select the option which 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) Then click System Stability Chart above the date 12/19 

    6) Below the chart, in the System Stability Report section look at the report titled "Software (Un) Installs for 12/19/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 Windows Vista to a Tamper State. Because of this, please repeat steps 5) through 7) for the dates 12/18/2008, 12/17/2008, and 12/16/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 12/19/2008, this process may not be helpful.  The removal of any application you may have installed recently could go a long way to troubleshooting these issues as well since it may fall outside of the 3 day time frame described above.

    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 the following link below:

    http://go.microsoft.com/fwlink/?linkid=52029




    Thank you for visiting the Genuine Advantage forum


    Stephen Holm, MS
    WGA Forum Manager


    Stephen Holm
    • Marked as answer by Stephen Holm Friday, December 19, 2008 10:02 PM
    Friday, December 19, 2008 10:01 PM

All replies

  •  

    Self-investigation (aka blog)

    I alredy find some connection with all previously posted messages:

    License service(C:\Windows\system32\SLsvc.exe) depend from RPC (C:\Windows\system32

    \svchost.exe -k rpcss)
    RPC depend from DCOM and Plug-and-Play(C:\Windows\system32\svchost.exe -k DcomLaunch)

    I think that is the key to solvation because if I restart Slsvc.exe at the begining of system load then restricted windows mode(block of control panel) is out and works normal till new system reboot.

    So maybe someone of VISTA's GURU tell me what I should do next or I stay in self-support

    mode? :)

    Thursday, December 18, 2008 7:44 PM
  • Dr Yuri,


    Please run the Microsoft Genuine Advantage Diagnostic Test (MGADT) so that I may analyze the results.

    By clicking the link below, you will download the MGADT.  Then click the Run button. Then click the Run button again. Then click the Continue button to perform the diagnostic. The Windows tab should show, click the Copy button to paste your report to the clipboard.  Then paste the report into a New Post on this Forum by adding a post in it and pressing Ctrl V (to paste the text). Clicking the OK button will clear the Diagnostic window. Here is the download link:

     http://go.microsoft.com/fwlink/?linkid=52012

    Please tell us about the Certificate of Authenticity (COA) for your copy of Windows Vista.

    1. What edition/version of Windows XP is titled?

    ·         Home Basic

    ·         Home Premium 

    ·         Business

    ·         Ultimate

    2. Does it read "OEM Software" or "OEM Product" in black lettering?

    3. Or, does it have the computer manufacturer's name in black lettering?

    4. Please provide the customer scenario you are experiencing.

    5. DO NOT post the Product Key. 

    Not sure what to look for, see this page to reference your COA:

    http://www.microsoft.com/resources/howtotell/product.aspx?pID=b5c507e5-3522-40de-a2f4-97d82b39cc47&cID=ea710cad-37b0-4975-bcd6-abfee19961df&method=oem&displaylang=en

    NOTE: The data collected with the MGADT does NOT contain any information that can personally identify you. The information can be fully reviewed, by you, before being posted.




    Thank you for your participation here on the Genuine Advantage forum. We look forward to working with you.



    Stephen Holm, MS
    WGA Forum Manager


    Stephen Holm
    Thursday, December 18, 2008 8:10 PM
  • Dr. Yuri,


    Windows 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, and was modified in some way. This can be caused by a malicious program (malware) 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 Windows 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 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 Windows Vista does not allow which by definition means it is incompatible with Windows Vista.

     

    In addition to why a Tamper occurs, it's also important to understand how Windows Vista detects the Tamper event. There is a Service that runs in Windows 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, Windows 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 Windows 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:

     

    The following Knowledge Base (KB) article may help you confirm that you do not have any of the programs known to cause this type of issue.

     

    KB931699 - Error message when you use Windows Vista: "An unauthorized change was made to your license"

     

    http://support.microsoft.com/kb/931699/

     
    Second, in your Microsoft Genuine Diagnostic Tool (MGADT) 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       12             19               1653                          07070-
     

    Note: I also see a "K" type Tamper Time Stamp. The “K“stands for Kernel Mode tamper. This is a minor tamper and is most likely 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.


    (Year)       (Month)      (Day)      (Time in 24format)      (Millisecond) 

    K:2008       12             18             1905                             28657-





    Now that you know the time of the tamper, you can now try to connect that time with a program.

     

    1) Login to Windows Vista and select the option which 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) Then click System Stability Chart above the date 12/19 

    6) Below the chart, in the System Stability Report section look at the report titled "Software (Un) Installs for 12/19/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 Windows Vista to a Tamper State. Because of this, please repeat steps 5) through 7) for the dates 12/18/2008, 12/17/2008, and 12/16/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 12/19/2008, this process may not be helpful.  The removal of any application you may have installed recently could go a long way to troubleshooting these issues as well since it may fall outside of the 3 day time frame described above.

    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 the following link below:

    http://go.microsoft.com/fwlink/?linkid=52029




    Thank you for visiting the Genuine Advantage forum


    Stephen Holm, MS
    WGA Forum Manager


    Stephen Holm
    • Marked as answer by Stephen Holm Friday, December 19, 2008 10:02 PM
    Friday, December 19, 2008 10:01 PM
  • I don't ever install such programs like in KB931699.

    I already saw stability monitor and first svhost(Plug&Play, DCOM etc)-crash dated 11.27.2008. Last program I install was ZA downloading date 11.01.2008.

    And 12.18-19.2008 I upgrade windows thru the Windows Update - there are a lot of patch installed but it's useless because the 'Mod-Auth' already was before.
     
    I have an object in Windows Defender isolation list: Name: SettingsModifier:Win32/PossibleHostFileHijack Level: Medium Date: 12.17.2008

    Maybe it is but I was already delete that object and nothing was changes. Now it's exist because I restore system into previous point.

    I Uninstall all Windows upgrades but problem still exist... All other progarms was install a long time ago before the crash.

    PS About "no cost support" I see only phone numbers and commercial support request license & additional support cost of 149 usd. Sorry I don't believe in no cost phone talking. :)

    Thank you for your time, Stephen!

    • Edited by Dr. Yuri Saturday, December 20, 2008 10:05 PM
    Saturday, December 20, 2008 1:27 AM
  • Ok. Thanks to all of the Microsoft society /social.microsoft.com

    Like an always I'll make it by my self.

    Goodluck.

    Saturday, December 20, 2008 10:06 PM
  •  Problem fixed!

    I Download latest 30-days trial Kaspersky antivirus(KAV) program.
    KAV report:
    C:\Windows\system32\twext.exe - Trojan.Win32.Agent.anyc
    twext.exe\twext.exe - HEUR:Trojan.Win32.Generic 
    C:\Users\User\AppData\Local\Temp\wJQs.exe - Trojan.Win32.Agent.anyc

    When this two files was deleted problem with "Invalid license" gone.

    Where is it come from? I don't know because:
    - This is my personal computer.
    - I always use a firewall, never click on unknown EXE-files in e-mail or web.
    - If I download such files then I save them in another directory(always in one) so I know which files I download and that directory is clean.

    Conclusion:
    1) Windows Defender is useless.
    2) Windows License validation(WGA): paranoid.
    3) Time Stamp useless (TTS was 2008 and Trojan was 2005-2006)

    I hope that this information be unneeded for somebody else.

    Happy New Year and Merry Christmas!



    Monday, December 22, 2008 4:46 PM