locked
Validation issues RRS feed

  • Question

  • Hello,

    My laptop is a Toshiba with Vista home premium edition installed. I use CCleaner, Spyware Doctor, AVG and Avira software for security while my firewall is usually on low so that I can play on XBOX live through my router. I have not installed any new software or hardware outside of what is installed through automatic updates and today I got an error message relating to a validation issue, saying "unauthorized change to windows you will no longer receive notifications."

    I followed instructions on previous forum postings, running the WinDirStat analysis to see what software or hardware updates may be causing the problem and the only updates installed in the last 6 days were definition updates for windows defender KB915597 Definition 1. Is this causing problems on Vista?

    I have run the validation checks on your website and installed the firefox plugins, but to no avail. Are there any other checks I can do to see what may be causing this problem? I ran the MGA Diagnostic test and the following came back:

    Diagnostic Report (1.9.0011.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50

    Cached Validation Code: N/A, hr = 0xc004d401
    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.6001.2.00010300.1.0.003
    ID: {0ED1D464-02AD-44E5-8E9D-7F201A973BA8}(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: 6001.vistasp1_gdr.090805-0102
    TTS Error: K:20100111142053599-M:20100111141656317-
    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
    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: 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 8.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>{0ED1D464-02AD-44E5-8E9D-7F201A973BA8}</UGUID><Version>1.9.0011.0</Version><OS>6.0.6001.2.00010300.1.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-RJ34F</PKey><PID>89578-OEM-7332157-00237</PID><PIDType>2</PIDType><SID>S-1-5-21-3863870051-1747408505-848335923</SID><SYSTEM><Manufacturer>TOSHIBA</Manufacturer><Model>EQUIUM A200</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies LTD</Manufacturer><Version>1.60    </Version><SMBIOSVersion major="2" minor="4"/><Date>20071005000000.000000+000</Date></BIOS><HWID>56313507018400FA</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><OEMID>TOSINV</OEMID><OEMTableID>TOSINV00</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAALkJFAAAAAAAYWECAOiApqnEYwS7yJLKARhy9171jCizkdIEkQaJZ64b//9A2EQDKiIuQ6iJvfFozfg2FxeuJ/JMAjXOgjB+aTxmIhnxJS6W2ohsCzadr0J5O281QgMo6Qd67lE3/GW0BtU6zyz3v9Z2MrIHa9x3W3cNP6YJJRzZ3sGPZMdauCpWgA9xqCKT2pyzU4ikmVXcUHxhcf38akJWjrTFmdio3G4MbsZdJFBl6ID8Z6PgzOE3ppKHhVqCwkvaDzBS7RRf801+h+MsTFkRlJ2ZAjRAiDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

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

    HWID Data-->
    HWID Hash Current: OAAAAAEABAABAAIAAQABAAAAAwABAAEAJJSiYNS/JqnkM0aDBgymiV6yulvy9Dr9ANasVnW6KoU=

    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            INTEL         CRESTLNE
      FACP            TOSINV        CRESTLNE
      HPET            INTEL         CRESTLNE
      BOOT            TOSINV        $SBFTBL$
      MCFG            INTEL         CRESTLNE
      TCPA            Intel          CRESTLN
      TMOR            TOSINV               
      APIC            INTEL         CRESTLNE
      SLIC            TOSINV        TOSINV00
      SSDT            SataRe        SataAhci
      SSDT            SataRe        SataAhci
      SSDT            SataRe        SataAhci
      SSDT            SataRe        SataAhci


    I tried the following steps without success: 1. Click on the Start button and in the Start Search box type in:  services.msc

    2. Press the Enter key on your keyboard.

    3. The Services window should now open.

    4. Scroll down to Software Licensing , then right-click on it and select Properties .

    5. Under the General tab, click on the Stop button.

    6. Set the Startup Type to Automatic , then click Apply .

    7. Next, under Service Status , click on the Start button.

    8. Last, restart your computer.  

    The manual steps the force start didn't work either. Please help!!

    Stephen

    Monday, January 11, 2010 3:45 PM

Answers

  • Hello Stewhatcott,

      First off, there is no point attempting to restart the Solftware Licensing Service.  The main purpose of that Service is to detect Tampers.  When it detects a Tamper, the Service is designed to Stop.  When the Tamper is resolved, the Service will restart automaticly.

     Almost all Non-Genuine issues look alike but have many different causes and many resolution steps so I have no idea what steps you have already tried.  The below is specific to the issue your Vista is experiencing.

    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         01         11            1416                     56317-

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

    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 01/11/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 01/10/2010, 01/09/2010 and 01/08/2010  (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

    Monday, January 11, 2010 9:51 PM

All replies

  • Hello Stewhatcott,

      First off, there is no point attempting to restart the Solftware Licensing Service.  The main purpose of that Service is to detect Tampers.  When it detects a Tamper, the Service is designed to Stop.  When the Tamper is resolved, the Service will restart automaticly.

     Almost all Non-Genuine issues look alike but have many different causes and many resolution steps so I have no idea what steps you have already tried.  The below is specific to the issue your Vista is experiencing.

    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         01         11            1416                     56317-

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

    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 01/11/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 01/10/2010, 01/09/2010 and 01/08/2010  (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

    Monday, January 11, 2010 9:51 PM
  • Hello Darin,

    Thanks for getting back to me. I tried the above scan with onecare and got back a few registry fixes but no virus found. There were 6 Errors:
    File Type Associations (skipped by User): HKCU\SoftwareMicrosoft\Windows\CurrentVersion\Explorer\FileExts\.xht\  and 5 more with .wms .wpl .xhtml .wmd and .wmz extensions at the end.  I sent the report to Microsoft but have not contacted the support team yet.

    No other virus scan has come up with a virus although I did get an alert from Avira saying there was malware found on 09/01/2010: Virus or unwanted program 'HTML/Infected.WebPage.Gen [virus]'
    detected in file 'C:\Users\Catherine\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\NXAZQOYZ\content_main[1].htm.
    Action performed: Deny access

    The same program alerted me to a TR/Dropper.Gen Trojan back in November whose source was Windows Installer (C:\Windows\Installer\MSI9F9.tmp) but after quarantineing it never seemed to raise its head...

    I accepted an automatic Java update on 11/01/2010 which is the only installation in the past few weeks so could it be this that has affected the validation? The only other automatic updates were for my security software (Avira, AVG and SPyware Doctor)

    If any of the above problems may be to blame, could you advise me on how to fix?

    Thanks again for your help.

    Stephen


    Tuesday, January 12, 2010 1:59 PM
  • Hi Stephen,

      I don't believe the Java Update would be to blame (it's a major program used by allot of people and if it caused an 'In Memory Mod-Auth' non-genuine problems, I would have seen allot of people experiencing it...you are currently only Vista, in this forum, experiencing an In Memory Mod-Auth).

      The File Type Association problem is unlikly to be to blame because file type associations are just setting that tell windows which files can be opened by what programs.  In Memory Mod-Auth are only caused by programs actively modifing protected Windows files in system memory.

      The Malware and Trojan could very well cause this, however, as I said, the program (malware and trojans and viruses are programs) must be present (currently on the computer) and running to cause the In Memory Mod-Auth.  It could be that past Malware or that past Trojan weren't removed and could be causing the problem.

      As I mentioned above, now days, Malware  is almost always the cause of this type of issue.  when Vista first came out there were a number of legitamate programs that weren't compatible with Vista that if they were installed, this issue would occure. But Vista has been around for some time now and all program writers know the correct way to write a program for Vista so legit programs almost never do this anymore.  So, unless you have a program installed that hasn't been updated since Vista was release, this issue is most likely caused by Malware.  (note: when I say Malware, I mean all the bad stuff like Viruses, Trojans, keyloggers, and such).

      To get help with any sort of Malware problem, the link I gave to PC Safety are your best resource.

    Sorry I couldn't be more help,
    Darin MS 

     
    Tuesday, January 12, 2010 10:32 PM