locked
An unauthorised change was made to Windows. RRS feed

  • Question

  • Hi there,

    I've recently been getting spontaneous error messages regarding validation. I bought this computer last July and it's been trouble-free until recently. When I try to run any program or even when the computer's just idling, I get two message boxes popping up - one says, "You may be a victim of software counterfeiting." and the other, "An unauthorized change was made to Windows." The second box bears the error code 0xC004D401.

    I've pasted a copy of the diagnostic report results below. I'd greatly appreciate any and all help - thanks!


    Diagnostic Report (1.7.0110.1):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0xc004d401
    Cached Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-9Q27C-6CWD7-MQ3CQ
    Windows Product Key Hash: qhMbHikwhp/jGNClWTyMpDZP8h0=
    Windows Product ID: 89578-OEM-7332157-00115
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6000.2.00010300.0.0.003
    ID: {D1460850-74D3-4ED7-84C8-E83EC72303DC}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6000.vista_gdr.071023-1545
    TTS Error: K:20090104115843597-M:20090109151147651-
    Validation Diagnostic:
    Resolution Status: N/A

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

    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: 101 Not Activated
    Microsoft Office Standard Edition 2003 - 100 Genuine
    Microsoft Office Ultimate 2007 - 101 Not Activated
    Microsoft Office Home and Student 2007 - 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 77F760FE-153-80070002_7E90FEE8-203-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_E2AD56EA-761-d003_E2AD56EA-762-0_E2AD56EA-134-80004005_B4D0AA8B-1065-80070057_FA827CE6-153-8007007e_FA827CE6-180-8007007e

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 7.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>{D1460850-74D3-4ED7-84C8-E83EC72303DC}</UGUID><Version>1.7.0110.1</Version><OS>6.0.6000.2.00010300.0.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-MQ3CQ</PKey><PID>89578-OEM-7332157-00115</PID><PIDType>2</PIDType><SID>S-1-5-21-3190125270-3030402773-52859268</SID><SYSTEM><Manufacturer>Packard Bell BV</Manufacturer><Model>iPower X8630</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>1005 </Version><SMBIOSVersion major="2" minor="4"/><Date>20071011000000.000000+000</Date></BIOS><HWID>AD313507018400FA</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>PacBel</OEMID><OEMTableID>PBDTNB00</OEMTableID></OEM><BRT/></MachineData><Software><Office><Result>101</Result><Products><Product GUID="{90120409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Standard Edition 2003</Name><Ver>11</Ver><Val>34E7252F907DD00</Val><Hash>Gg8z8yDBheg78tj/2ZI0uU9gXlE=</Hash><Pid>70141-640-2769425-57217</Pid><PidType>14</PidType></Product><Product GUID="{91120000-002E-0000-0000-0000000FF1CE}"><LegitResult>101</LegitResult><Name>Microsoft Office Ultimate 2007</Name><Ver>12</Ver><Val>216A8614A72F70C</Val><Hash>au9bt1YwdTYjprG8+36sw09bUnk=</Hash><Pid>81608-902-2697121-65848</Pid><PidType>1</PidType></Product><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><PidType>19</PidType></Product></Products><Applications><App Id="16" Version="11" Result="100"/><App Id="18" Version="11" Result="100"/><App Id="1A" Version="11" Result="100"/><App Id="1B" Version="11" Result="100"/><App Id="15" Version="12" Result="101"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="101"/><App Id="1A" Version="12" Result="101"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="101"/><App Id="A1" Version="12" Result="100"/><App Id="BA" Version="12" Result="101"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAJmXzAAAAAAAYWECADAgAABgedBR4mrJAW4aG1/FHasdtBRBPRnxqCKz7EbE3pO+/AB5kyYiEzCSdDcHTihOPa1rdmES9n3Q5iB1W5n2A+lDPPdVGB2dW432WsBZYbIZJJLJezdT4XiJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agipsTaXrRWnUCyYatDieiTFNj8EiZjFPUOQk/bCgM0mzGKILxj3OonhwhMo6zuzeiP9lrAWWGyGSSSyXs3U+F4iTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMbhobX8Udqx20FEE9GfGoIqYprF/Qb0GGJiVSYsvjMXogS8zJjAgiiXcYflT2Vn7MiiC8Y9zqJ4cITKOs7s3oj/ZawFlhshkkksl7N1PheIkzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDG4aG1/FHasdtBRBPRnxqCLRk2bGJcOyQz1mvJmneo72MuJnn7DjKtMuzqaVn8Ms6SAW1e8qVyrC6ZRqEldbMwT2WsBZYbIZJJLJezdT4XiJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agi/szI058xiT+u+xgAR1LcnXchZ7/g8hXwSDK/aFfuB7monVGbYXcRJlU07W6dvqlT9lrAWWGyGSSSyXs3U+F4iTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMbhobX8Udqx20FEE9GfGoIv7MyNOfMYk/rvsYAEdS3J18UeT8rFCKA83T0uSpcXQOqJ1Rm2F3ESZVNO1unb6pU/ZawFlhshkkksl7N1PheIkzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDA==

    Licensing Data-->
    C:\Windows\system32\slmgr.vbs(291, 5) (null): 0xC004D401

    HWID Data-->
    HWID Hash Current: OAAAAAEAAgABAAEABQABAAAAAgABAAEAeqj8iLSMwCBIJO7rMHrarkKqwPvy9OBBSJ5gT6xWzDE=

    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            PacBel        PBDTNB00
      FACP            PacBel        PBDTNB00
      HPET            PacBel        PBDTNB00
      MCFG            PacBel        PBDTNB00
      SLIC            PacBel        PBDTNB00
      SSDT            PacBel        PBDTNB00



    Friday, January 9, 2009 3:50 PM

Answers

  • sebhaque,

    Your Vista is in, what is known as 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) 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 occure.

     

    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 is No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, your issue is an In Memory Mod-Auth. 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.

    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       01      03         1935                02089

    In your case, there is also a 'K' type TTS listed (K:20080104094514981) A 'K' type tamper is also know as a Kernel Mod tamper and it is a minor issue I beleive this tamper can be directly attributed to the Mod-Auth tamper and once that is fixed, the kernel mod tamper should disappear.


    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 01/03

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 01/03/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 01/02/2008, 01/01/2008 and 12/31/2007

     

      This could tell us 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 01/03/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, in addition to the list of incompatible programs found un the URL above, 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 updateing to the most recent version.

    Rick

    • Marked as answer by RickImAPC Friday, January 9, 2009 8:22 PM
    Friday, January 9, 2009 8:20 PM

All replies

  • sebhaque,

    Your Vista is in, what is known as 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) 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 occure.

     

    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 is No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, your issue is an In Memory Mod-Auth. 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.

    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       01      03         1935                02089

    In your case, there is also a 'K' type TTS listed (K:20080104094514981) A 'K' type tamper is also know as a Kernel Mod tamper and it is a minor issue I beleive this tamper can be directly attributed to the Mod-Auth tamper and once that is fixed, the kernel mod tamper should disappear.


    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 01/03

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 01/03/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 01/02/2008, 01/01/2008 and 12/31/2007

     

      This could tell us 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 01/03/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, in addition to the list of incompatible programs found un the URL above, 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 updateing to the most recent version.

    Rick

    • Marked as answer by RickImAPC Friday, January 9, 2009 8:22 PM
    Friday, January 9, 2009 8:20 PM
  • Hi Rick,

    Thanks very much for your extremely detailed answer. I've followed all your steps and read all the information up until number 6 - my Reliability Monitor only dates back to August 2008, which is when I must have bought the computer (not July as I previously mentioned).

    Nonetheless, I've checked through the application installs, and these are the entries:

    19/12/2008: Definition update for Windows Defender - KB915597
    20/12/2008: Disk Drive x2, Generic Volume x2, Microsoft WPD FileSystem Volume Driver x2, USB Composite Device, USB Mass Storage Device x2, USB\VID_0FCE&PID_D039\3597570142651790 - the last one failed to install.
    23/12/2008: Definition update for Windows Defender - KB915597
    26/12/2008: Definition update for Windows Defender - KB915597
    30/12/2008: Definition update for Windows Defender - KB915597
    31/12/2008: Adobe Reader 8.1.2
    01/01/2009: Adobe Acrobat and Reader 8.1.2 Security Update 1 (KB403742)

    The problem has been occurring since around the same time Acrobat Reader was installed. I've uninstalled it for now and will see if that solves the problem. Is there anything else that I need to monitor or needs to be brought to attention?

    Thanks once again for your help.

    Seb
    Saturday, January 10, 2009 11:28 AM
  • I still get the message box popping up with the unauthorised change notification, albeit the counterfeiting one hasn't appeared since the uninstall. The error code remains the same as before - is there anything I've missed?

    Thanks.
    Seb
    Saturday, January 10, 2009 3:14 PM