none
error with having a invalid license? RRS feed

  • Question

  • I ran the diagnostics and this is what I got. Please help! Thank you!


    Diagnostic Report (1.7.0095.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0xc004d401
    Cached Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-27HYQ-XTKW2-WQD8Q
    Windows Product Key Hash: U8YEZzymoD4DMyaMb32rPrNIS90=
    Windows Product ID: 89578-OEM-7332157-00061
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6000.2.00010300.0.0.003
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {5428FFAE-9227-4433-BAB5-9806BB0EE286}(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.071023-1545
    TTS Error: K:20080924221122683-M:20080925095150364-
    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: 114 Blocked VLK 2
    Microsoft Office Professional Edition 2003 - 114 Blocked VLK 2
    Microsoft Office Home and Student 2007 - 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-282-80041010_025D1FF3-170-80041010_025D1FF3-171-1_025D1FF3-434-80040154_025D1FF3-178-80040154_025D1FF3-179-2_025D1FF3-185-80070002_025D1FF3-199-3

    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>{5428FFAE-9227-4433-BAB5-9806BB0EE286}</UGUID><Version>1.7.0095.0</Version><OS>6.0.6000.2.00010300.0.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-WQD8Q</PKey><PID>89578-OEM-7332157-00061</PID><PIDType>2</PIDType><SID>S-1-5-21-582145257-3797276795-3156641546</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Pavilion dv6000 (RV216UA#ABA)  </Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.16     </Version><SMBIOSVersion major="2" minor="4"/><Date>20070202000000.000000+000</Date></BIOS><HWID>20313507018400EE</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-MPC</OEMTableID></OEM><BRT/></MachineData><Software><Office><Result>114</Result><Products><Product GUID="{90110409-6000-11D3-8CFE-0150048383C9}"><LegitResult>114</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>59D1605114E3500</Val><Hash>vfZmaSmFPIYrLWTcZSZErUQg+Fo=</Hash><Pid>73931-640-0000106-57251</Pid><PidType>14</PidType></Product><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><Val>72812B97901EF0C</Val><Hash>R9A2SDTNSsl9hXzYBP8cIF6WTpg=</Hash><Pid>81602-902-6222646-68236</Pid><PidType>1</PidType></Product></Products><Applications><App Id="15" Version="11" Result="114"/><App Id="16" Version="11" Result="114"/><App Id="18" Version="11" Result="114"/><App Id="19" Version="11" Result="114"/><App Id="1A" Version="11" Result="114"/><App Id="1B" Version="11" Result="114"/><App Id="44" Version="11" Result="114"/><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: U1BMRwEAAAAAAQAABAAAAGNKAAAAAAAAYWECADAgAAC0fnxi6x3JAW4aG1/FHasdtBRBPRnxqCIQjestcDUe+Vr0liu89usisfj1OozZquV5dGpL20qcSuiUIQ9q7NR8lcc6509+ikj2WsBZYbIZJJLJezdT4XiJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agi/NqtheAwT3lVi9Yz2oVxz/aLa5Ab3MW/4GXKmvs8/14qf6Oj36QvkWlTB0nJij3V9lrAWWGyGSSSyXs3U+F4iTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMbhobX8Udqx20FEE9GfGoIggGCQ52cddOY5+RyJ5RKTGtAkUO0NUHesUHg/wTj+uhmrsc+bp6db/vp/yXf6beTvZawFlhshkkksl7N1PheIkzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDG4aG1/FHasdtBRBPRnxqCJ6aZSLtB9k0UGDd7kfhV3W974OQ5Wb0YOycBiJRxefGnJJmhCq3UecO7l98EwYvwP2WsBZYbIZJJLJezdT4XiJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

    Thursday, September 25, 2008 2:09 PM

Answers

  • Lady_Dantesgirl said:

    I'm going to be blunt with you - the service in this forum isn't that great, so I'm going to provide you with whatever little knowledge I have to try to give you a better insight on your problem.

    First of all, I just want to say that your copy of Vista probably is genuine, but this is just an invalid error that Vista likes to throw around quite often.

    Like I said, I'm only fairly new to this (and when I say fairly, I'm talking about last night...), but I can already locate the main problem.

    The error code you posted consists of this line:

    TTS Error: K:20080924221122683-M:20080925095150364-

    'TTS' stands for Tamper Time Stamp, which basically means there is a problem with an incompatiable piece of software on your computer. The fact that there is a 'K' means that it is only a minor problem and it should be fixed easily.

    The error code itself is an indication of the exact time this error occured. To show you what I mean, I'll break it up for you:
    2008|09|24|22:11|22683

    So that means the K error occured on the 24th September 2008 at 22:11 (10:11pm) at the 22683'd millisecond.

    This is the second error code:
    2008|09|25|09:51|50364

    So that means that the second error occured on the 25th September 2008 at 09:51 (9:51am) at the 50364'd millisecond.

    To find out what caused this error:
    1) Open Internet Explorer.
    2) Paste into the address bar 'file:///C:/Windows/system32/perfmon.msc' - I guarantee you that this is completely safe.
    3) Click 'Open'
    4) On the left hand side, click 'Reliability Monitor'
    5) Go through the 'System Stability Report' and look for an error.

    When you find something that doesn't look right, post it here and I'll take a look at it. If it's simply a piece of software, just uninstall it. If you're unsure, feel free to post it.




    Hello Lady,

    The service in this forum is actually GREAT! We provide service as quickly as possible to all customers on a GLOBAL nature. You received service in less than 24 hours on your post. If you have a concern please let us know in your thread and not post in other threads. We focus attention to each person on a one on one basis. 


    Thank you,


    Stephen Holm, MS
    WGA Forum Manager
    Stephen Holm
    • Marked as answer by Stephen Holm Thursday, September 25, 2008 8:13 PM
    Thursday, September 25, 2008 7:09 PM
  • Hello Mystarsshine,


    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, and was modified in some way. This can be caused by a malicious program (spyware, malware, and 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 usually 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, 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.

     

    In addition to why a Tamper occurs, it's also important to understand how Vista detects the Tamper 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 Tamper State and it could take some time for the Tamper to be detected. The important point to note is that the moment Vista detects the Tamper, you know that the program that caused the tamper, 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:2008      09             25              0951                         50364-

    Note, I also see a "K" type Tamper Time Stamp. The “K“stands for Kernel Mode tamper. This is a minor tamper and is most likely directly related to the Mod-Auth tamper. Once you remove the program that is causing the Mod-Auth tamper, I believe that the Kernel mode tamper will stop as well.


    (Year)      (Month)      (Day)      (Time in 24format)      (Millisecond) 

    K:2008              09                    24                       2211                                  22683-


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

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un) Installs for 09/24/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/23/2008, 09/22/2008, 09/21/2008 .

      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 (say) on 09/01/2007, but you didn't run (and, hence, prompted the tamper state)  till 09/24/2008  , this process may not be helpful.  The removal of any application you may have installed recently could go a long way to troubleshooting these issues as well since it may fall outside of the 3 day time frame described above.

     

    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 
    Stephen Holm
    • Marked as answer by Stephen Holm Thursday, September 25, 2008 8:10 PM
    Thursday, September 25, 2008 8:10 PM

All replies

  • I'm going to be blunt with you - the service in this forum isn't that great, so I'm going to provide you with whatever little knowledge I have to try to give you a better insight on your problem.

    First of all, I just want to say that your copy of Vista probably is genuine, but this is just an invalid error that Vista likes to throw around quite often.

    Like I said, I'm only fairly new to this (and when I say fairly, I'm talking about last night...), but I can already locate the main problem.

    The error code you posted consists of this line:

    TTS Error: K:20080924221122683-M:20080925095150364-

    'TTS' stands for Tamper Time Stamp, which basically means there is a problem with an incompatiable piece of software on your computer. The fact that there is a 'K' means that it is only a minor problem and it should be fixed easily.

    The error code itself is an indication of the exact time this error occured. To show you what I mean, I'll break it up for you:
    2008|09|24|22:11|22683

    So that means the K error occured on the 24th September 2008 at 22:11 (10:11pm) at the 22683'd millisecond.

    This is the second error code:
    2008|09|25|09:51|50364

    So that means that the second error occured on the 25th September 2008 at 09:51 (9:51am) at the 50364'd millisecond.

    To find out what caused this error:
    1) Open Internet Explorer.
    2) Paste into the address bar 'file:///C:/Windows/system32/perfmon.msc' - I guarantee you that this is completely safe.
    3) Click 'Open'
    4) On the left hand side, click 'Reliability Monitor'
    5) Go through the 'System Stability Report' and look for an error.

    When you find something that doesn't look right, post it here and I'll take a look at it. If it's simply a piece of software, just uninstall it. If you're unsure, feel free to post it.


    Thursday, September 25, 2008 3:28 PM
  • Lady_Dantesgirl said:

    I'm going to be blunt with you - the service in this forum isn't that great, so I'm going to provide you with whatever little knowledge I have to try to give you a better insight on your problem.

    First of all, I just want to say that your copy of Vista probably is genuine, but this is just an invalid error that Vista likes to throw around quite often.

    Like I said, I'm only fairly new to this (and when I say fairly, I'm talking about last night...), but I can already locate the main problem.

    The error code you posted consists of this line:

    TTS Error: K:20080924221122683-M:20080925095150364-

    'TTS' stands for Tamper Time Stamp, which basically means there is a problem with an incompatiable piece of software on your computer. The fact that there is a 'K' means that it is only a minor problem and it should be fixed easily.

    The error code itself is an indication of the exact time this error occured. To show you what I mean, I'll break it up for you:
    2008|09|24|22:11|22683

    So that means the K error occured on the 24th September 2008 at 22:11 (10:11pm) at the 22683'd millisecond.

    This is the second error code:
    2008|09|25|09:51|50364

    So that means that the second error occured on the 25th September 2008 at 09:51 (9:51am) at the 50364'd millisecond.

    To find out what caused this error:
    1) Open Internet Explorer.
    2) Paste into the address bar 'file:///C:/Windows/system32/perfmon.msc' - I guarantee you that this is completely safe.
    3) Click 'Open'
    4) On the left hand side, click 'Reliability Monitor'
    5) Go through the 'System Stability Report' and look for an error.

    When you find something that doesn't look right, post it here and I'll take a look at it. If it's simply a piece of software, just uninstall it. If you're unsure, feel free to post it.




    Hello Lady,

    The service in this forum is actually GREAT! We provide service as quickly as possible to all customers on a GLOBAL nature. You received service in less than 24 hours on your post. If you have a concern please let us know in your thread and not post in other threads. We focus attention to each person on a one on one basis. 


    Thank you,


    Stephen Holm, MS
    WGA Forum Manager
    Stephen Holm
    • Marked as answer by Stephen Holm Thursday, September 25, 2008 8:13 PM
    Thursday, September 25, 2008 7:09 PM
  • Hello Mystarsshine,


    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, and was modified in some way. This can be caused by a malicious program (spyware, malware, and 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 usually 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, 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.

     

    In addition to why a Tamper occurs, it's also important to understand how Vista detects the Tamper 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 Tamper State and it could take some time for the Tamper to be detected. The important point to note is that the moment Vista detects the Tamper, you know that the program that caused the tamper, 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:2008      09             25              0951                         50364-

    Note, I also see a "K" type Tamper Time Stamp. The “K“stands for Kernel Mode tamper. This is a minor tamper and is most likely directly related to the Mod-Auth tamper. Once you remove the program that is causing the Mod-Auth tamper, I believe that the Kernel mode tamper will stop as well.


    (Year)      (Month)      (Day)      (Time in 24format)      (Millisecond) 

    K:2008              09                    24                       2211                                  22683-


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

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un) Installs for 09/24/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/23/2008, 09/22/2008, 09/21/2008 .

      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 (say) on 09/01/2007, but you didn't run (and, hence, prompted the tamper state)  till 09/24/2008  , this process may not be helpful.  The removal of any application you may have installed recently could go a long way to troubleshooting these issues as well since it may fall outside of the 3 day time frame described above.

     

    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 
    Stephen Holm
    • Marked as answer by Stephen Holm Thursday, September 25, 2008 8:10 PM
    Thursday, September 25, 2008 8:10 PM