locked
Another 0xc004d401 Error :( RRS feed

  • Question

  • For a couple days I've been getting a error saying that "You may be a victim software counterfeiting" and telling me that my system can't check for definition updates, error: code 0xc004d401. I know for a fact that I have a genuine Vista, and I started getting these pop ups only recently...

    I was browsing around the forums and learned that this happened because of an installed update, but I haven't been able to solve the problem.

    What would be the quickest and painless way to solve this issue?

    My error log is:

    Diagnostic Report (1.9.0006.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: {B77F8A08-600A-41CC-BD53-8B854A00ABD8}(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: 6001.vistasp1_gdr.080917-1612  
    TTS Error: K:2009 02 24 1544 07248-M:2009 02 21 1746 18967-  
    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 Home and Student 2007 - 100 Genuine  
    Microsoft Office Enterprise 2007 - 101 Not Activated  
    OGA Version: Registered, 1.6.28.0  
    Signed By: Microsoft  
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_672A8F41-307-80004005_672A8F41-349-80004005_672A8F41-244-80004005  
     
    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>{B77F8A08-600A-41CC-BD53-8B854A00ABD8}</UGUID><Version>1.9.0006.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-3841269493-2638356451-368668710</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Inspiron 530</Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>1.0.3</Version><SMBIOSVersion major="2" minor="5"/><Date>20070712000000.000000+000</Date></BIOS><HWID>26313507018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL  </OEMID><OEMTableID>FX09   </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>101</Result><Products><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><Val>E52BD8972A724</Val><Hash>MBxg6fYxUNNZUNJUcv86Q+ahuHE=</Hash><Pid>81602-914-5137561-68343</Pid><PidType>1</PidType></Product><Product GUID="{91120000-0030-0000-0000-0000000FF1CE}"><LegitResult>101</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>8840BC2266B0F71</Val><Hash>VxbG6+M2So1OSjswstFYCfCFCz8=</Hash><Pid>81599-952-5401092-65524</Pid><PidType>1</PidType></Product></Products><Applications><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: U1BMRwEAAAAAAQAABAAAAC/xKQMAAAAAYWECAARQnIeQvHrU/YvJAW4aG1/FHasdtBRBPRnxqCIeiCB/OBB5sYbo8nua2lXwpQ6mtgw1g2OZfvQspNFY8EYu4egbXy8A+bDxK6xyWL32WsBZYbIZJJLJezdT4XiJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agianu9goUWH6geLXihQIutLnMyAYp7WLHEBtimKU5XYrEVUDQCClGAgLAnSBbKbOgO9lrAWWGyGSSSyXs3U+F4iTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMbhobX8Udqx20FEE9GfGoIhFNY8IKVhB/yuLRyZXgEa+f0AWX8Md4ipUDpbrPmsx8UWUZj1TMnkMoBbVB3Vg//PZawFlhshkkksl7N1PheIkzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDG4aG1/FHasdtBRBPRnxqCI0k7k9rUFCxcsbgCLLiTFiu8gOvbUXpRqtRoOpoO+TpRR9WMSXmS9OjbuOdmfC18P2WsBZYbIZJJLJezdT4XiJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agixPHqS1zj7KOg725BvLgexUOYsaZE6PSbm6x2QV9+wRGxYliEPViqdQ+op2UoSBSw9lrAWWGyGSSSyXs3U+F4iTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM  
     
    Licensing Data--> 
    C:\Windows\system32\slmgr.vbs(1634, 5) (null): 0xC004D401  
     
    HWID Data--> 
    HWID Hash Current: PAAAAAIABAABAAEAAQACAAAABAABAAEAJJR48lz/3HTye7ZZZP6I/Xg/Bj/y9EQlPW2nh5q/ZqOsViqF  
     
    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        FX09     
      FACP          DELL        FX09     
      HPET          DELL        FX09     
      MCFG          DELL        FX09     
      SLIC          DELL        FX09     
      DMY2          DELL        FX09     
      SSDT          PmRef       CpuPm 
    Wednesday, February 25, 2009 1:14 AM

Answers

  • Hello Gabriela,

      

    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 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, we know that 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 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 Mod-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.
     
      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      02          21            1746                     18967-

     

    Note, I also see a "K" type Tamper Time Stamp. The “K“ stands for Kernel Mode tamper. This is a minor tamper and is most likely 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/21 

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

    Also Note: it has been found that Malware, such as Viruses and Trojans, can also be incompatible with Vista and can cause an In Memory Mod-Auth. A few users (that were experiencing an In Memory Mod-Auth) have confirmed that a Malware infection was the cause. If you follow the above steps and cannot find a program that is causing the Mod-Auth, you may want to investigate if a Virus or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free help with Malware infections.

    PC Safety:

    1-866-PCSafety or 1-866-727-2338

    http://www.microsoft.com/protect/support/default.mspx

    http://onecare.live.com/site/en-us/center/whatsnew.htm

    Thank you,
    Darin MS


    Attention Forum All Users: Please Do Not post your issue in someone else's Thread...Create your own.
    • Marked as answer by Darin Smith MS Wednesday, February 25, 2009 9:28 PM
    Wednesday, February 25, 2009 9:28 PM