locked
Invalid License RRS feed

  • Question

  • I did the diagnostic it says I do not have a valid license I just renstsalled the operation systom from the hard drive I brough this HP computer new two years ago.

    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: *****-*****-27HYQ-XTKW2-WQD8Q
    Windows Product Key Hash: U8YEZzymoD4DMyaMb32rPrNIS90=
    Windows Product ID: 89583-OEM-7332157-00061
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6001.2.00010300.1.0.003
    ID: {0FDE26C5-B3F9-4D2C-B4ED-199CBA4F1422}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000009
    Build lab: 6001.vistasp1_gdr.100608-0458
    TTS Error: M:20100929092004523-
    Validation Diagnostic:
    Resolution Status: N/A

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

    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: 100 Genuine
    Microsoft Office Home and Student 2007 - 100 Genuine
    Microsoft Office Small Business 2007 - 100 Genuine
    OGA Version: Registered, 2.0.48.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_672A8F41-307-80004005_672A8F41-349-80004005_672A8F41-244-80004005_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\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>{0FDE26C5-B3F9-4D2C-B4ED-199CBA4F1422}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6001.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-WQD8Q</PKey><PID>89583-OEM-7332157-00061</PID><PIDType>2</PIDType><SID>S-1-5-21-2245381031-2291460010-3039631442</SID><SYSTEM><Manufacturer>HP-Pavilion</Manufacturer><Model>KQ437AA-ABA IQ506</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>5.05   </Version><SMBIOSVersion major="2" minor="5"/><Date>20080626000000.000000+000</Date></BIOS><HWID>76323507018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-CPC</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>2D76EF6AA145722</Val><Hash>mCTuTmMP0ev8cuFiwmoSE7Frp2k=</Hash><Pid>81602-913-0533712-68048</Pid><PidType>1</PidType></Product><Product GUID="{91120000-00CA-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Small Business 2007</Name><Ver>12</Ver><Val>57C4771AA54B70E</Val><Hash>eZJ4rSvUOZqQuwDKCmqPjSS9LhI=</Hash><Pid>81606-903-2575333-64733</Pid><PidType>1</PidType></Product></Products><Applications><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="A1" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAACAAAABJRAAAAAAAAYWECAAAAAABoo0+exV/LARhy9171jCizkdIEkQaJZ64FOCvhlOd2Ie05vclIGqYESlNUdMuXsqeszUb7dj81bid7IPmIgITKmLNv1wD2WLYhYmE5eBVFpeb6ouNkVzkA4DkkCd2V0+w0qMw9NW1lJIqaMVS50xsGhTiu2v3HTjLlzsauw1rN6YPtvvhlgmsOntaE+R2pndVdwiQf9u1zaeZn0+XwJIK7QecSF/kJ+BROU5kpI4Km83cHZMn5BmY2HdKPD8tNYkwP34K9Ekif+jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeuu5JOlyTUDAfkAcs6hVgZi4Ar98lVv9/Z80E7PgqW2LwneyD5iICEypizb9cA9li2+NvJMTc11EUhS1N7RoTKPOA5JAndldPsNKjMPTVtZSSKmjFUudMbBoU4rtr9x04y5c7GrsNazemD7b74ZYJrDp7WhPkdqZ3VXcIkH/btc2nmZ9Pl8CSCu0HnEhf5CfgUTlOZKSOCpvN3B2TJ+QZmNh3Sjw/LTWJMD9+CvRJIn/ozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM

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

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: NgAAAAIAAgABAAEAAQABAAAABAABAAEA6GFgk3oe1YeCW/Y31opaMvL0yASnOu7A3nasViqF

    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   HPQOEM  SLIC-CPC
      FACP   HPQOEM  SLIC-CPC
      HPET   HPQOEM  SLIC-CPC
      MCFG   HPQOEM  SLIC-CPC
      OEMB   HPQOEM  SLIC-CPC
      GSCI   HPQOEM  SLIC-CPC
      SLIC   HPQOEM  SLIC-CPC
      SSDT   HPQOEM  SLIC-CPC

     

    Wednesday, September 29, 2010 1:46 PM

Answers

  • Hello

    Unfortunately, David is incorrect.


    The Software Licensing Service has stopped because Vista is experiencing a Tamper.  The Software Licensing Service is designed to stop when any type of Tamper is detected.

    We know a Tamper is occurring because of the line in the Diagnostic Report that says:

    "TTS Error: M:20100929092004523-"

    TTS means Tamper Time Stamp and the M in front of the long number stands for "Mod-Auth" which is the type of tamper that is occurring. The long number is the actual time stamp that tells us the last time the tamper was detected.

    Below is information that may help you resolve the issue

    --------------------------------

     

    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       09        29           0920                04523-


    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 09/29
    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 02/26/2008"
    7)    Look for any program that shows "Application Install" in the 'Activity' column.
    8)    Since the process that detects Tampers runs randomly, it can take up to 3 days for the process to detect the tamper and set Vista to a Tamper State. Because of this, please repeat steps 5) thru 7) for the dates 09/28, 09/27 and 09/26 (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 Wednesday, October 13, 2010 8:09 PM
    Wednesday, October 13, 2010 8:09 PM

All replies

  • Hello, BI-LEE-GA

    Looking at the report, it looks like the Software Licensing Service has stopped.

    Try to restart the service using the 'Service Restart' steps, below. If the service won't restart, you will receive an error.

    (If you have access to the Start button):

    1.    Click the Start button

    2.    Type: cmd in the Start Search field

    3.    At the top the Start window, you will see cmd.exe

    4.    Right Click cmd.exe and select Run as Administrator

    5.    Type: net start slsvc

    (If you do not have access to the Start button):

    1.      Click the option that launches an Internet Browser

    2.      A Browser will open, type: %windir%\system32 into the address field

    3.      Find the file cmd.exe

    4.      Right Click on the cmd.exe and select Run as Administrator

    5.      Type: net start slsvc

    After the service starts, try validating once more.

    See the following if you get an error starting the service.

    A)     If the error message is "System Error 3, The system cannot find the path specified." or "System Error 2, The system cannot find the file specified": Go to the main Vista Validation forum page http://social.microsoft.com/Forums/en-US/genuinevista/threads/, look in the announcement section and follow the steps found in thread "Fix for ‘Software Licensing service Has Stopped’ on some Vista 64bit systems"

    B)     If you receive any other error (System Error 5, System Error 57346 or System Error 54273): These occur as a result of massive file corruption. Usual causes are either Malware Infection or failing Hard Drive. The only resolution we can suggest is reinstall Vista.

    C)     If you receive no System Error and the Service start but then stops almost immediately: Something is apparently actively stopping the service. Most likely caused by some other dependent Windows Service or possibly a Malware infection.


    David
    Microsoft Answers Support Engineer
    Visit our Microsoft Answers Feedback Forum and let us know what you think.
    Thursday, September 30, 2010 12:01 AM
    Moderator
  • Hello

    Unfortunately, David is incorrect.


    The Software Licensing Service has stopped because Vista is experiencing a Tamper.  The Software Licensing Service is designed to stop when any type of Tamper is detected.

    We know a Tamper is occurring because of the line in the Diagnostic Report that says:

    "TTS Error: M:20100929092004523-"

    TTS means Tamper Time Stamp and the M in front of the long number stands for "Mod-Auth" which is the type of tamper that is occurring. The long number is the actual time stamp that tells us the last time the tamper was detected.

    Below is information that may help you resolve the issue

    --------------------------------

     

    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       09        29           0920                04523-


    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 09/29
    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 02/26/2008"
    7)    Look for any program that shows "Application Install" in the 'Activity' column.
    8)    Since the process that detects Tampers runs randomly, it can take up to 3 days for the process to detect the tamper and set Vista to a Tamper State. Because of this, please repeat steps 5) thru 7) for the dates 09/28, 09/27 and 09/26 (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 Wednesday, October 13, 2010 8:09 PM
    Wednesday, October 13, 2010 8:09 PM