locked
My Vista is no longer validated erroe code oxc004d401 RRS feed

  • Question

  • I have recently bought my laptop from dell with vista ultimate included. I'm now getting messages that it is no longer validated. The error code is OxC004D401. It must be a genuine product so why am i getting these disturbing messages. Thanks, Jamie
    Thursday, March 5, 2009 11:42 AM

Answers

  • Helllo Jamie,

    In order to recieve the best support, we request all users initially download and run the Genuine Diagnostics tool at this link http://go.microsoft.com/fwlink/?linkid=52012. Click "Continue" click the Windows tab, click the "Copy" button, then paste the report into a response message in this thread.


    If you do not have access to the Start Button:

    1) Login to Vista and Click the option that brings up Internet Explorer.
    2) Type: http://go.microsoft.com/fwlink/?linkid=52012 into the browser address bar.
    3) A window will come up asking if you want to Run or Save, Select Run
    4) When the program runs, Click the Continue button, then click the Copy button.
    5) Return to this thread by Typing: http://social.microsoft.com/Forums/en-US/genuinevista/thread/538c9f5a-1a41-4fd7-8da2-5c7a272907be into the browser address bar.
    6) In a reply post, Paste the Diagnostic Report.


    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please click the "Post was Helpful" button for that post. This will help us showcase the threads that best help our customers.
    Thursday, March 5, 2009 10:58 PM
  • Hello Colin,

    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.

    NOTE: We have seen an increase in this type of issue and we believe it is unlikely that software writers are still making programs that are incompatible with Vista. Instead, we believe that a majority of the issues are being caused by Malware that are doing the same things (on purpose) as incompatible programs do (by accident).

     

      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      05       01         1556                  55707-


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

    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 05/01/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 04/30/2009, 04/29/2009 and 04/28/2009  (or around the date the issue first occurred)

      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 number of users (that were experiencing your same issue) 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, Worm or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ (http://onecare.live.com/site/en-us/center/whatsnew.htm) before contacting PC Safety.

    PC Safety:

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

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

    Thank you,
    Darin MS

    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please vote the post as Helpful. This will help us showcase the threads that best help our customers.
    Friday, May 1, 2009 6:24 PM
  • 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.

    NOTE: We have seen an increase in this type of issue and we believe it is unlikely that software writers are still making programs that are incompatible with Vista. Instead, we believe that a majority of the issues are being caused by Malware that are doing the same things (on purpose) as incompatible programs do (by accident).

     

      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       05       01           1509                     03404-

     

    Note: I also see a "K" type Tamper Time Stamp. The “K“ stands for Kernel Mode tamper. Once you remove the program that is causing the In Memory Mod-Auth tamper, the Kernel Mode tamper may be resolved as well. But a Kernel Mode Tamper can sometime indicate a Malware infection. To be on the safe side, we strongly suggest scanning your system with the Anti-Virus program of your choice as well as with the OneCare Safety Scanner for Vista (http://onecare.live.com/site/en-us/center/whatsnew.htm)


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

    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 05/01/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 04/30/2009, 04/29/2009 and 04/228/2009  (or around the date the issue first occurred)

      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 number of users (that were experiencing your same issue) 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, Worm or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ (http://onecare.live.com/site/en-us/center/whatsnew.htm) before contacting PC Safety.

    PC Safety:

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

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

    Thank you,
    Darin MS

    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please vote the post as Helpful. This will help us showcase the threads that best help our customers.
    Friday, May 1, 2009 8:52 PM
  • Hello xsmail321,

      These forums are for the support of Windows Genuine Advantage Validation issues. Your post does not appear to a be Vista Activation or Validation related and, as such is, unfortunately, off-topic (as well as outside my main area of knowledge).

     

      I suggest reposting your question to one of the Vista Answers Forums at http://social.answers.microsoft.com/Forums/en-US/category/windowsvista/ or go to http://support.microsoft.com for additional support options.


    Note: once you find the Vista Answers forums that you want to post in, click the "Ask a Question" link in the upper left hand corner of the forum. That will create a new thread for you.

    Thank you,
    Darin MS 


    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please vote the post as Helpful. This will help us showcase the threads that best help our customers.
    Monday, May 4, 2009 6:28 PM
  • Hello nienke123,

    The core of your issue centers on the line in your Diagnostic Report that reads:

    File Scan Data-->
    File Mismatch: C:\Windows\system32\Slsvc.exe[6.0.6000.16509]
    File Mismatch: C:\Windows\system32\drivers\Spsys.sys[6.0.5840.16389]
    File Mismatch: C:\Windows\system32\Slcext.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\advapi32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\kernel32.dll[6.0.6000.16820]
    File Mismatch: C:\Windows\system32\rpcrt4.dll[6.0.6000.16525]
    File Mismatch: C:\Windows\system32\authz.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\msvcrt.dll[7.0.6000.16386]
    File Mismatch: C:\Windows\system32\samlib.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\ntdsapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\dnsapi.dll[6.0.6000.16615]
    File Mismatch: C:\Windows\system32\ws2_32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\nsi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\user32.dll[6.0.6000.16438]
    File Mismatch: C:\Windows\system32\gdi32.dll[6.0.6000.16766]
    File Mismatch: C:\Windows\system32\msimg32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\powrprof.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\setupapi.dll[6.0.6000.16609]
    File Mismatch: C:\Windows\system32\oleaut32.dll[6.0.6000.16609]
    File Mismatch: C:\Windows\system32\ole32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\shell32.dll[6.0.6000.16774]
    File Mismatch: C:\Windows\system32\shlwapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\version.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\winmm.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\oleacc.dll[4.2.5406.0]
    File Mismatch: C:\Windows\system32\mmdevapi.dll[6.0.6000.20564]
    File Mismatch: C:\Windows\system32\wtsapi32.dll[6.0.6000.16553]
    File Mismatch: C:\Windows\system32\regapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\crypt32.dll[6.0.6000.16425]
    File Mismatch: C:\Windows\system32\msasn1.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\userenv.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\secur32.dll[6.0.6000.16820]
    File Mismatch: C:\Windows\system32\netapi32.dll[6.0.6000.16764]
    File Mismatch: C:\Windows\system32\psapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\netrap.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\wldap32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\winbrand.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\iphlpapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\dhcpcsvc.dll[6.0.6000.16512]
    File Mismatch: C:\Windows\system32\winnsi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\dhcpcsvc6.dll[6.0.6000.16512]
    File Mismatch: C:\Windows\system32\gpapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\slc.dll[6.0.6000.16509]
    File Mismatch: C:\Windows\system32\gpsvc.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\sysntfy.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\winsta.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\nlaapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\ncrypt.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\bcrypt.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\mpr.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\credui.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\cryptui.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\wintrust.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\imagehlp.dll[6.0.6000.16470]
    File Mismatch: C:\Windows\system32\dbghelp.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\mssign32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\wininet.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\normaliz.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\iertutil.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\tapi32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\rtutils.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\rasapi32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\rasman.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\rasdlg.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\mprapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\activeds.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\adsldpc.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\atl.dll[3.5.2284.0]
    File Mismatch: C:\Windows\system32\certcli.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\winscard.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\netplwiz.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\urlmon.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\propsys.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\xmllite.dll[1.1.1002.0]
    File Mismatch: C:\Windows\system32\mlang.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\advpack.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\apphelp.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\msiltcfg.dll[4.0.6000.16386]
    File Mismatch: C:\Windows\system32\shunimpl.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\devmgr.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\newdev.dll[6.0.5054.0]
    File Mismatch: C:\Windows\system32\dwmapi.dll[6.0.6000.20530]
    File Mismatch: C:\Windows\system32\winspool.drv[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\cscapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\uxtheme.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\windowscodecs.dll[6.0.6000.16740]
    File Mismatch: C:\Windows\system32\ntshrui.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\feclient.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\shdocvw.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\browseui.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\imm32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\msctf.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\duser.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\winsxs\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6000.16386_none_9ea0ac9ec96e7127\gdiplus.dll[5.2.6000.16386]
    File Mismatch: C:\Windows\system32\msrating.dll[7.0.6000.16386]
    File Mismatch: C:\Windows\system32\ieframe.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\msi.dll[4.0.6000.16386]
    File Mismatch: C:\Windows\system32\mshtml.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\msls31.dll[3.10.349.0]
    File Mismatch: C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.6000.16386_none_87e0cb09378714f1\comctl32.dll[5.82.6000.16386]
    File Mismatch: C:\Windows\system32\comdlg32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\printui.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\cfgmgr32.dll[6.0.6000.16609]
    File Mismatch: C:\Windows\system32\puiapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\hlink.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\imgutil.dll[7.0.6000.16386]
    File Mismatch: C:\Windows\system32\usp10.dll[1.626.6000.16386]
    File Mismatch: C:\Windows\system32\inetcomm.dll[6.0.6000.16669]
    File Mismatch: C:\Windows\system32\msoert2.dll[6.0.6000.16480]
    File Mismatch: C:\Windows\system32\ieui.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\efsadu.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\mfc42u.dll[6.6.8063.0]
    File Mismatch: C:\Windows\system32\odbc32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\oledlg.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\linkinfo.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\query.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\clbcatq.dll[2001.12.6930.16386]
    File Mismatch: C:\Windows\system32\cabinet.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\scecli.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\w32topl.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\rpchttp.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\winhttp.dll[6.0.6000.16786]
    File Mismatch: C:\Windows\system32\fwpuclnt.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\ktmw32.dll[6.0.6000.16386]

     

    This means the file has been Tampered, Modified or has become Corrupt. Vista see this as an attack to bypass it's Licensing security.

    To resolve the issue, you need to either repair or replace the file with a known-good one (of the proper file version)

     

    First try repairing Windows using System Restore:

    1)    Reboot Vista into Safe Mode

    2)    Go to Control Panel

    3)    On the left hand side of the Control Panel window, Click on "Classic View"

    4)    Double-click "Backup and Restore Center"

    5)    On the left hand side of the window, click "Repair Windows using system restore"

    6)    Select "Choose Different Restore Point", Put a check in the box that says "Show restore points older than 5 days", select the restore point that corresponds to the date Before you first noticed the issue.

    7)    Click the "Next" button.

    8)    Reboot back into Normal mode

    9)    Vista should no longer be in Reduced Functionality mode

     

    If that doesn't work, we'll try doing a System Scan. The scan will look for bad Vista files and will attempt to repair them, if possible.

    1)    Login to Vista in Normal Mode (not safe mode)

    2)    Launch an Internet Browser

    3)    Type: %windir%\system32\ in the browser's address field

    4)    Scroll down till you find the file cmd.exe

    5)    Right-click the file and select 'Run as Administrator'

    6)    In the CMD window, type: sfc /scannow

    7)    Reboot twice and see if that resolves the issue.

    If neither of these sets of steps resolves the issue, my only other suggestions would be either to contact Vista support at http://support.microsoft.com or reinstall Vista.

    Thank you,
    Darin MS

    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please vote the post as Helpful. This will help us showcase the threads that best help our customers.
    Monday, May 4, 2009 7:52 PM

All replies

  • Helllo Jamie,

    In order to recieve the best support, we request all users initially download and run the Genuine Diagnostics tool at this link http://go.microsoft.com/fwlink/?linkid=52012. Click "Continue" click the Windows tab, click the "Copy" button, then paste the report into a response message in this thread.


    If you do not have access to the Start Button:

    1) Login to Vista and Click the option that brings up Internet Explorer.
    2) Type: http://go.microsoft.com/fwlink/?linkid=52012 into the browser address bar.
    3) A window will come up asking if you want to Run or Save, Select Run
    4) When the program runs, Click the Continue button, then click the Copy button.
    5) Return to this thread by Typing: http://social.microsoft.com/Forums/en-US/genuinevista/thread/538c9f5a-1a41-4fd7-8da2-5c7a272907be into the browser address bar.
    6) In a reply post, Paste the Diagnostic Report.


    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please click the "Post was Helpful" button for that post. This will help us showcase the threads that best help our customers.
    Thursday, March 5, 2009 10:58 PM
  • 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: *****-*****-PXJ77-RJDPB-MVMDM
    Windows Product Key Hash: 81eRDq6LtzPwJQxNV9Nw0iNrWFQ=
    Windows Product ID: 89578-OEM-7359657-17918
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.0.6000.2.00010300.0.0.003
    ID: {1D5E34A0-5141-47D3-B1CF-2EC198B24724}(1)
    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.090302-1506
    TTS Error: M:20090501155655707-
    Validation Diagnostic:
    Resolution Status: N/A

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

    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: 114 Blocked VLK 2
    Microsoft Office XP Professional with FrontPage - 114 Blocked VLK 2
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    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

    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>{1D5E34A0-5141-47D3-B1CF-2EC198B24724}</UGUID><Version>1.9.0006.1</Version><OS>6.0.6000.2.00010300.0.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-MVMDM</PKey><PID>89578-OEM-7359657-17918</PID><PIDType>3</PIDType><SID>S-1-5-21-339223764-1959756023-4129341945</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>0702   </Version><SMBIOSVersion major="2" minor="4"/><Date>20070528000000.000000+000</Date></BIOS><HWID>8E333507018400F6</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/><GANotification/></MachineData><Software><Office><Result>114</Result><Products><Product GUID="{90280409-6000-11D3-8CFE-0050048383C9}"><LegitResult>114</LegitResult><Name>Microsoft Office XP Professional with FrontPage</Name><Ver>10</Ver><Val>39476F84C4B4004</Val><Hash>4iCnywwNW1w4s9ukTIwGMGxyGic=</Hash><Pid>54185-640-0000025-17104</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="10" Result="114"/><App Id="16" Version="10" Result="114"/><App Id="17" Version="10" Result="114"/><App Id="18" Version="10" Result="114"/><App Id="1A" Version="10" Result="114"/><App Id="1B" Version="10" Result="114"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAMvQAgAAAAAAYWECADAgAABv2OIRbcrJARhDs/4hWdo7Xkl9D+HKpng0UlYVmm2YNL3fSk2K4IOvFKGasMKu2BHaRMQuybMLDRQjdPDwDinTfkQXASERseFB3TBdNOWmIfRxfxBPgMH8/CnzzILgnyke56K3TqupK/u1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y2BX7mQ2Q7393z5XQ50VXv9mhrKhq4UIi+PwtGQfjOGIjOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

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

    HWID Data-->
    HWID Hash Current: OgAAAAIAAgABAAEABAACAAAAAgABAAEAeqhczhjS+oQoK5IAFOz6Wtqu0E7y9OFBGuz6QHKorFYm6Q==

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            A_M_I_        OEMAPIC
      FACP            A_M_I_        OEMFACP
      HPET            A_M_I_        OEMHPET0
      MCFG            A_M_I_        OEMMCFG
      OEMB            A_M_I_        AMI_OEM
      SSDT            A_M_I_        POWERNOW


    Friday, May 1, 2009 4:18 PM
  • Hello Colin,

    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.

    NOTE: We have seen an increase in this type of issue and we believe it is unlikely that software writers are still making programs that are incompatible with Vista. Instead, we believe that a majority of the issues are being caused by Malware that are doing the same things (on purpose) as incompatible programs do (by accident).

     

      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      05       01         1556                  55707-


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

    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 05/01/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 04/30/2009, 04/29/2009 and 04/28/2009  (or around the date the issue first occurred)

      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 number of users (that were experiencing your same issue) 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, Worm or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ (http://onecare.live.com/site/en-us/center/whatsnew.htm) before contacting PC Safety.

    PC Safety:

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

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

    Thank you,
    Darin MS

    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please vote the post as Helpful. This will help us showcase the threads that best help our customers.
    Friday, May 1, 2009 6:24 PM
  • 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: *****-*****-DWM6X-2TFTB-JRYQ8
    Windows Product Key Hash: mOKuTEVBKfi8d1Ma/Ez42sgCL5A=
    Windows Product ID: 89576-426-2025741-71902
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.0.6001.2.00010100.1.0.006
    ID: {C9926277-40EC-47F4-91D6-D48B6D3C4FC7}(1)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.9.9.1
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Business
    Architecture: 0x00000000
    Build lab: 6001.vistasp1_gdr.090302-1506
    TTS Error: K:20090501125056104-M:20090501150903404-
    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 Home and Student 2007 - 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: B4D0AA8B-604-645_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-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>{C9926277-40EC-47F4-91D6-D48B6D3C4FC7}</UGUID><Version>1.9.0006.1</Version><OS>6.0.6001.2.00010100.1.0.006</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-JRYQ8</PKey><PID>89576-426-2025741-71902</PID><PIDType>5</PIDType><SID>S-1-5-21-2155271733-2109416328-3127108386</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>Presario C500 (RQ338UA#ABA)       </Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.11</Version><SMBIOSVersion major="2" minor="4"/><Date>20061130000000.000000+000</Date></BIOS><HWID>4BB33507018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-MPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><Val>6469D2F3DE12724</Val><Hash>2Tydyw3F2iQcsnt1buKMcbkAZiE=</Hash><Pid>81602-914-5629321-68967</Pid><PidType>1</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAK5/OgIAAAAAYWECAARQVIf31wKSVsrJARhy9171jCizkdIEkQaJZ66J20ekq6cu+Mzfmmet364lVFK5zJaO/qxlYNt5c4jLTOfDvX0zCybmDilyQLttVIxA6Iek00zI32DgJ4YZKpUAsEGnmR0ReJ9KlWCJouxq6PAIwHwHVMfvNauSbFvmaTCDPKtQZQFIQcDXIAwFGl6D9S/GUDYecePFRKM/leS97bxOVVm9fICZUkfHdDNbo72qUqYYmAlRJO05+WV1r70w2O6Pl99gqTnSYR4j0FashTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeuybmHMbq/rlZsn+xWh4WVTACf6GRN2NFc4pgQdnabRUTnw719Mwsm5g4pckC7bVSM0F2DWlQpDsA5JPAYjIopTLBBp5kdEXifSpVgiaLsaujwCMB8B1TH7zWrkmxb5mkwgzyrUGUBSEHA1yAMBRpeg/UvxlA2HnHjxUSjP5Xkve28TlVZvXyAmVJHx3QzW6O9qlKmGJgJUSTtOfllda+9MNjuj5ffYKk50mEeI9BWrIUzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrvz88uThzriSceF3Xp7MXzp0a8eW7KYWn+HxEq/YHBKe58O9fTMLJuYOKXJAu21UjJHB04M8lqHiixU263YtLZSwQaeZHRF4n0qVYImi7Gro8AjAfAdUx+81q5JsW+ZpMIM8q1BlAUhBwNcgDAUaXoP1L8ZQNh5x48VEoz+V5L3tvE5VWb18gJlSR8d0M1ujvapSphiYCVEk7Tn5ZXWvvTDY7o+X32CpOdJhHiPQVqyFM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDA==

    Licensing Data-->


    HWID Data-->
    HWID Hash Current: PAAAAAIABAABAAIAAgABAAAAAwABAAEAJJSU7JoqFT/AQ8x74hVI5PqPcHGysPL0d/YqbCKcUDqsVvga

    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   HP      NISSAN 
      FACP   HP      NISSAN 
      HPET   HP      NISSAN 
      BOOT   PTLTD   $SBFTBL$
      MCFG   HP      NISSAN 
      SLIC   HPQOEM  SLIC-MPC
      APIC   HP      NISSAN 
      SSDT   SataRe  SataAhci
      SSDT   SataRe  SataAhci
      SSDT   SataRe  SataAhci

     

    Friday, May 1, 2009 8:18 PM
  • 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.

    NOTE: We have seen an increase in this type of issue and we believe it is unlikely that software writers are still making programs that are incompatible with Vista. Instead, we believe that a majority of the issues are being caused by Malware that are doing the same things (on purpose) as incompatible programs do (by accident).

     

      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       05       01           1509                     03404-

     

    Note: I also see a "K" type Tamper Time Stamp. The “K“ stands for Kernel Mode tamper. Once you remove the program that is causing the In Memory Mod-Auth tamper, the Kernel Mode tamper may be resolved as well. But a Kernel Mode Tamper can sometime indicate a Malware infection. To be on the safe side, we strongly suggest scanning your system with the Anti-Virus program of your choice as well as with the OneCare Safety Scanner for Vista (http://onecare.live.com/site/en-us/center/whatsnew.htm)


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

    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 05/01/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 04/30/2009, 04/29/2009 and 04/228/2009  (or around the date the issue first occurred)

      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 number of users (that were experiencing your same issue) 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, Worm or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ (http://onecare.live.com/site/en-us/center/whatsnew.htm) before contacting PC Safety.

    PC Safety:

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

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

    Thank you,
    Darin MS

    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please vote the post as Helpful. This will help us showcase the threads that best help our customers.
    Friday, May 1, 2009 8:52 PM
  • ***sorry-- not sure where to post this.. this website is a headache and i can't figure out how to post a question!!!!

    Wireless Card Defective - Reset IP address?
    IP address is corrupt.
    Posted 5/2/09
    Problem: Able to connect to internet, but the IP address is defective.

    I recently bought a TOSHIBA "satellite" model about 2,3 months ago which came with Windows Vista. I have been only unhappy to frustrated with vista.

    Background:
    On 4/17/09 i was unable to connect to my wireless. I phoned up Toshiba, and the guy explained to me that i needed to "reset" the wireless link/card. The reason was, Windows Vista did an update and caused some kind of problem

    with the wireless link/card. I did exactly what he told me to do and it worked perfectly.

    on 4/28/09 I experienced the same problem, did this "reset" technique again and it worked perfectly.
    On 5/1/09 in the evening, I had the same problem did this "reset" technique but it did not work well. I knew i was connected because the icon in the lower right showed I was connected but I was unable to reach websites i.e.

    yahoo.com

    5/2/09 I phoned up TOSHIBA. The woman again said Windows Vista automatically updated the computer and in the process caused the IP Address to become defective.
    She said the only way to solve this problem is to re install the operating system. She said that this is not a TOSHIBA problem but a Windows Vista problem.

    I told her that for toshiba to endorse Windows vista which "updates" computers like this causing such defects is irresponsible, unethical and immoral. I do not have the time to reinstall windows, reinstall all my old programs, and transfer

    all my data onto an external hard drive.

    Please advise me what to do!
    1. Should I purchase windows XP off of ebay.com?
    2. Should I sell my toshiba computer online and use that money to buy and "older" computer with "windows xp?"

    ***Also, does anybody know of other websites/forums that I can post this question at? Have you guys used others that you liked?

    Please help!

    Saturday, May 2, 2009 6:40 PM
  • Hello xsmail321,

      These forums are for the support of Windows Genuine Advantage Validation issues. Your post does not appear to a be Vista Activation or Validation related and, as such is, unfortunately, off-topic (as well as outside my main area of knowledge).

     

      I suggest reposting your question to one of the Vista Answers Forums at http://social.answers.microsoft.com/Forums/en-US/category/windowsvista/ or go to http://support.microsoft.com for additional support options.


    Note: once you find the Vista Answers forums that you want to post in, click the "Ask a Question" link in the upper left hand corner of the forum. That will create a new thread for you.

    Thank you,
    Darin MS 


    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please vote the post as Helpful. This will help us showcase the threads that best help our customers.
    Monday, May 4, 2009 6:28 PM
  • Diagnostic Report (1.9.0006.1):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0x80070426
    Cached Validation Code: N/A, hr = 0x80070426
    Windows Product Key: *****-*****-JQMWD-2QJRJ-RJ34F
    Windows Product Key Hash: R8gPTEFMoOygFewoq/uOoWMpz68=
    Windows Product ID: 89578-OEM-7332157-00237
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6000.2.00010300.0.0.003
    ID: {FB4FA0C7-C37E-45E9-A30C-971BACAA8CB1}(1)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.9.9.1
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6000.vista_gdr.090302-1506
    TTS Error: M:20090504204353894-
    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 Enterprise 2007 - 100 Genuine
    OGA Version: Registered, 1.7.111.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_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-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-->
    File Mismatch: C:\Windows\system32\Slsvc.exe[6.0.6000.16509]
    File Mismatch: C:\Windows\system32\drivers\Spsys.sys[6.0.5840.16389]
    File Mismatch: C:\Windows\system32\Slcext.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\advapi32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\kernel32.dll[6.0.6000.16820]
    File Mismatch: C:\Windows\system32\rpcrt4.dll[6.0.6000.16525]
    File Mismatch: C:\Windows\system32\authz.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\msvcrt.dll[7.0.6000.16386]
    File Mismatch: C:\Windows\system32\samlib.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\ntdsapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\dnsapi.dll[6.0.6000.16615]
    File Mismatch: C:\Windows\system32\ws2_32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\nsi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\user32.dll[6.0.6000.16438]
    File Mismatch: C:\Windows\system32\gdi32.dll[6.0.6000.16766]
    File Mismatch: C:\Windows\system32\msimg32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\powrprof.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\setupapi.dll[6.0.6000.16609]
    File Mismatch: C:\Windows\system32\oleaut32.dll[6.0.6000.16609]
    File Mismatch: C:\Windows\system32\ole32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\shell32.dll[6.0.6000.16774]
    File Mismatch: C:\Windows\system32\shlwapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\version.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\winmm.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\oleacc.dll[4.2.5406.0]
    File Mismatch: C:\Windows\system32\mmdevapi.dll[6.0.6000.20564]
    File Mismatch: C:\Windows\system32\wtsapi32.dll[6.0.6000.16553]
    File Mismatch: C:\Windows\system32\regapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\crypt32.dll[6.0.6000.16425]
    File Mismatch: C:\Windows\system32\msasn1.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\userenv.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\secur32.dll[6.0.6000.16820]
    File Mismatch: C:\Windows\system32\netapi32.dll[6.0.6000.16764]
    File Mismatch: C:\Windows\system32\psapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\netrap.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\wldap32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\winbrand.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\iphlpapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\dhcpcsvc.dll[6.0.6000.16512]
    File Mismatch: C:\Windows\system32\winnsi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\dhcpcsvc6.dll[6.0.6000.16512]
    File Mismatch: C:\Windows\system32\gpapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\slc.dll[6.0.6000.16509]
    File Mismatch: C:\Windows\system32\gpsvc.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\sysntfy.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\winsta.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\nlaapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\ncrypt.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\bcrypt.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\mpr.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\credui.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\cryptui.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\wintrust.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\imagehlp.dll[6.0.6000.16470]
    File Mismatch: C:\Windows\system32\dbghelp.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\mssign32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\wininet.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\normaliz.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\iertutil.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\tapi32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\rtutils.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\rasapi32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\rasman.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\rasdlg.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\mprapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\activeds.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\adsldpc.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\atl.dll[3.5.2284.0]
    File Mismatch: C:\Windows\system32\certcli.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\winscard.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\netplwiz.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\urlmon.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\propsys.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\xmllite.dll[1.1.1002.0]
    File Mismatch: C:\Windows\system32\mlang.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\advpack.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\apphelp.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\msiltcfg.dll[4.0.6000.16386]
    File Mismatch: C:\Windows\system32\shunimpl.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\devmgr.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\newdev.dll[6.0.5054.0]
    File Mismatch: C:\Windows\system32\dwmapi.dll[6.0.6000.20530]
    File Mismatch: C:\Windows\system32\winspool.drv[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\cscapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\uxtheme.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\windowscodecs.dll[6.0.6000.16740]
    File Mismatch: C:\Windows\system32\ntshrui.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\feclient.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\shdocvw.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\browseui.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\imm32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\msctf.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\duser.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\winsxs\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6000.16386_none_9ea0ac9ec96e7127\gdiplus.dll[5.2.6000.16386]
    File Mismatch: C:\Windows\system32\msrating.dll[7.0.6000.16386]
    File Mismatch: C:\Windows\system32\ieframe.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\msi.dll[4.0.6000.16386]
    File Mismatch: C:\Windows\system32\mshtml.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\msls31.dll[3.10.349.0]
    File Mismatch: C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.6000.16386_none_87e0cb09378714f1\comctl32.dll[5.82.6000.16386]
    File Mismatch: C:\Windows\system32\comdlg32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\printui.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\cfgmgr32.dll[6.0.6000.16609]
    File Mismatch: C:\Windows\system32\puiapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\hlink.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\imgutil.dll[7.0.6000.16386]
    File Mismatch: C:\Windows\system32\usp10.dll[1.626.6000.16386]
    File Mismatch: C:\Windows\system32\inetcomm.dll[6.0.6000.16669]
    File Mismatch: C:\Windows\system32\msoert2.dll[6.0.6000.16480]
    File Mismatch: C:\Windows\system32\ieui.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\efsadu.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\mfc42u.dll[6.6.8063.0]
    File Mismatch: C:\Windows\system32\odbc32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\oledlg.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\linkinfo.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\query.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\clbcatq.dll[2001.12.6930.16386]
    File Mismatch: C:\Windows\system32\cabinet.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\scecli.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\w32topl.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\rpchttp.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\winhttp.dll[6.0.6000.16786]
    File Mismatch: C:\Windows\system32\fwpuclnt.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\ktmw32.dll[6.0.6000.16386]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{FB4FA0C7-C37E-45E9-A30C-971BACAA8CB1}</UGUID><Version>1.9.0006.1</Version><OS>6.0.6000.2.00010300.0.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-RJ34F</PKey><PID>89578-OEM-7332157-00237</PID><PIDType>2</PIDType><SID>S-1-5-21-2869786479-2332408029-3606691292</SID><SYSTEM><Manufacturer>TOSHIBA</Manufacturer><Model>Satellite P300</Model></SYSTEM><BIOS><Manufacturer>TOSHIBA</Manufacturer><Version>V2.70   </Version><SMBIOSVersion major="2" minor="4"/><Date>20080414000000.000000+000</Date></BIOS><HWID>0E313507018400FA</HWID><UserLCID>0413</UserLCID><SystemLCID>0413</SystemLCID><TimeZone>West-Europa (standaardtijd)(GMT+01:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>TOSQCI</OEMID><OEMTableID>TOSQCI00</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>56A0A8A48F69F73</Val><Hash>rjMDL6J0fh25/cEm7q3V3eQn1oY=</Hash><Pid>81599-953-3993317-65927</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: U1BMRwEAAAAAAQAABAAAAPIJAAAAAAAAYWECANOQ06eF9fNMkczJAdArSr9MLECc5R83cvYPeMwGXpMur4X+/08kVmtYmTsooZ0eZqYAqw9CvwR4NdoYcxzlbKaVHBjD6SE/4CKjeOsBcMEzqhTG7Em0l8vXpxS427OKLWTN3/xFyngmD3afWQd5BWut+vD3FqOkH5qwY3oKzOF7eXdqQzOdQlJCgYTeP9KSju/t9vu9LXUgneZO8JuQnPomGb9VupAJaZo25SIJxGN5hPlYXq2AFDshBm86M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMBl6TLq+F/v9PJFZrWJk7KGFfDWfGqjaXi+RxWq4MlPgjRF/UyoDcPmxZ8TDtZ41/BRF0szw/HAuYveiHbHkEPqostOvttek9/t2KR7P+ImfkvDxiVcwE2xHkprZh79txmkFFKIGhTu8RsGTmZ4fJmzSkqs5hKGcTzKr4HYhiEDk/b40i1fXcxf/8eDMx4xEWO9/SuEZ7ZybrgiuZnL8g+hQ/h+NizjRbhH/7eykkarAzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zAZeky6vhf7/TyRWa1iZOyhiv9N1xEa0JdDFnzmSQTfjX6DCE274h5BHGEKzs4IX48oTHvzo/CrZmybNDDUuHCUYPzXtLwK7UdSUY0dUUEtOXQGlGwPoPC3HoCfHMRTYiUhVxTU2aBc5z/fL4z2W/t/Scxq3fz8iPxa/CU3QtHvTQF5h2LlSorwJ7kXZhFMQz083cxe0K1s6qmFT74tiWUkzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMwGXpMur4X+/08kVmtYmTsonYd2MZup4hLCvo+Vy6apRggUFXRiwaqJsd7c+EucaFtT7jzuM2z/yE4JY+3+mSLK9x6koTp2wjkQM4duA+DK8VPShUB7hxqRa/JRAlWy+knQiGFIjtrdv7vADb+xICP1BCerXMgWX4ZLkwNC+kE1taWCmYC+GgruwOsRhldUEuQpk1bDB1iJelz+Eg1xoOGKM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMBl6TLq+F/v9PJFZrWJk7KJIhekM/QVlRv/K9VafEnbwrDD4HrDkZw1L+b/MWSE84OSQHt3f/n3aTGikUWwUNbxg/Ne0vArtR1JRjR1RQS05dAaUbA+g8LcegJ8cxFNiJSFXFNTZoFznP98vjPZb+39JzGrd/PyI/Fr8JTdC0e9O+ZRJ0w7jfPDmJzOMRtWkHDfUxUTAlCg1WWZ0veQsn5TOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zAZeky6vhf7/TyRWa1iZOyiQnsKwkY6aZwiZQng4YKd/oKhNRZeGGCzWbbfWYXhCcDc066S+LdMqyxjCpSNmswvbs4otZM3f/EXKeCYPdp9ZB3kFa6368PcWo6QfmrBjegrM4Xt5d2pDM51CUkKBhN4/0pKO7+32+70tdSCd5k7wVjgATrjNuipHgLbBl2kxC7xWNu8WOgNnmTiaHmb66REzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMwGXpMur4X+/08kVmtYmTsotMktRQtWvkH9wIBjIF+jm/mA2FF124VnPMn56Nv0G9EFv9D81lg0OGcZuYaYg4XjGD817S8Cu1HUlGNHVFBLTl0BpRsD6Dwtx6AnxzEU2IlIVcU1NmgXOc/3y+M9lv7f0nMat38/Ij8WvwlN0LR706J/AdUP4L3wi2m/Gi/9qyM7UcmmKQdXOYNsqcu4BNLbM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jM+ZJ0NFHCEt+0z0yb2C/7f/Zk63q9YSfMUVKsrk4iReMc5WymlRwYw+khP+Aio3jrCN4ps3EZ/32d3QNnxJsN6tuzii1kzd/8Rcp4Jg92n1kHeQVrrfrw9xajpB+asGN6Cszhe3l3akMznUJSQoGE3j/Sko7v7fb7vS11IJ3mTvCbkJz6Jhm/VbqQCWmaNuUiCcRjeYT5WF6tgBQ7IQZvOjOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zPmSdDRRwhLftM9Mm9gv+39WqaBcrx1RQ4fnN2LMP4rmI0Rf1MqA3D5sWfEw7WeNf84Yy42rXA2iGzcQ/WYkqjWqLLTr7bXpPf7dikez/iJn5Lw8YlXMBNsR5Ka2Ye/bcZpBRSiBoU7vEbBk5meHyZs0pKrOYShnE8yq+B2IYhA5P2+NItX13MX//HgzMeMRFjvf0rhGe2cm64IrmZy/IPoUP4fjYs40W4R/+3spJGqwM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMz5knQ0UcIS37TPTJvYL/t/zERb7RRIQRfP0b2czNlXLl+gwhNu+IeQRxhCs7OCF+OE/+M0qARK9VT/d6XtTR//GD817S8Cu1HUlGNHVFBLTl0BpRsD6Dwtx6AnxzEU2IlIVcU1NmgXOc/3y+M9lv7f0nMat38/Ij8WvwlN0LR700BeYdi5UqK8Ce5F2YRTEM9PN3MXtCtbOqphU++LYllJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jM+ZJ0NFHCEt+0z0yb2C/7fz8kPahX2B8fQTtc0HUzfcIAFC4CkMYJzxkTgq/GLLsUU+487jNs/8hOCWPt/pkiyvcepKE6dsI5EDOHbgPgyvFT0oVAe4cakWvyUQJVsvpJ0IhhSI7a3b+7wA2/sSAj9QQnq1zIFl+GS5MDQvpBNbWlgpmAvhoK7sDrEYZXVBLkKZNWwwdYiXpc/hINcaDhijOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zPmSdDRRwhLftM9Mm9gv+3+4M5o+IDhaFjBrueFNBohkKww+B6w5GcNS/m/zFkhPOJKfh31Gf0CR460jwCLZjYQYPzXtLwK7UdSUY0dUUEtOXQGlGwPoPC3HoCfHMRTYiUhVxTU2aBc5z/fL4z2W/t/Scxq3fz8iPxa/CU3QtHvTvmUSdMO43zw5iczjEbVpBw31MVEwJQoNVlmdL3kLJ+UzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMz5knQ0UcIS37TPTJvYL/t/XxgmZ9p0VJkAumS5NoWRm6CoTUWXhhgs1m231mF4QnCHYxrIawbuYSWWKh8kNnM627OKLWTN3/xFyngmD3afWQd5BWut+vD3FqOkH5qwY3oKzOF7eXdqQzOdQlJCgYTeP9KSju/t9vu9LXUgneZO8FY4AE64zboqR4C2wZdpMQu8VjbvFjoDZ5k4mh5m+ukRM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jM+ZJ0NFHCEt+0z0yb2C/7f9kz27D3k1raqvTje+ypZxX5gNhRdduFZzzJ+ejb9BvRxparCrk1UsywEgspG5ZE/hg/Ne0vArtR1JRjR1RQS05dAaUbA+g8LcegJ8cxFNiJSFXFNTZoFznP98vjPZb+39JzGrd/PyI/Fr8JTdC0e9OifwHVD+C98Itpvxov/asjO1HJpikHVzmDbKnLuATS2zOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zFOCBxi8Vi7V2QFIsQIJA2NQnPEiNdaqmKLS3vM7CuavHOVsppUcGMPpIT/gIqN46wjeKbNxGf99nd0DZ8SbDerbs4otZM3f/EXKeCYPdp9ZB3kFa6368PcWo6QfmrBjegrM4Xt5d2pDM51CUkKBhN4/0pKO7+32+70tdSCd5k7wm5Cc+iYZv1W6kAlpmjblIgnEY3mE+VherYAUOyEGbzozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMxTggcYvFYu1dkBSLECCQNjpZyVj1GXCVOGBYt0VDxMBSNEX9TKgNw+bFnxMO1njX/OGMuNq1wNohs3EP1mJKo1qiy06+216T3+3YpHs/4iZ+S8PGJVzATbEeSmtmHv23GaQUUogaFO7xGwZOZnh8mbNKSqzmEoZxPMqvgdiGIQOT9vjSLV9dzF//x4MzHjERY739K4RntnJuuCK5mcvyD6FD+H42LONFuEf/t7KSRqsDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMU4IHGLxWLtXZAUixAgkDY39gr8YsjIfeVJU+0ZL3Pk5foMITbviHkEcYQrOzghfjhP/jNKgESvVU/3el7U0f/xg/Ne0vArtR1JRjR1RQS05dAaUbA+g8LcegJ8cxFNiJSFXFNTZoFznP98vjPZb+39JzGrd/PyI/Fr8JTdC0e9NAXmHYuVKivAnuRdmEUxDPTzdzF7QrWzqqYVPvi2JZSTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zFOCBxi8Vi7V2QFIsQIJA2Nf0ODYzPpTZnlWlg+nabu2ABQuApDGCc8ZE4Kvxiy7FFPuPO4zbP/ITglj7f6ZIsr3HqShOnbCORAzh24D4MrxU9KFQHuHGpFr8lECVbL6SdCIYUiO2t2/u8ANv7EgI/UEJ6tcyBZfhkuTA0L6QTW1pYKZgL4aCu7A6xGGV1QS5CmTVsMHWIl6XP4SDXGg4YozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMxTggcYvFYu1dkBSLECCQNj4nccybQl//C3K3Eec2xeZysMPgesORnDUv5v8xZITziSn4d9Rn9AkeOtI8Ai2Y2EGD817S8Cu1HUlGNHVFBLTl0BpRsD6Dwtx6AnxzEU2IlIVcU1NmgXOc/3y+M9lv7f0nMat38/Ij8WvwlN0LR7075lEnTDuN88OYnM4xG1aQcN9TFRMCUKDVZZnS95CyflM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMU4IHGLxWLtXZAUixAgkDYzVx8J0lJK/0itv378W00RCgqE1Fl4YYLNZtt9ZheEJwh2MayGsG7mElliofJDZzOtuzii1kzd/8Rcp4Jg92n1kHeQVrrfrw9xajpB+asGN6Cszhe3l3akMznUJSQoGE3j/Sko7v7fb7vS11IJ3mTvBWOABOuM26KkeAtsGXaTELvFY27xY6A2eZOJoeZvrpETOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zFOCBxi8Vi7V2QFIsQIJA2MWPgj09eJQ7Dm2m/xcuKDa+YDYUXXbhWc8yfno2/Qb0caWqwq5NVLMsBILKRuWRP4YPzXtLwK7UdSUY0dUUEtOXQGlGwPoPC3HoCfHMRTYiUhVxTU2aBc5z/fL4z2W/t/Scxq3fz8iPxa/CU3QtHvTon8B1Q/gvfCLab8aL/2rIztRyaYpB1c5g2ypy7gE0tszkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMxzrNgZ99TAKyqN+IJI8yYrtpvKEIbYj4DJKFtOddIxxRzlbKaVHBjD6SE/4CKjeOsI3imzcRn/fZ3dA2fEmw3q27OKLWTN3/xFyngmD3afWQd5BWut+vD3FqOkH5qwY3oKzOF7eXdqQzOdQlJCgYTeP9KSju/t9vu9LXUgneZO8JuQnPomGb9VupAJaZo25SIJxGN5hPlYXq2AFDshBm86M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMc6zYGffUwCsqjfiCSPMmK9T8il1yr0J7ebhLQp8u6yYjRF/UyoDcPmxZ8TDtZ41/zhjLjatcDaIbNxD9ZiSqNaostOvttek9/t2KR7P+ImfkvDxiVcwE2xHkprZh79txmkFFKIGhTu8RsGTmZ4fJmzSkqs5hKGcTzKr4HYhiEDk/b40i1fXcxf/8eDMx4xEWO9/SuEZ7ZybrgiuZnL8g+hQ/h+NizjRbhH/7eykkarAzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zHOs2Bn31MArKo34gkjzJiuVxeLEtg6c/kIhdk0Jvrf4X6DCE274h5BHGEKzs4IX44T/4zSoBEr1VP93pe1NH/8YPzXtLwK7UdSUY0dUUEtOXQGlGwPoPC3HoCfHMRTYiUhVxTU2aBc5z/fL4z2W/t/Scxq3fz8iPxa/CU3QtHv

    Licensing Data-->
    Software Licensing service is not running.

    HWID Data-->
    HWID Hash Current: OAAAAAEAAwABAAIAAgABAAAAAwABAAEAJJRiPWCIYuyggEaDyF5k3ILPprDy9JwJ3DasVkddKoU=

    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   PTLTD     APIC 
      FACP   T0SQCI  TOSQCI00
      HPET   TOSQCI  TOSQCI00
      BOOT   PTLTD   $SBFTBL$
      MCFG   TOSQCI  TOSQCI00
      SLIC   TOSQCI  TOSQCI00
      SSDT   SataRe  SataAhci
      SSDT   SataRe  SataAhci
      SSDT   SataRe  SataAhci
      SSDT   SataRe  SataAhci

     

    Monday, May 4, 2009 6:56 PM
  • Hello nienke123,

    The core of your issue centers on the line in your Diagnostic Report that reads:

    File Scan Data-->
    File Mismatch: C:\Windows\system32\Slsvc.exe[6.0.6000.16509]
    File Mismatch: C:\Windows\system32\drivers\Spsys.sys[6.0.5840.16389]
    File Mismatch: C:\Windows\system32\Slcext.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\advapi32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\kernel32.dll[6.0.6000.16820]
    File Mismatch: C:\Windows\system32\rpcrt4.dll[6.0.6000.16525]
    File Mismatch: C:\Windows\system32\authz.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\msvcrt.dll[7.0.6000.16386]
    File Mismatch: C:\Windows\system32\samlib.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\ntdsapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\dnsapi.dll[6.0.6000.16615]
    File Mismatch: C:\Windows\system32\ws2_32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\nsi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\user32.dll[6.0.6000.16438]
    File Mismatch: C:\Windows\system32\gdi32.dll[6.0.6000.16766]
    File Mismatch: C:\Windows\system32\msimg32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\powrprof.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\setupapi.dll[6.0.6000.16609]
    File Mismatch: C:\Windows\system32\oleaut32.dll[6.0.6000.16609]
    File Mismatch: C:\Windows\system32\ole32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\shell32.dll[6.0.6000.16774]
    File Mismatch: C:\Windows\system32\shlwapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\version.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\winmm.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\oleacc.dll[4.2.5406.0]
    File Mismatch: C:\Windows\system32\mmdevapi.dll[6.0.6000.20564]
    File Mismatch: C:\Windows\system32\wtsapi32.dll[6.0.6000.16553]
    File Mismatch: C:\Windows\system32\regapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\crypt32.dll[6.0.6000.16425]
    File Mismatch: C:\Windows\system32\msasn1.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\userenv.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\secur32.dll[6.0.6000.16820]
    File Mismatch: C:\Windows\system32\netapi32.dll[6.0.6000.16764]
    File Mismatch: C:\Windows\system32\psapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\netrap.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\wldap32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\winbrand.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\iphlpapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\dhcpcsvc.dll[6.0.6000.16512]
    File Mismatch: C:\Windows\system32\winnsi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\dhcpcsvc6.dll[6.0.6000.16512]
    File Mismatch: C:\Windows\system32\gpapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\slc.dll[6.0.6000.16509]
    File Mismatch: C:\Windows\system32\gpsvc.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\sysntfy.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\winsta.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\nlaapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\ncrypt.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\bcrypt.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\mpr.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\credui.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\cryptui.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\wintrust.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\imagehlp.dll[6.0.6000.16470]
    File Mismatch: C:\Windows\system32\dbghelp.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\mssign32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\wininet.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\normaliz.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\iertutil.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\tapi32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\rtutils.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\rasapi32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\rasman.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\rasdlg.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\mprapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\activeds.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\adsldpc.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\atl.dll[3.5.2284.0]
    File Mismatch: C:\Windows\system32\certcli.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\winscard.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\netplwiz.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\urlmon.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\propsys.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\xmllite.dll[1.1.1002.0]
    File Mismatch: C:\Windows\system32\mlang.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\advpack.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\apphelp.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\msiltcfg.dll[4.0.6000.16386]
    File Mismatch: C:\Windows\system32\shunimpl.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\devmgr.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\newdev.dll[6.0.5054.0]
    File Mismatch: C:\Windows\system32\dwmapi.dll[6.0.6000.20530]
    File Mismatch: C:\Windows\system32\winspool.drv[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\cscapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\uxtheme.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\windowscodecs.dll[6.0.6000.16740]
    File Mismatch: C:\Windows\system32\ntshrui.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\feclient.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\shdocvw.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\browseui.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\imm32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\msctf.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\duser.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\winsxs\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6000.16386_none_9ea0ac9ec96e7127\gdiplus.dll[5.2.6000.16386]
    File Mismatch: C:\Windows\system32\msrating.dll[7.0.6000.16386]
    File Mismatch: C:\Windows\system32\ieframe.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\msi.dll[4.0.6000.16386]
    File Mismatch: C:\Windows\system32\mshtml.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\msls31.dll[3.10.349.0]
    File Mismatch: C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.6000.16386_none_87e0cb09378714f1\comctl32.dll[5.82.6000.16386]
    File Mismatch: C:\Windows\system32\comdlg32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\printui.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\cfgmgr32.dll[6.0.6000.16609]
    File Mismatch: C:\Windows\system32\puiapi.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\hlink.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\imgutil.dll[7.0.6000.16386]
    File Mismatch: C:\Windows\system32\usp10.dll[1.626.6000.16386]
    File Mismatch: C:\Windows\system32\inetcomm.dll[6.0.6000.16669]
    File Mismatch: C:\Windows\system32\msoert2.dll[6.0.6000.16480]
    File Mismatch: C:\Windows\system32\ieui.dll[7.0.6000.16830]
    File Mismatch: C:\Windows\system32\efsadu.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\mfc42u.dll[6.6.8063.0]
    File Mismatch: C:\Windows\system32\odbc32.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\oledlg.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\linkinfo.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\query.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\clbcatq.dll[2001.12.6930.16386]
    File Mismatch: C:\Windows\system32\cabinet.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\scecli.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\w32topl.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\rpchttp.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\winhttp.dll[6.0.6000.16786]
    File Mismatch: C:\Windows\system32\fwpuclnt.dll[6.0.6000.16386]
    File Mismatch: C:\Windows\system32\ktmw32.dll[6.0.6000.16386]

     

    This means the file has been Tampered, Modified or has become Corrupt. Vista see this as an attack to bypass it's Licensing security.

    To resolve the issue, you need to either repair or replace the file with a known-good one (of the proper file version)

     

    First try repairing Windows using System Restore:

    1)    Reboot Vista into Safe Mode

    2)    Go to Control Panel

    3)    On the left hand side of the Control Panel window, Click on "Classic View"

    4)    Double-click "Backup and Restore Center"

    5)    On the left hand side of the window, click "Repair Windows using system restore"

    6)    Select "Choose Different Restore Point", Put a check in the box that says "Show restore points older than 5 days", select the restore point that corresponds to the date Before you first noticed the issue.

    7)    Click the "Next" button.

    8)    Reboot back into Normal mode

    9)    Vista should no longer be in Reduced Functionality mode

     

    If that doesn't work, we'll try doing a System Scan. The scan will look for bad Vista files and will attempt to repair them, if possible.

    1)    Login to Vista in Normal Mode (not safe mode)

    2)    Launch an Internet Browser

    3)    Type: %windir%\system32\ in the browser's address field

    4)    Scroll down till you find the file cmd.exe

    5)    Right-click the file and select 'Run as Administrator'

    6)    In the CMD window, type: sfc /scannow

    7)    Reboot twice and see if that resolves the issue.

    If neither of these sets of steps resolves the issue, my only other suggestions would be either to contact Vista support at http://support.microsoft.com or reinstall Vista.

    Thank you,
    Darin MS

    Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please vote the post as Helpful. This will help us showcase the threads that best help our customers.
    Monday, May 4, 2009 7:52 PM