WINDOWS VALIDATION PROBLEM

All replies

• 

  

  0

  Sign in to vote

  "MAG2011" wrote in message news:b4cddd9a-39cf-47e1-ad0f-ae7fa1ffb187...

  HERE IS THE DATA:

  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
  Windows OS version: 6.0.6000.2.00010300.0.0.003
  
  
  Spsys.log Content: 0x800700EA
  
  Licensing Data-->
  C:\Windows\system32\slmgr.vbs(291, 5) (null): 0xC004D401
  
  

  
  

  there's a rare error message there (Spsys.log Content: 0x800700EA) which I have no idea about - but the other one is...

  This error is usually the result of corruption in the Licensing store - and the solution is to recreate the store.
  Please try the below steps to recreate the Store files.  This may resolve the issue.
   
  1) Open an Internet Browser window.
  2) Type: %windir%\system32 into the browser address bar.
  3) Find the file CMD.exe
  4) Right-Click on CMD.exe and select 'Run as Administrator'
  5) Type: net stop slsvc  (it may ask you if you are sure, select yes)
  6) Type: cd %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareLicensing
  7) Type: rename tokens.dat tokens.bar
  8) Type: cd %windir%\system32
  9) Type: net start slsvc
  10) Type: cscript slmgr.vbs -rilc (It may take a long time for this to complete, please be patient)
  11) Restart your computer twice.
  12) You may be required to enter the Product Key and/or Activate. Be sure to use the Product key on the sticker on the side or bottom of the PC (some laptops may have the sticker located in the battery compartment) To Activate, please use the Activate by Phone option.
   
   
  Once complete, please post back with a new MGADiag report

  
  --
  
  

  ---

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

  Tuesday, August 31, 2010 8:48 PM

  Moderator
• 

  

  0

  Sign in to vote

  "Noel D Paton" wrote in message news:b4cde365-7a87-4046-bf0e-d81b0fe2f741...

  "MAG2011" wrote in message news:b4cddd9a-39cf-47e1-ad0f-ae7fa1ffb187...

  HERE IS THE DATA:

  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
  Windows OS version: 6.0.6000.2.00010300.0.0.003
  
  
  Spsys.log Content: 0x800700EA
  
  Licensing Data-->
  C:\Windows\system32\slmgr.vbs(291, 5) (null): 0xC004D401
  
  

  
  

  there's a rare error message there (Spsys.log Content: 0x800700EA) which I have no idea about - but the other one is...

  This error is usually the result of corruption in the Licensing store - and the solution is to recreate the store.
  Please try the below steps to recreate the Store files.  This may resolve the issue.
   
  1) Open an Internet Browser window.
  2) Type: %windir%\system32 into the browser address bar.
  3) Find the file CMD.exe
  4) Right-Click on CMD.exe and select 'Run as Administrator'
  5) Type: net stop slsvc  (it may ask you if you are sure, select yes)
  6) Type: cd %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareLicensing
  7) Type: rename tokens.dat tokens.bar
  8) Type: cd %windir%\system32
  9) Type: net start slsvc
  10) Type: cscript slmgr.vbs -rilc (It may take a long time for this to complete, please be patient)
  11) Restart your computer twice.
  12) You may be required to enter the Product Key and/or Activate. Be sure to use the Product key on the sticker on the side or bottom of the PC (some laptops may have the sticker located in the battery compartment) To Activate, please use the Activate by Phone option.
   
   
  Once complete, please post back with a new MGADiag report

  
  --
  
  

  ---

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

  
  

  As an addendum ....

  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:20100831125100950 This is the Tamper Time Stamp and it breaks down like this:

   

      (year)  (month) (day) (time in 24format) (millisecond)
  M:2010         08      31           1125                     00950-

   

   

   

  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)[v2] 

   

  
  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 31 Aug 

   

  6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 31 August "

   

  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 28-31 August  (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

   

   

  
  --
  
  

  ---

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

  • Marked as answer by Darin Smith MS Wednesday, September 1, 2010 9:08 PM
  • Unmarked as answer by MAG2011 Friday, September 3, 2010 1:01 AM
  • Marked as answer by Darin Smith MS Thursday, September 9, 2010 9:23 PM

  Tuesday, August 31, 2010 9:52 PM

  Moderator
• 

  

  0

  Sign in to vote

  Hi,

  I ran the Windows live safety scanner and my vipre antivirus and it cleaned out all of the spyware on my computer. When I ran the system stability report application, the only thing that I could find that I installed was Itunes. So i tried deleting that but the message still appeared. On the first message that you sent me, I tried to recreate the Store files just like you told me but I encountered a problem. When trying to perform step 9, an error occurred and gave me this message: " The software licensing service is starting.

                                                                                                            The software licensing service could not be started.

                                                                                                            A system error has occurred

                                                                                                            System error 54529. The system cannot find message text for message number 0xd501 in the message file for BASE."

  I ran another diagnosis and I thought it might be helpful if I attached a new one:

  Diagnostic Report (1.9.0027.0):
  -----------------------------------------
  Windows Validation Data-->
  Validation Status: Invalid License
  Validation Code: 50
  Cached Online Validation Code: N/A, hr = 0x80070426
  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
  Windows OS version: 6.0.6000.2.00010300.0.0.003
  ID: {6786BB89-9B39-413B-A208-BEDB6FE99000}(3)
  Is Admin: Yes
  TestCab: 0x0
  LegitcheckControl ActiveX: Registered, 1.9.42.0
  Signed By: Microsoft
  Product Name: Windows Vista (TM) Home Premium
  Architecture: 0x00000000
  Build lab: 6000.vista_gdr.070627-1500
  TTS Error: K:20100901180034514-M:20100901084225221-
  Validation Diagnostic:
  Resolution Status: N/A
  
  Vista WgaER Data-->
  ThreatID(s): N/A, hr = 0x80070002
  Version: 6.0.6002.16398
  
  Windows XP 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
  OGAExec.exe Signed By: N/A, hr = 0x80070002
  OGAAddin.dll Signed By: N/A, hr = 0x80070002
  
  OGA Data-->
  Office Status: 109 N/A
  OGA Version: N/A, 0x80070002
  Signed By: N/A, hr = 0x80070002
  Office Diagnostics: 77F760FE-153-80070002_7E90FEE8-175-80070002_B4D0AA8B-604-645_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
  
  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>{6786BB89-9B39-413B-A208-BEDB6FE99000}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6000.2.00010300.0.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-G6MF9</PKey><PID>89578-OEM-7332157-00203</PID><PIDType>2</PIDType><SID>S-1-5-21-4097760166-2955443086-1424922374</SID><SYSTEM><Manufacturer>Sony Corporation</Manufacturer><Model>VGC-LS25E</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies LTD</Manufacturer><Version>R0100W2</Version><SMBIOSVersion major="2" minor="40"/><Date>20061207000000.000000+000</Date></BIOS><HWID>D3303507018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>Sony</OEMID><OEMTableID>VAIO</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> 
  
  Spsys.log Content: 0x800700EA
  
  Licensing Data-->
  Software Licensing service is not running.
  
  Windows Activation Technologies-->
  N/A
  
  HWID Data-->
  HWID Hash Current: OAAAAAEABAABAAEAAQACAAAAAwABAAEAJJRCuqhoxu1cBEjk6k6EUEig8vRKzlZ9IkOgx6xWKoU=
  
  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            Sony        VAIO
    FACP            Sony        VAIO
    HPET            Sony        VAIO
    BOOT            Sony        VAIO
    MCFG            Sony        VAIO
    SLIC            Sony        VAIO
    APIC            Sony        VAIO
    SSDT            Sony        VAIO
    SSDT            Sony        VAIO
    SSDT            Sony        VAIO
  
  
  

  Thursday, September 2, 2010 3:40 AM
• 

  

  0

  Sign in to vote

  Adding to the previous message, at this point I can no longer run my computer in normal mode and have to run it in safe mode. I imagine that the problem is due to the fact that I could not start the software licensing service again. Every time I turn on my computer a message appears: "Windows must be reinstalled to activate. Insert the windows installation DVD or CD into your computer to begin the re-installation process." At the bottom, right-hand corner of the screen, you can see a message that reads: " This copy of windows is not genuine". The only way I can use my computer is by using Safe mode with Networking and your previous instructions cannot be performed under this mode. Your help in this matter would be greatly appreciated.

  Thursday, September 2, 2010 5:17 AM