locked
Crippled Vista Ultimate RRS feed

  • Question

  •  

    Crippled Vista Ultimate

     

    My Windows Vista Ultimate system has been 'crippled' due to validation failure. The system worked properly for months,  and then the problems happened out of the blue.

     

    My Dell computer came with XP2,which I upgraded to Vista Premium purchased from a large retail chain. I then upgraded this to Ultimate via the Microsoft website. The enabling licence was from Digital River.

     

    I've spent over a month trying to resolve this, including the advice given by:

     

    http://www.microsoft.com/genuine/downloads/nonGenuineVista.aspx?displaylang=en&Error=0x80070426&sGuid=978d8b06-8f65-40e1-bfb1-1d80b4835eda

     

    Here is the WGA report:

     

    Diagnostic Report (1.7.0062.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Genuine
    Validation Code: 0
    Online Validation Code: 0x80070426
    Cached Validation Code: N/A, hr = 0x80070426
    Windows Product Key: *****-*****-CX49B-K4FRQ-CQMCP
    Windows Product Key Hash: k/HEt8aVtxCGoUlFmDRPXQXZcU0=
    Windows Product ID: 89580-283-7294767-71509
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.0.6000.2.00010100.0.0.001
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {197605FD-FDF2-460F-8FB0-BD0D7A39228D}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.7.59.1
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Ultimate
    Architecture: 0x00000000
    Build lab: 6000.vista_gdr.071009-1548
    TTS Error: K:20071213073140777-M:20071226064613010-
    Validation Diagnostic:
    Resolution Status: N/A

    WgaER Data-->
    Grace Flag: N/A, hr = 0x80070426
    Commit: N/A, hr = 0x80070426
    Reboot Flag: 0x0
    ThreatID(s): N/A, hr = 0x80070426
    Wgaer.exe Version: N/A, hr = 0x80070002
    Wgaer.exe Signed By: 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: 103 Blocked VLK
    OGA Version: Registered, 1.6.21.0
    Signed By: Microsoft
    Office Diagnostics: 7E90FEE8-169-80004005_B4D0AA8B-514-80004005_B4D0AA8B-531-645_B4D0AA8B-531-645_025D1FF3-282-80041013_025D1FF3-170-80041013_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: N/A, hr=0x80070002
    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>{197605FD-FDF2-460F-8FB0-BD0D7A39228D}</UGUID><Version>1.7.0062.0</Version><OS>6.0.6000.2.00010100.0.0.001</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-CQMCP</PKey><PID>89580-283-7294767-71509</PID><PIDType>5</PIDType><SID>S-1-5-21-206368328-987270798-2167864653</SID><SYSTEM><Manufacturer>Dell Inc.                </Manufacturer><Model>Dell DXP051                  </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.                </Manufacturer><Version>A07</Version><SMBIOSVersion major="2" minor="3"/><Date>20070108000000.000000+000</Date></BIOS><HWID>E5733207018400EC</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>2</stat><msppid></msppid><name>Dell Dimension DXPO51</name><model>Pentium Dual Core</model></SBID><OEM/><BRT/></MachineData><Software><Office><Result>103</Result><Products><Product GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>103</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>ACD7202654E586</Val><Hash>fFic3JgCreGGRxyF8uMWB4R4Jcg=</Hash><Pid>89388-707-1528066-65867</Pid><PidType>14</PidType></Product></Products></Office></Software></GenuineResults> 

    Spsys.log Content: 0x800700EA

     

    Note that I get a 'Genuine' result quite often but I have, on a couple of occasions, got an 'Invalid' result.

     

    Thanks in advance for any help.

    Wednesday, December 26, 2007 9:21 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 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 of the In Memory variety. Which means that you have an application that 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 yours breaks down like this:

     

        (year)  (month) (day) (time in 24format) (millisecond)
    M:2007      12       26           0646                13010

     

    This number indicates the last time the Mod-Auth Tamper occured.

     

    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 thamper, I believe that the Kernel mode tamper will stop as well.

     

      Normally, I would provide you steps to find all the new programs that had been installed in the last 3 days and then have you uninstall then, one at a time, till the tamper no longer occured. But since you stated that this issue has been occuring for over a month, those steps would not be usefull.

     

      What I can suggest is to try to remember what program(s) you installed around the same time the Mod-Auth started and start by uninstalling those first.

     

    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.

     

    Thank you,

    Darin Smith

    WGA Forum Manager

    Wednesday, December 26, 2007 9:57 PM

All replies

  • Any help for my problem?

     

    Thanks

     

     

     

    Wednesday, December 26, 2007 7:43 PM
  • 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 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 of the In Memory variety. Which means that you have an application that 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 yours breaks down like this:

     

        (year)  (month) (day) (time in 24format) (millisecond)
    M:2007      12       26           0646                13010

     

    This number indicates the last time the Mod-Auth Tamper occured.

     

    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 thamper, I believe that the Kernel mode tamper will stop as well.

     

      Normally, I would provide you steps to find all the new programs that had been installed in the last 3 days and then have you uninstall then, one at a time, till the tamper no longer occured. But since you stated that this issue has been occuring for over a month, those steps would not be usefull.

     

      What I can suggest is to try to remember what program(s) you installed around the same time the Mod-Auth started and start by uninstalling those first.

     

    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.

     

    Thank you,

    Darin Smith

    WGA Forum Manager

    Wednesday, December 26, 2007 9:57 PM
  • Hello Darin,

     

    Thanks for your comprehensive reply. I'll work through the stages in it until I find the problem software.

     

    It's interesting you mention PC Tools software: I think I once had their firewall software installed although I do remember finding it a tad 'unfriendly' with my Vista software. Their famous Registry Mechanic software was my main interest in their company - I used this extensively. I'll start by removing that, just in case.

     

    I'll get back to you soon.

     

    Peter G.

    Thursday, December 27, 2007 3:58 AM
  •   Yes, I'm sorry the reply was so long. but I figure that if this issue is going to have such a major affect on your computer, you might as well understand what's going on and how it happened. 

     

      I just wish I had a tool, of some kind, that could pinpoint and tell me exactly what program is causing the problem. My Dev team tells me this is not possable due to code level stuff (that I, frankly, do not understand) but I'll continue to make a fuss  till they finally figure out how to make one for me.

     

    Darin 

     

    Friday, December 28, 2007 12:55 AM