locked
Vista "not genuine" after sp1 upgrade attempt "unauthorized change to liscense" RRS feed

  • Question

  • I have a LEGAL copy of Vista. How do I know? It came preloaded from HP- so unless HP is shipping pirated software with their notebooks this is a legal copy. Everything was working fine until sp1 attempt yesterday which failed to install and rolled itself back SUPPOSEDLY.

     Now I only have "limited functionality"  "Windows not genuine"   "unauthorized change to liscense"

     

    HELP!!!

     

    Diagnostic Report (1.7.0069.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0xc004d401
    Cached Validation Code: N/A, hr = 0x80004005
    Windows Product Key: *****-*****-GD2PK-BD3R2-44MV3
    Windows Product Key Hash: f7FPE6g/CLFmnJ4E6GbEU9Xn1sA=
    Windows Product ID: 89572-OEM-7332166-00021
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6000.2.00010300.0.0.002
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {4B8C403D-7B95-43AE-92AF-F67CF8A519E9}(1)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.7.69.1
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Basic
    Architecture: 0x00000000
    Build lab: 6000.vista_gdr.071023-1545
    TTS Error: M:20080320120031943-
    Validation Diagnostic:
    Resolution Status: N/A

    WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: 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: 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: FCEE394C-2920-80070002_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>{4B8C403D-7B95-43AE-92AF-F67CF8A519E9}</UGUID><Version>1.7.0069.0</Version><OS>6.0.6000.2.00010300.0.0.002</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-44MV3</PKey><PID>89572-OEM-7332166-00021</PID><PIDType>2</PIDType><SID>S-1-5-21-4268873803-2005341152-606289516</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Pavilion dv6000 (RX019AV#ABA)  </Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.16     </Version><SMBIOSVersion major="2" minor="4"/><Date>20070202000000.000000+000</Date></BIOS><HWID>38313507018400EE</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>100</Result><Products><Product GUID="{91120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>9F5577161FED6CE</Val><Hash>T/DTxyXbz9m6wRRtFIjVorXOLD0=</Hash><Pid>81599-871-9238204-65184</Pid><PidType>1</PidType></Product></Products></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAPMOAAAAAAAAYWECANOQl6PTURksMg7IAVMWKYGB4wMcsbz+lAen7WfTlMrUKb5LZP0qGc4aMIHuX8mw/4XBADnL9eBL+i8bEu97BuxrKcj+9gzTrUJt+r1og4Rl7Pc1XB1wwGrSEYeSnKfOZv/AmB9uvmxWADGc/AFrdnzWO+jF8eq69LRpcSiTN/jEi/pgsTdkQKOEZadnYeIFmHEs83923aEKqaV7o+zn9064UC3nw4H6gZCOU0nKqWFt2MoukZB/UcTfBJcD74TgJfOd1LfEdWT9Qb1zuiT+h08wRI5b3Ii0HwoRaNfY7o+X32CpOdJhHiPQVqyFM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxTFimBgeMDHLG8/pQHp+1nsLoAEhFzEzFD1EbPL4uAnzK81YdA0+lR5t3613E4cqTvewbsaynI/vYM061Cbfq9Ejfr0avkzFhNf+NJurIiZpynzmb/wJgfbr5sVgAxnPwBa3Z81jvoxfHquvS0aXEokzf4xIv6YLE3ZECjhGWnZ2HiBZhxLPN/dt2hCqmle6Ps5/dOuFAt58OB+oGQjlNJyqlhbdjKLpGQf1HE3wSXA++E4CXzndS3xHVk/UG9c7ok/odPMESOW9yItB8KEWjX2O6Pl99gqTnSYR4j0FashTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMUxYpgYHjAxyxvP6UB6ftZ2IQ16xNRyzpDjrEDTWQnW1r1lBNGmlZvdUdzfZB3zt/73sG7GspyP72DNOtQm36vTd+Nvage22A8NhE0lJSDSWcp85m/8CYH26+bFYAMZz86bxyE4QSuYb82i1/zOcW05M3+MSL+mCxN2RAo4Rlp2dh4gWYcSzzf3bdoQqppXuj7Of3TrhQLefDgfqBkI5TScqpYW3Yyi6RkH9RxN8ElwPvhOAl853Ut8R1ZP1BvXO6JP6HTzBEjlvciLQfChFo19juj5ffYKk50mEeI9BWrIUzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDFMWKYGB4wMcsbz+lAen7Wf2rtwEubxL96JXRYV4LlupxAiybOBhGQYpGFiYb91CI+97BuxrKcj+9gzTrUJt+r090hs4lwlweZxtE9nyThQmnKfOZv/AmB9uvmxWADGc/AFrdnzWO+jF8eq69LRpcSiTN/jEi/pgsTdkQKOEZadnYeIFmHEs83923aEKqaV7o+zn9064UC3nw4H6gZCOU0nKqWFt2MoukZB/UcTfBJcD74TgJfOd1LfEdWT9Qb1zuiT+h08wRI5b3Ii0HwoRaNfY7o+X32CpOdJhHiPQVqyFM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

     

    Friday, March 21, 2008 9:11 AM

Answers

  • Hello lampoilman,

     

    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 usually caused by a running program that is incompatible with Vista.

     

    Because there are No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, your issue is a 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 follow the steps to resolve the issue. Also 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      03      20        1200                31943-

     


    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 03/20 

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 03/20/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 03/19/2008, 03/18/2008 and 03/17/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 03/20/2008, this process may not be helpful. 

     

    To summerize:

    a) Vista is in a Mod-Auth tamper caused by a program running that is incompatible with Vista.

    b) Only while the incompatible program is Running, will the Mod-Auth occure.

    c) The program may have been installed some time ago, it's only when you run it will the issue happen.

    d) The service that detects (that the incompatible program is doing something it shouldn't) runs randomly, so even if you run the incompatible program, it may take some time for the Mod-Auth to occure.

    e) SP1 could Not have caused this because:

    1) SP1 only runs once, so if SP1 is not currently running and you still have the issue....it's not SP1 that is causing it.

    2) SP1 couldn't make changes to Vista that would make Vista incompatible with itself, otherwise everyone would have this issue. 

     

    Thank you,

    Darin Smith

    WGA Forum Manager

    Friday, March 21, 2008 10:03 PM

All replies

  • Hello lampoilman,

     

    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 usually caused by a running program that is incompatible with Vista.

     

    Because there are No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, your issue is a 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 follow the steps to resolve the issue. Also 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      03      20        1200                31943-

     


    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 03/20 

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 03/20/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 03/19/2008, 03/18/2008 and 03/17/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 03/20/2008, this process may not be helpful. 

     

    To summerize:

    a) Vista is in a Mod-Auth tamper caused by a program running that is incompatible with Vista.

    b) Only while the incompatible program is Running, will the Mod-Auth occure.

    c) The program may have been installed some time ago, it's only when you run it will the issue happen.

    d) The service that detects (that the incompatible program is doing something it shouldn't) runs randomly, so even if you run the incompatible program, it may take some time for the Mod-Auth to occure.

    e) SP1 could Not have caused this because:

    1) SP1 only runs once, so if SP1 is not currently running and you still have the issue....it's not SP1 that is causing it.

    2) SP1 couldn't make changes to Vista that would make Vista incompatible with itself, otherwise everyone would have this issue. 

     

    Thank you,

    Darin Smith

    WGA Forum Manager

    Friday, March 21, 2008 10:03 PM
  • Darin,

     

    Thank you for your prompt and courteous reply.

    I will preform the steps suggested in a few days when I have time,

    but I am not hopeful as:

     

    1. I have installed no apps, java or active x in well over a month.

    2. This has happened before - several months ago after a "genuine DIS-advantage" upgrade

    3. Local computer radio talk show guy said that this problem has been linked to some

        early "Vista ready" systems. Last time I had to reinstall

    Sunday, March 23, 2008 7:11 AM