locked
Software Not Genuine???? RRS feed

  • Question

  • What happened with my original windows license? I bought this notebook with Windows Vista pre installed.

    Few days ago, a message box appeared and Aero feature is not working since that day.

     

    Diagnostic report:

     

    Any explanation?

     

    Diagnostic Report (1.7.0062.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0xc004d401
    Cached Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-2WYKM-GBM3G-XM3H2
    Windows Product Key Hash: BaH+4ZtUU4s3R0+N/isNquyMYpE=
    Windows Product ID: 89578-OEM-7215677-76100
    Windows Product ID Type: 8
    Windows License Type: COA SLP
    Windows OS version: 6.0.6000.2.00010300.0.0.000
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {41D7CEA5-3233-4D1D-A204-AFE8FE0E99D1}(1)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.7.59.1
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6000.vista_gdr.070627-1500
    TTS Error: K:20071028210233698-M:20071028205445173-
    Validation Diagnostic:
    Resolution Status: N/A

    WgaER Data-->
    Grace Flag: N/A, hr = 0xc004d401
    Commit: N/A, hr = 0xc004d401
    Reboot Flag: 0x0
    ThreatID(s): N/A, hr = 0xc004d401
    Wgaer.exe Version: N/A, hr = 0x80070002
    Wgaer.exe Signed By: N/A, hr = 0x80070002

    Notifications Data-->
    Cached Result: N/A
    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 Data-->
    Office Status: 109 N/A
    OGA Version: Registered, 1.6.21.0
    Signed By: Microsoft
    Office Diagnostics: B4D0AA8B-531-645

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Win32)
    Default Browser: C:\PROGRA~1\MOZILL~2\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>{41D7CEA5-3233-4D1D-A204-AFE8FE0E99D1}</UGUID><Version>1.7.0062.0</Version><OS>6.0.6000.2.00010300.0.0.000</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-XM3H2</PKey><PID>89578-OEM-7215677-76100</PID><PIDType>8</PIDType><SID>S-1-5-21-3308472759-3504468858-2495799252</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>MCP51M</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.27    </Version><SMBIOSVersion major="2" minor="4"/><Date>20070118000000.000000+000</Date></BIOS><HWID>67303507018400FE</HWID><UserLCID>2C0A</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>SA Eastern Standard Time(GMT-03:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><BRT/></MachineData><Software><Office><Result>109</Result><Products/></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAEa3QQAAAAAAYWECADAgAAAguo2P6hPIARhDs/4hWdo7Xkl9D+HKpnigY4qCQEZay1rbHDF1b6cv04vVADisw1ty+k28Up8fnVF0H9Oh+hJEw7XKSAShRbemd84ybZjeiQoed1N3gqw/1mjkjzXhcq94m48ceJqGOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y0OKm53Bw867hHNE43WvZqUI0Rf1MqA3D5sWfEw7WeNfzOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYQ7P+IVnaO15JfQ/hyqZ4/m8tdCv+Cg8Gmp/rjX14imXIoM1ZxcjliLO9fnWHzsg8ZiIZ8SUultqIbAs2na9C+OLDuf808buiGWxEn80CRQbVOs8s97/WdjKyB2vcd1t3DT+mCSUc2d7Bj2THWrgqQdvFFncxR62TzQo0j8c3rVB8YXH9/GpCVo60xZnYqNxuDG7GXSRQZeiA/Gej4MzhN6aSh4VagsJL2g8wUu0UX/NNfofjLExZEZSdmQI0QIgzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGEOz/iFZ2jteSX0P4cqmeH3wc9L9o4qgssMXT6eAqJikej2SVD8KaiMR2hxRnC7rUXQf06H6EkTDtcpIBKFFt8S32TqYgqNUXv8WHXFnM4jWaOSPNeFyr3ibjxx4moY4+7VS8HtvGIh9QS2AhEamGQ5Jr4QZRhw5fn9S+QAedXHKlSlNgUn/lD0SF0aEkphMmxsmKxy8BhaDPIVnTPv3LQ4qbncHDzruEc0Tjda9mpQjRF/UyoDcPmxZ8TDtZ41/M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhDs/4hWdo7Xkl9D+HKpng+B45lpFp5AjTNE6Fa3IA+lvUIR2mg2eOoCxzW/2l+/1F0H9Oh+hJEw7XKSAShRbc8TARIf7P55U/6W3nnR6jR1mjkjzXhcq94m48ceJqGOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y0OKm53Bw867hHNE43WvZqUI0Rf1MqA3D5sWfEw7WeNfzOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

     

    Monday, October 29, 2007 12:29 AM

Answers

  • Hi Gashina,

     

    What's happening is  called a Tamper State. There is a program that is incompatible with Vista and when that program does something that Vista doesn't allow, Vista goes into a Tamper state.

     

    There is two types of programs that cause a Tamper State

      a) A program that can be launched at any time, by the user (such as a game or application)

      b) A program that launches at Start up and that contently runs (such as an anti-virus program)

     

    The key is identifying the offending program and either deleting it or upgrading is to a Vista compatible version.

     

    In your Diagnostic report above, you can see the line that starts with 'TTS Error:' followed by a bunch of letters and numbers: K:20071028210233698-M:20071028205445173-

     

    If you break down the numbers, you will get a time stamp:

     

        (year)  (month) (day) (time in 24format) (milliseconds)

    K: 2007      10       28          2102                  33698

    M: 2007      10       28          2054                  45173

     

    In your case you have 2 tampers, but since it's at about the same time, I would assume it's only one program causing both tampers.

     

    Now that we know the time of the tamper, you can now try to connect that time with a program.

     

    we do that by:

    1) Click the 'Start' button

    2) Right Click 'Computer'

    3) Select 'Manage'

    4) Continue thru the "Windows needs your permission to continue" window (if any)

    5) Click the arrow next to 'Reliability and Performance'

    6) Click the arrow next to 'Monitoring Tools'

    7) Click on 'Reliability Monitor'

    8) Click on the graph above the date 10/28/2007

    9) Below the graph, look at the report titled "Software (Un)Installs for 10/28/2007"

    10) Look for any program that shows "Application Install" in the 'Activity' column.

    11) 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 8) thru 10) for the dates 10/27, 10/26 and 10/25

    This will tell you what programs were installed on 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 10/28/2007, this process may not be helpful. 

     

    Please tell me if this helps you resolve the issue.

     

    Thank you,
    Darin Smith
    WGA Forum Manager
    Wednesday, November 7, 2007 10:13 PM

All replies

  • Hi Gashina,

     

    What's happening is  called a Tamper State. There is a program that is incompatible with Vista and when that program does something that Vista doesn't allow, Vista goes into a Tamper state.

     

    There is two types of programs that cause a Tamper State

      a) A program that can be launched at any time, by the user (such as a game or application)

      b) A program that launches at Start up and that contently runs (such as an anti-virus program)

     

    The key is identifying the offending program and either deleting it or upgrading is to a Vista compatible version.

     

    In your Diagnostic report above, you can see the line that starts with 'TTS Error:' followed by a bunch of letters and numbers: K:20071028210233698-M:20071028205445173-

     

    If you break down the numbers, you will get a time stamp:

     

        (year)  (month) (day) (time in 24format) (milliseconds)

    K: 2007      10       28          2102                  33698

    M: 2007      10       28          2054                  45173

     

    In your case you have 2 tampers, but since it's at about the same time, I would assume it's only one program causing both tampers.

     

    Now that we know the time of the tamper, you can now try to connect that time with a program.

     

    we do that by:

    1) Click the 'Start' button

    2) Right Click 'Computer'

    3) Select 'Manage'

    4) Continue thru the "Windows needs your permission to continue" window (if any)

    5) Click the arrow next to 'Reliability and Performance'

    6) Click the arrow next to 'Monitoring Tools'

    7) Click on 'Reliability Monitor'

    8) Click on the graph above the date 10/28/2007

    9) Below the graph, look at the report titled "Software (Un)Installs for 10/28/2007"

    10) Look for any program that shows "Application Install" in the 'Activity' column.

    11) 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 8) thru 10) for the dates 10/27, 10/26 and 10/25

    This will tell you what programs were installed on 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 10/28/2007, this process may not be helpful. 

     

    Please tell me if this helps you resolve the issue.

     

    Thank you,
    Darin Smith
    WGA Forum Manager
    Wednesday, November 7, 2007 10:13 PM
  • How do I get this diagnostic report?  I am having the same problem with my preloaded Vista installation.

     

    Thanks,

    Jeremy

     

    Sunday, February 24, 2008 3:27 PM