locked
Suddenly will not validate RRS feed

  • Question

  • NOTE TO WOULD-BE HELPERS:  I think I solved the problem for now, so no rush at all.  This is really strange though.  Please let me know if you have any suggestions, I absolutely DO NOT want this to happen again if I can help it.

    ----------------

    Yesterday I uninstalled my registered version of Norton 360, along with the Symantec LiveUpdate software because my subscription was up and I was annoyed at how the software seemed to bog down my computer and interrupt me randomly.  Tonight I'm online doing my homework(I'm an online student, so my computer is VERY important to me) and I suddenly get this validation error.

    There is absolutely zero chance anything on this computer is pirated.  The copy of Windows Vista was preinstalled on this laptop from Dell.  I also own a registered copy of Microsoft Office that I bought from a direct download from microsoft.com.  The only other installed programs are iTunes, Firefox, EditPad Lite, The Sims 2, and yWriter.  All perfectly legit programs that have been running on this computer for over a year.

    I am terrified to turn this thing off because I spent all of yesterday writing two papers for my philosophy class in MS Word.  And after searching on the internet I found that this problem locks a person out of their computer.

    I ran the diagnostic tool which is telling me this:

    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: *****-*****-4WD8X-M9WM7-CH4CG
    Windows Product Key Hash: EkdqJZ28Y9zyrh7DU/lHNjTXlQY=
    Windows Product ID: 89572-OEM-7332166-00096
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6000.2.00010300.0.0.002
    ID: {A3AE71D4-23F5-4BF6-8D96-2F8762D15A4F}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.7.69.2
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Basic
    Architecture: 0x00000000
    Build lab: 6000.vista_gdr.080917-1612
    TTS Error: M:20090113031845959-
    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 Ultimate 2007 - 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_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>{A3AE71D4-23F5-4BF6-8D96-2F8762D15A4F}</UGUID><Version>1.7.0110.1</Version><OS>6.0.6000.2.00010300.0.0.002</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-CH4CG</PKey><PID>89572-OEM-7332166-00096</PID><PIDType>2</PIDType><SID>S-1-5-21-358520094-1907991459-2520644621</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Vostro 1400                     </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A03</Version><SMBIOSVersion major="2" minor="4"/><Date>20070925000000.000000+000</Date></BIOS><HWID>4D323507018400EA</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>DELL  </OEMID><OEMTableID>M08    </OEMTableID></OEM><BRT/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-002E-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Ultimate 2007</Name><Ver>12</Ver><Val>6883F24577A7F78</Val><Hash>WCtZk5arEkzthAR7pvigfMRb1gs=</Hash><Pid>81608-956-6919082-65577</Pid><PidType>1</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="44" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/><App Id="BA" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAKx4HgAAAAAAYWECADAgAACABS+zcHXJARhDs/4hWdo7Xkl9D+HKpnjNmgcID3QCgi81TkVnbld+zBYYNT+Dd755W9p9FTTBoRY3hlB6ccWFlfEC2sD/66Lqp2G1Bh+wdLNpvNraHdY3sEGnmR0ReJ9KlWCJouxq6PAIwHwHVMfvNauSbFvmaTBYC/G/amipOp+xBjXwWbbP9S/GUDYecePFRKM/leS97bxOVVm9fICZUkfHdDNbo725QzYM7NoLIP6BsYz9FHAia30CP0z0OYRuUWLuf4S5JTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

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

    HWID Data-->
    HWID Hash Current: PAAAAAEABgABAAIAAQABAAAAAwABAAEAnJ80RWaAtLOQR4RniIBC9UaDwoPKjhbU8vS03mJShrqsViqF

    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   
      SSDT   PmRef  CpuPm

    I turned in a support ticket but I really need some sleep and I'm afraid to turn the computer off.  :(  If someone can please help me, I'd really appreciate it.



    ------------



    EDIT: I broke down and restarted the computer, to see if I could safe mode + system restore, but to my surprise it let me back in with no hassle(which I wasn't expecting because I googled this problem and everyone else said they were locked out).  I then went through and uninstalled everything I don't regularly use, backed up my files, and installed the new updates.  I then went through the web-browser validation and Vista and my copy of Office both validated.  Can you tell by my diagnostic stuff what happened?  Will it happen again?  Do I still need to just use system restore to go back before the error?  Thank you for your help. :)

    Tuesday, January 13, 2009 12:15 PM

Answers

  • Good Morning Lindsay,


    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:2009         01           13                 0318                         45959-
     

    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 01/13.  

    6) Below the chart, in the System Stability Report section look at the report titled "Software (Un) Installs for 01/13/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 Windows Vista to a Tamper State. Because of this, please repeat steps 5) through 7) for the dates 01/12/200901/11/2009, and 01/10/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 (say) on 09/01/2007, but you didn't run (and, hence, prompted the tamper state) till 01/13/2009, 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 Tuesday, January 13, 2009 6:02 PM
    Tuesday, January 13, 2009 6:01 PM