none
unauthorized change/ windows not genuine issue RRS feed

  • Question

  • I just bought my computer 10 days ago from circuit city with an pre-installed version of the MS WINDOWS VISTA. I think after i delted Norton Software which came from all those pre-installed software and installed my own "incompatible" anti-visurs software, i started to have this issue. it's very annoying and after certain time of leaving the computer on, i can't change my wallpaper or opening up control panel. As well as even though i put my computer to the sleep mode, after a while, it turns on by itself again. Please fix this probelm for me and i hope it's not because of all those business partner thing that makes MS to have these messages for people to use all their partner's softwares....Please let me know how i won't see this message anymore~

     

    Thank you!

     

     

    Diagnostic Report (1.7.0069.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0x80072efd
    Cached Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-27HYQ-XTKW2-WQD8Q
    Windows Product Key Hash: U8YEZzymoD4DMyaMb32rPrNIS90=
    Windows Product ID: 89578-OEM-7332157-00061
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6000.2.00010300.0.0.003
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {F52414A6-F1EB-4785-9D2A-A65812CE2F9F}(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_ldr.071023-1545
    TTS Error: K:20080219191927934-M:20080219191612079-
    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: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: FCEE394C-2920-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>{F52414A6-F1EB-4785-9D2A-A65812CE2F9F}</UGUID><Version>1.7.0069.0</Version><OS>6.0.6000.2.00010300.0.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-WQD8Q</PKey><PID>89578-OEM-7332157-00061</PID><PIDType>2</PIDType><SID>S-1-5-21-1215560068-3439553330-3653371526</SID><SYSTEM><Manufacturer>HP-Pavilion</Manufacturer><Model>GX611AA-ABA m8300f</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>5.20 </Version><SMBIOSVersion major="2" minor="4"/><Date>20071003000000.000000+000</Date></BIOS><HWID>6C323507018400F6</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-CPC</OEMTableID></OEM><BRT/></MachineData><Software><Office><Result>109</Result><Products/></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAIIaAwAAAAAAYWECADAgAAAUo9RDUm3IARhDs/4hWdo7Xkl9D+HKpngJY2BGAD9AfpalT9rGt5SwkzJ+bfc2pqzBx+KR3tRdrhQjdPDwDinTfkQXASERseGY/k1WTObSVcK0f69TvjEi/CnzzILgnyke56K3TqupK/u1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y2BX7mQ2Q7393z5XQ50VXv9mhrKhq4UIi+PwtGQfjOGIjOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYQ7P+IVnaO15JfQ/hyqZ4t8D4PgdJXJwpGC4fiyjBpyKCvcAi0faj50tGKX5bg8MUI3Tw8A4p035EFwEhEbHhztKVgj6S5d/sDrqKDszZqfwp88yC4J8pHueit06rqSv7tVLwe28YiH1BLYCERqYZDkmvhBlGHDl+f1L5AB51ccqVKU2BSf+UPRIXRoSSmEybGyYrHLwGFoM8hWdM+/ctgV+5kNkO9/d8+V0OdFV7/ZoayoauFCIvj8LRkH4zhiIzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGEOz/iFZ2jteSX0P4cqmeNG9/tCjLX2jpaRroUN+LSPjarpsb6GIrOFoQC7CeSKtUXQf06H6EkTDtcpIBKFFtxnvE7dMdqsoqKxv89iUMvPWaOSPNeFyr3ibjxx4moY4+7VS8HtvGIh9QS2AhEamGQ5Jr4QZRhw5fn9S+QAedXHKlSlNgUn/lD0SF0aEkphMmxsmKxy8BhaDPIVnTPv3LQ4qbncHDzruEc0Tjda9mpQjRF/UyoDcPmxZ8TDtZ41/M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhDs/4hWdo7Xkl9D+HKpnjstZuNGTHZmq0Pz8Uvr7OK1L6ZhIubDSfdOmU47Vqz3hQjdPDwDinTfkQXASERseHNMSs99uIGmnbW3dl4rwN1/CnzzILgnyke56K3TqupK/u1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y2BX7mQ2Q7393z5XQ50VXv9mhrKhq4UIi+PwtGQfjOGIjOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYQ7P+IVnaO15JfQ/hyqZ4IrZRIIxURJ/jGU6p1waN7b3NMS81ypwzaeumHcrlA98UI3Tw8A4p035EFwEhEbHhmzvrON5TJEYEzyig12q2sfwp88yC4J8pHueit06rqSv7tVLwe28YiH1BLYCERqYZDkmvhBlGHDl+f1L5AB51ccqVKU2BSf+UPRIXRoSSmEybGyYrHLwGFoM8hWdM+/ctgV+5kNkO9/d8+V0OdFV7/ZoayoauFCIvj8LRkH4zhiIzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGEOz/iFZ2jteSX0P4cqmeBCDeU1AKhyLGKj8fXsWOgqrUC/3Hs6FeMaIP3SeGhJmFCN08PAOKdN+RBcBIRGx4a/X11CJzRPptcBmPwNLDNT8KfPMguCfKR7nordOq6kr+7VS8HtvGIh9QS2AhEamGQ5Jr4QZRhw5fn9S+QAedXHKlSlNgUn/lD0SF0aEkphMmxsmKxy8BhaDPIVnTPv3LYFfuZDZDvf3fPldDnRVe/2aGsqGrhQiL4/C0ZB+M4YiM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhDs/4hWdo7Xkl9D+HKpnhaZau9AaEeYkq97FkRovPZmsyx2kwWsLl7w0S0l8K/klF0H9Oh+hJEw7XKSAShRbeebCvbn5wgx+xW6K8QIqD81mjkjzXhcq94m48ceJqGOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y0OKm53Bw867hHNE43WvZqUI0Rf1MqA3D5sWfEw7WeNfzOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYQ7P+IVnaO15JfQ/hyqZ4U19M/WaeLDly9HtV6u7wKml9wcSr7Ggm6nJ2HLPZb1QUI3Tw8A4p035EFwEhEbHhFtA0LWIC9GwLQiqvojhMG/wp88yC4J8pHueit06rqSv7tVLwe28YiH1BLYCERqYZDkmvhBlGHDl+f1L5AB51ccqVKU2BSf+UPRIXRoSSmEybGyYrHLwGFoM8hWdM+/ctgV+5kNkO9/d8+V0OdFV7/ZoayoauFCIvj8LRkH4zhiIzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGEOz/iFZ2jteSX0P4cqmeOyrq9hNP53XA8uFGhLY68ER7HaO2IzcW6wDBAGXL+s4UXQf06H6EkTDtcpIBKFFt5YKBlD9SaV0UNCmhq3bREjWaOSPNeFyr3ibjxx4moY4+7VS8HtvGIh9QS2AhEamGQ5Jr4QZRhw5fn9S+QAedXHKlSlNgUn/lD0SF0aEkphMmxsmKxy8BhaDPIVnTPv3LQ4qbncHDzruEc0Tjda9mpQjRF/UyoDcPmxZ8TDtZ41/M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhDs/4hWdo7Xkl9D+HKpni5k8QIVfl4gXRACTDzg5yKL60vnESyUwpWDg0Qkr9clhQjdPDwDinTfkQXASERseFoLLbq0HWcFme9Nuz14yHL/CnzzILgnyke56K3TqupK/u1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y2BX7mQ2Q7393z5XQ50VXv9mhrKhq4UIi+PwtGQfjOGIjOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYQ7P+IVnaO15JfQ/hyqZ4fK8KumGqrxL5wYv4UwEF3Ctolg9S8ConZ1NRvFlM2o0UI3Tw8A4p035EFwEhEbHhZnntf8EcbKgn1c5uphdC+fwp88yC4J8pHueit06rqSv7tVLwe28YiH1BLYCERqYZDkmvhBlGHDl+f1L5AB51ccqVKU2BSf+UPRIXRoSSmEybGyYrHLwGFoM8hWdM+/ctgV+5kNkO9/d8+V0OdFV7/ZoayoauFCIvj8LRkH4zhiIzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM

     

    Wednesday, February 20, 2008 4:04 AM

Answers

  • Hello

     

      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      19           1916               12079

     

    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/19

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 02/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 Vista to a Tamper State. Because of this, please repeat steps 5) thru 7) for the dates 02/18/2008, 02/17/2008 and 02/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 02/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 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

     

    p.s. You do not need to use the software that came with your computer, just be sure that the software that you do use, is compatible with Vista

    Wednesday, February 20, 2008 5:57 PM

All replies

  • Hello

     

      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      19           1916               12079

     

    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/19

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 02/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 Vista to a Tamper State. Because of this, please repeat steps 5) thru 7) for the dates 02/18/2008, 02/17/2008 and 02/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 02/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 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

     

    p.s. You do not need to use the software that came with your computer, just be sure that the software that you do use, is compatible with Vista

    Wednesday, February 20, 2008 5:57 PM
  •  

    thanks for all the info. i've checked that it's not caused by any hardware problem. but i have one problem that is i failed to install the monitor driver on my pc,which in suspect,it's because it's all HP products, i don't really need to install.

     

    The changes i've made to the software is that i uninstalled NORTON and installed another product. I didn't have PC tools for FIREWALL before, so as you recommended, i just installed that a moment ago. I don't know if this is gonna help or not. I know it might be a compatibily probelm with my ANTI-VIRUS software, but that's a genuine product that i purchased internationally. I love to use that since it's been working very well. I hope WINDOWS is not trying to make its users to use all their partner's produts to make it's compatible with VISTA................

     

    I don't know if the installation of the Pc tools is going to help me solve this issue, i'll need to see for couple hours so that i know what i can do with it. Another thing is that i think PC TOOLS has a newer version today than the one that you told me. which is 3.0.0.62.......... which is higher than the 53. i wonder this should work right????

     

    Thank you!

    Thursday, February 21, 2008 7:09 AM
  • ok, i've just tested on the windows genuine website, that it still has the same issue~ my own copy of the anti-virus software is compatible with vista, i just checked it on the cover of the software~ i'm still trying to figure out what causes the problem~~~~

     

    Please HELP~~~~~~~

     

    Thursday, February 21, 2008 7:47 AM
  •  just want to fix my computer wrote:

     

    thanks for all the info. i've checked that it's not caused by any hardware problem.

     

    I'm unsure what you mean by this, but I don't believe I suggested that the issue was caused by a Hardware problem. If you see my post, I tried to explain that there is a Incomatible program running in Vista that is causing this issue.

     

     just want to fix my computer wrote:

    but i have one problem that is i failed to install the monitor driver on my pc,which in suspect,it's because it's all HP products, i don't really need to install

     

    I am unsure what you mean...is this related to the issue?

     

     just want to fix my computer wrote:

    The changes i've made to the software is that i uninstalled NORTON and installed another product. I didn't have PC tools for FIREWALL before, so as you recommended, i just installed that a moment ago. I don't know if this is gonna help or not.

     

      First off, Please re-read my post.  I specificly said "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"

    I Never "recommended" you install Any software.

     

     

     just want to fix my computer wrote:

    I know it might be a compatibily probelm with my ANTI-VIRUS software, but that's a genuine product that i purchased internationally. I love to use that since it's been working very well. I hope WINDOWS is not trying to make its users to use all their partner's produts to make it's compatible with VISTA................

     

      Microsoft does not care what programs you run on your computer. Long before Vista was released, Microsoft published the specifications (to everyone) on how to make programs compatible with Vista. but ANY program that was built before that, has a risk that it's not compatible with Vista and we highly recommend contacting the maker of that program and find out if there is any updates that make the program compatible.

     

     just want to fix my computer wrote:

    I don't know if the installation of the Pc tools is going to help me solve this issue, i'll need to see for couple hours so that i know what i can do with it. Another thing is that i think PC TOOLS has a newer version today than the one that you told me. which is 3.0.0.62.......... which is higher than the 53. i wonder this should work right????

     

    Thank you!

     

      No, installing PC Tool is not going to help, I never said it would...again I never said to install it. If you read my post, it basically says that you need to identify the program that is causing the problem then unistall it. I provide you a link to a list of programs known to cause this kind of problem and I provide tips on how best to identify the offending program.

     

    Darin Smith

    WGA Forum Manager

    Friday, February 22, 2008 11:07 PM
  • i just re-read your post, and followed by this step

     

    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/19

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 02/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 Vista to a Tamper State. Because of this, please repeat steps 5) thru 7) for the dates 02/18/2008, 02/17/2008 and 02/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 02/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 this issues as well since it may fall outside of the 3 day time frame described above.

     

     

    i found out that the failure could be possibly cause by the uninstallation of the NORTON program, and some of the components under norton.

     

    1. LiveUpdate (Symantec Corporation) was uninstalled....on 02/11/08

    2. Norton Antivirus was uninstalled

    3. Norton Antivirus says Application Configuration Change

    4. Norton Confidential Core was uninstalled.

    5. Norton Internet Security was uninstalled.

    6. Norton Protection Center was uninstalled.

    7. SPBBC 32bit was uninstalled.

    8. SymNet was uninstalled.

    9. Symantec Real Time Storage Protection Component was uninstalled.

    10. ccCommon was uninstalled.

     

    Then, there were couple application failures on 02/11/08

    1. PurblePlace. exe ( which is a window game)

    2. drm70to71.exe ( i don't know what this is )

    3. wmplayer. exe

     

    I guess the issued could possibly be affected by these changes. I didn't include all the applicaitons, but i think these might give me an answer.

     

    Please advise.

     

    Thank you!

    Tuesday, February 26, 2008 7:06 AM
  •  

    i found out that the failure could be possibly cause by the uninstallation of the NORTON program, and some of the components under norton.

     

    1. LiveUpdate (Symantec Corporation) was uninstalled....on 02/11/08

    2. Norton Antivirus was uninstalled

    3. Norton Antivirus says Application Configuration Change

    4. Norton Confidential Core was uninstalled.

    5. Norton Internet Security was uninstalled.

    6. Norton Protection Center was uninstalled.

    7. SPBBC 32bit was uninstalled.

    8. SymNet was uninstalled.

    9. Symantec Real Time Storage Protection Component was uninstalled.

    10. ccCommon was uninstalled.

     

    Then, there were couple application failures on 02/11/08

    1. PurblePlace. exe ( which is a window game)

    2. drm70to71.exe ( i don't know what this is )

    3. wmplayer. exe

     

    I guess the issued could possibly be affected by these changes. I didn't include all the applicaitons, but i think these might give me an answer.

     

    Please advise.

     

    Thank you!

    Monday, March 3, 2008 4:48 AM