locked
Vista has started saying it is not genuine. RRS feed

  • Question

  • We have a Dell laptop that has suddenly started claining it is not genuine. I have tried the solution in kb931573 but it says that it does not apply. Trying to revalidate via the web says it is not geunuine.

    The output of MGADiag is:

    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 = 0x80004005

    Windows Product Key: *****-*****-VRCTY-3V3RH-WRMG7

    Windows Product Key Hash: l2HYuM058SkcIU57PqWaCOL7rEU=

    Windows Product ID: 89576-OEM-7332141-00054

    Windows Product ID Type: 2

    Windows License Type: OEM SLP

    Windows OS version: 6.0.6000.2.00010100.0.0.006

    CSVLK Server: N/A

    CSVLK PID: N/A

    ID: {7EFA6927-265D-413E-9737-BD4274930899}(3)

    Is Admin: Yes

    TestCab: 0x0

    WGA Version: Registered, 1.7.69.2

    Signed By: Microsoft

    Product Name: Windows Vista (TM) Business

    Architecture: 0x00000000

    Build lab: 6000.vista_gdr.071009-1548

    TTS Error: K:20081009140046924-M:20081009125746972-

    Validation Diagnostic:

    Resolution Status: N/A

     

    WgaER Data-->

    ThreatID(s): N/A, hr = 0x80070002

    Version: N/A, hr = 0x80070002

     

    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: 100 Genuine

    Microsoft Office Small Business 2007 - 100 Genuine

    OGA Version: N/A, 0x80070002

    Signed By: N/A, hr = 0x80070002

    Office Diagnostics: 77F760FE-153-80070002_7E90FEE8-175-80070002_7E90FEE8-198-80004005_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\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>{7EFA6927-265D-413E-9737-BD4274930899}</UGUID><Version>1.7.0095.0</Version><OS>6.0.6000.2.00010100.0.0.006</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-WRMG7</PKey><PID>89576-OEM-7332141-00054</PID><PIDType>2</PIDType><SID>S-1-5-21-2831625289-657346063-2484030645</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>MP061                           </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A07</Version><SMBIOSVersion major="2" minor="4"/><Date>20070205000000.000000+000</Date></BIOS><HWID>02333507018400FA</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL  </OEMID><OEMTableID>M07    </OEMTableID></OEM><BRT/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-00CA-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Small Business 2007</Name><Ver>12</Ver><Val>B0332181402E5AE</Val><Hash>Ymmhqh4OLFhMy2Fk8ANeYd7hBUs=</Hash><Pid>81606-OEM-6472727-17190</Pid><PidType>4</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"/></Applications></Office></Software></GenuineResults> 

     

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAACcoFQAAAAAAYWECADAgAAAPTK+YuyfJAW4aG1/FHasdtBRBPRnxqCLYrRMcDGbBOLZyzPit2urZCHwY3JX6O1vIFdi205G6nzCz23cw+crsFqgqjDNgFF/2WsBZYbIZJJLJezdT4XiJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agi2K0THAxmwTi2csz4rdrq2Us4rq2LzntfP2S4ll6s24Mws9t3MPnK7BaoKowzYBRf9lrAWWGyGSSSyXs3U+F4iTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMbhobX8Udqx20FEE9GfGoImscgHVuCGlCFkWd/bIp9nn+hxpIWPVsNbkn3qdvk10UEy1szKv04v9PfcBnLkFOPvZawFlhshkkksl7N1PheIkzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDG4aG1/FHasdtBRBPRnxqCJrIuLtpPGlq/6U4CetBYD8+4/5Gk1INOD8+PNkMbhKbmThitsBD2SX02fT3KYCKVD2WsBZYbIZJJLJezdT4XiJM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxuGhtfxR2rHbQUQT0Z8agiayLi7aTxpav+lOAnrQWA/IZLwV97HBrTP5mwcyXC/Udk4YrbAQ9kl9Nn09ymAilQ9lrAWWGyGSSSyXs3U+F4iTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMbhobX8Udqx20FEE9GfGoIs0GVyvSmgrRj3lEwfJqbKOZF0fcZwBhkRzTRWV7OUzryOib+w/u4y1NgXOD/IJV7fZawFlhshkkksl7N1PheIkzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDA==

    Thursday, October 9, 2008 3:06 PM

Answers

  •  Hello,


    Windows 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 (malware) 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 Windows 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 Windows Vista does not allow which by definition means it is incompatible with Windows Vista.

     

    In addition to why a Tamper occurs, it's also important to understand how Windows Vista detects the Tamper event. There is a Service that runs in Windows 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, Windows 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 Windows 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:

     

    The following Knowledge Base (KB) article may help you confirm that you do not have any of the programs known to cause this type of issue.

     

    KB931699 - Error message when you use Windows Vista: "An unauthorized change was made to your license"

     

    http://support.microsoft.com/kb/931699/

     
    Second, in your Microsoft Genuine Diagnostic Tool (MGADT) 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    10        09        1257               46972-

    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   10    09     1400              46924-


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

     1) Login to Windows Vista and select the option which 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) Then click System Stability Chart above the date 10/09.   

    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 Windows Vista to a Tamper State. Because of this, please repeat steps 5) through 7) for the dates 10/8/2009 10/7/2008 and 10/6/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 10/09/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 the following link below:

    http://go.microsoft.com/fwlink/?linkid=52029

    Thank you for visiting the Genuine Advantage forum



    Stephen Holm, MS
    WGA Forum Manager


    Stephen Holm
    • Marked as answer by Stephen Holm Thursday, October 9, 2008 10:55 PM
    Thursday, October 9, 2008 10:54 PM