locked
Unauthorized Change To Windows RRS feed

  • Question

  • To whom it may concern:

    I've had my new Dell laptop for a couple of weeks now and just got an error message that "An unauthorized change was made to windows" and that "You will no longer receive notifications, including those about your license or activation.  Use the link below to find out how to fix your system"

    I looked at the article on-line and do not believe I have any of the programs listed as incompatible.  I've read in other posts that if I added my MGA diag message here, you might be able to give me more specific direction as to what is wrong/incompatible.

    Thanks in advance for your help,
    Jason


    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: *****-*****-F4GJK-KG77H-B9HD2
    Windows Product Key Hash: iJAth4TbScMi8HdcPurlASXdEkw=
    Windows Product ID: 89578-OEM-7332157-00204
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6001.2.00010300.1.0.003
    ID: {C071C689-EB84-4747-9F9B-6F590BD631C6}(1)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.9.9.0
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6001.vistasp1_gdr.080917-1612
    TTS Error: M:20090121213205110-
    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: 100 Genuine
    Microsoft Office Professional Edition 2003 - 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-282-80041010_025D1FF3-170-80041010_025D1FF3-171-1_025D1FF3-434-80040154_025D1FF3-178-80040154_025D1FF3-179-2_025D1FF3-185-80070002_025D1FF3-199-3_3E121E02-115-80004005_E2AD56EA-761-d003_E2AD56EA-762-0_E2AD56EA-134-80004005_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\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>{C071C689-EB84-4747-9F9B-6F590BD631C6}</UGUID><Version>1.7.0110.1</Version><OS>6.0.6001.2.00010300.1.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-B9HD2</PKey><PID>89578-OEM-7332157-00204</PID><PIDType>2</PIDType><SID>S-1-5-21-3064979916-3915663759-1373607507</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Inspiron 1525                   </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A16</Version><SMBIOSVersion major="2" minor="4"/><Date>20081016000000.000000+000</Date></BIOS><HWID>8A303507018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Tokyo Standard Time(GMT+09:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL  </OEMID><OEMTableID>M08    </OEMTableID></OEM><BRT/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91E30409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>39ED6AE41526DA2</Val><Hash>eei2ENiskXis7ekH7MYYhdaRukI=</Hash><Pid>73931-721-3247372-57490</Pid><PidType>1</PidType></Product></Products><Applications><App Id="15" Version="11" Result="100"/><App Id="16" Version="11" Result="100"/><App Id="18" Version="11" Result="100"/><App Id="19" Version="11" Result="100"/><App Id="1A" Version="11" Result="100"/><App Id="1B" Version="11" Result="100"/><App Id="44" Version="11" Result="100"/><App Id="A1" Version="11" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAP4wMwAAAAAAYWECAARwxokwJJNExHvJAc9At6VrojbY4U/Z1uNN4rYoO33wRRzDwXxvjZTs0flxVaPgR7XyPT+CpuXDlPW7tKFw/Wffn/E2kaX5OmirHxljpJE4zCrelHg3e0WFz2QsK76hG2yNGl2cxd7o0co56pZebP4Stc5RIO/QG8Q06iKhAwb2AL20o5j+0QyTiiPWOZl1j/NBR2VxORvL0Dyvqzu3OQeCd5rIiDLE2mLTlj4C+46JxvVbUyhjbo8HqXpcBibWTOo/TveTfz891CtD2RRSaFac2eTbEyHOah378tqkAw+0SfDZX0n+Eyuac5snM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

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

    HWID Data-->
    HWID Hash Current: QAAAAAEABgABAAIAAQABAAAABQABAAEA6GFgTnoQtsBszMCyCiVsPEaDPDwGpJT78vSi8QyTMpKsVnKKvkEqhQ==

    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   DELL    M08   
      FACP   DELL    M08   
      HPET   DELL    M08   
      BOOT   DELL    M08   
      MCFG   DELL    M08   
      SLIC   DELL    M08   
      OSFR   DELL    M08   
      SSDT   PmRef  CpuPm


     

    Wednesday, January 21, 2009 1:03 PM

Answers

  • Hi heli.novice,

      You are on the right track. The issue is with a program that is incompatible with Vista. The list of incompatible programs, that you saw, only includes the programs we Know to be incompatible. There are sure to be others (there are allot of computer programs floating around out there).

      

    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 Mod-Auth occurs, it's also important to understand how Vista detects a Mod-Auth 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 TMod-Auth  State and it could take some time for the Mod-Auth to be detected. The important point to note is that the moment Vista detects the Mod-Auth, you know that the program that is causing the Mod-Auth, 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. (you can probably skip this step since I believe you have already seen that help article).
      
      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:2009     01           21            2132                     05110-


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

      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 some time in the past but you didn't run it till now, 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.  

    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 http://go.microsoft.com/fwlink/?linkid=52029

    Thank you,
    Darin MS


    Attention Forum All Users: Please Do Not post your issue in someone else's Thread...Create your own.
    • Proposed as answer by Darin Smith MS Wednesday, January 21, 2009 8:57 PM
    • Marked as answer by Darin Smith MS Tuesday, February 3, 2009 7:51 PM
    Wednesday, January 21, 2009 8:57 PM