Vista authentication problem - windows aero?

All replies

• 

  

  0

  Sign in to vote

  "kevans24" wrote in message news:84eacc1b-6699-498a-a999-e14b9b14964a...

  I have never gotten this error and now all of a sudden when I open up a program I continually get a message that talks about windows aero color scheme not being able to be used. I tried to check the validity of my windows to get rid of this message but it wouldn't work and this is the diagnostic report.

   

  Diagnostic Report (1.9.0027.0):
  -----------------------------------------
  Windows Validation Data-->
  Validation Status: Invalid License
  Validation Code: 50
  Cached Online Validation Code: N/A, hr = 0xc004d401
  Windows Product Key: *****-*****-4GV68-6D8JB-G6MF9
  Windows Product Key Hash: Ua+OBZ1y48sKA/bWkfKXiuCrOjY=
  Windows Product ID: 89578-OEM-7332157-00203
  Windows Product ID Type: 2
  Windows License Type: OEM SLP
  

  Licensing Data-->
  C:\Windows\system32\slmgr.vbs(291, 5) Microsoft VBScript runtime error: Permission denied

  
  

  C:\Windows\system32\slmgr.vbs(291, 5) Microsoft VBScript runtime error: Permission denied

  seems to be the cause of the problem -

   

  This may be caused by the Software Licensing Service being turned off - pleas check that it is set to Automatic, and is started.

  To do this:-

   

  Click on Start

   

  in the Search box type

   

  SERVICES.MSC

   

  and hit the Enter key

   

  The Serves control panel will come up - look for the Software Licensing Service there, and right-click on it, and select Properties. Check that the Startup type is set to Automatic, then click on the Start Button and wait for the service to start - then click OK out, and close the panel.

  Go to the Validation site and run the Validation. http://www.microsoft.com/genuine/ProgramInfo.aspx  with any luck that will validate Windows

   

  If that doesn't work - or SLS is already running - then do you have Norton Anti-Virus installed (or any other form of script blocking)? - if so turn off the Scripting protection, and try validating again.

   

  HTH

  --
   

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

  Friday, June 4, 2010 7:27 AM

  Moderator
• 

  

  0

  Sign in to vote

  The startup type was set to automatic but I was still unable to validate windows. I do have mcafee installed but I am unaware of how to disable script protection. I turned off the firewall to while trying to validate and that did not work.

  Friday, June 4, 2010 8:54 AM
• 

  

  0

  Sign in to vote

  "kevans24" wrote in message news:9bd6bee3-f161-4e90-9d2d-681f7cdb6fac...

  The startup type was set to automatic but I was still unable to validate windows. I do have mcafee installed but I am unaware of how to disable script protection. I turned off the firewall to while trying to validate and that did not work.

  
  

  Something is preventing the script from actually running - whether the script itself is locked in some way so that it can't be opened for running, I don't know -  look here for some advice on script blocking in McAfee  8

  http://antivirus.nih.gov/information/install_vscan80.asp

  "ScriptScan is enabled by default. It is recommended that this feature be disabled by unchecking the Enable ScriptScan box and selecting apply."

   

  ...and here

  http://support.maximizer.com/scripts/support.cfg/php.exe/enduser/std_adp.php?p_refno=050527-000000#mcafee

   

  HTH

  
  --
   

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

  Friday, June 4, 2010 1:20 PM

  Moderator
• 

  

  0

  Sign in to vote

  Hello kevans24,

  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:2010       05      30         1651                 21909-

  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/30

  6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 05/30/2010"

  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 05/29, 05/28 and 05/23  (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

  • Marked as answer by Darin Smith MS Friday, June 4, 2010 7:09 PM

  Friday, June 4, 2010 7:09 PM