Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Windows Vista Validation RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I did windows recovery on this laptop using manufacture hard disk partition. After recovery, it says the Windows version is not genius and ask me to enter the product key again. I don't have access to this key as it has worn away.

    Please help to resolve the issue.

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-XK376-TJ7T4-76PKF
    Windows Product Key Hash: 5QFdDDGgO8Pgmj93aZhOuZ69dH0=
    Windows Product ID: 89578-022-5000027-71416
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.0.6002.2.00010300.2.0.003
    ID: {D5C6B4FC-5039-4D00-9D19-61F233EA3B99}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6002.vistasp2_gdr.130707-1535
    TTS Error: M:20130827181401481-
    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: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: B4D0AA8B-604-645_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.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>{D5C6B4FC-5039-4D00-9D19-61F233EA3B99}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6002.2.00010300.2.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-76PKF</PKey><PID>89578-022-5000027-71416</PID><PIDType>5</PIDType><SID>S-1-5-21-1917705021-374260620-1927911711</SID><SYSTEM><Manufacturer>ASUSTeK Computer Inc.        </Manufacturer><Model>M50Vc               </Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>212    </Version><SMBIOSVersion major="2" minor="5"/><Date>20091014000000.000000+000</Date></BIOS><HWID>5D303507018400F8</HWID><UserLCID>1809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAMJYAAAAAAAAYWECAARAip9agqHHsKHOARhy9171jCizkdIEkQaJZ65C66EQAnirrRf3JnvsjEjMer8P4Cdg6WhUF/ZU1BV9nxQjdPDwDinTfkQXASERseEbgC8fMPbXg4WqvofoI9hVk/oA/SfEX6ot/bnNmgLA1vu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxZcgJE7vAy9kku8TlF45JWpsbJiscvAYWgzyFZ0z79y2BX7mQ2Q7393z5XQ50VXv9mhrKhq4UIi+PwtGQfjOGIjOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeupbG+z+CZUvsOIdYST4zBYD+md+xals7Qg3QxBvNaDZ8UI3Tw8A4p035EFwEhEbHhSEyX+R2KYiWogGIMS0KB9pP6AP0nxF+qLf25zZoCwNb7tVLwe28YiH1BLYCERqYZDkmvhBlGHDl+f1L5AB51cWXICRO7wMvZJLvE5ReOSVqbGyYrHLwGFoM8hWdM+/ctgV+5kNkO9/d8+V0OdFV7/ZoayoauFCIvj8LRkH4zhiIzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrgaPoUzwqnPDHB+YcjJ6HCyD+iZ+Y/aGkA/BUmwEn85q58O9fTMLJuYOKXJAu21UjKqVAirsbAW/fJmXE6Z79bmwQaeZHRF4n0qVYImi7Gro8AjAfAdUx+81q5JsW+ZpMGACbXwGR0lMTQQYALCXt1X1L8ZQNh5x48VEoz+V5L3tvE5VWb18gJlSR8d0M1ujvapSphiYCVEk7Tn5ZXWvvTDY7o+X32CpOdJhHiPQVqyFM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhy9171jCizkdIEkQaJZ66hIDZtrI3OVi7EOiGvWKW7wpWAFOMGZE5/3bIZF22IUhQjdPDwDinTfkQXASERseGM6cfABa1sw8/cG+IWJGIIk/oA/SfEX6ot/bnNmgLA1vu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxZcgJE7vAy9kku8TlF45JWpsbJiscvAYWgzyFZ0z79y2BX7mQ2Q7393z5XQ50VXv9mhrKhq4UIi+PwtGQfjOGIjOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeuxTIct8J65hG238UoPS7oLrIDwbvhcRYA/DeYFIHBNdAUI3Tw8A4p035EFwEhEbHhjOnHwAWtbMPP3BviFiRiCJP6AP0nxF+qLf25zZoCwNb7tVLwe28YiH1BLYCERqYZDkmvhBlGHDl+f1L5AB51cWXICRO7wMvZJLvE5ReOSVqbGyYrHLwGFoM8hWdM+/ctgV+5kNkO9/d8+V0OdFV7/ZoayoauFCIvj8LRkH4zhiIzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM

    Licensing Data-->
    Software licensing service version: 6.0.6002.18005

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: OgAAAAIABAABAAEAAQACAAAAAwABAAEAeqhCLncWHCCeEbg5gk741T5vpJXy9ETYeMxoJr4FrFZGyg==

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            101409        APIC1544
      FACP            101409        FACP1544
      DBGP            101409        DBGP1544
      HPET            101409        OEMHPET
      BOOT            101409        BOOT1544
      MCFG            101409        OEMMCFG
      OEMX            101409        OEMX1544
      ECDT            101409        OEMECDT
      OEMB            101409        OEMB1544
      TCPA            101409        TBLOEMID
      ATKG            022008        OEMATKG
      SSDT            PmRef        CpuPm



    Tuesday, August 27, 2013 6:56 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Your problem is a Mod-Auth Tamper.

     

    There are 2 types of Mod-Auth tampers.

     

    1) A critical system file was modified On Disk - What this means is that a 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 this is caused by running a program that is incompatible with Vista.

     

    Because there are 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.

    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 are 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:20130827181401481-

     

    This is the Tamper Time Stamp and it breaks down like this:

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

     

    M:2013         08        27            1814                 01481-

     

     

    (Note that the following only applies if this is the FIRST time you've seen the error! - if it's a problem that's been around for a while you'll need to work out when you first saw it, and apply that date below)

     

    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 8th July

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 27th Aug "

    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 24th to 26th July (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: If you suspect that Malware, such as Viruses and Trojans, has caused the In Memory Mod-Auth,

    Please download and install  Malwarebytes Anti-malware (free version) from  www.malwarebytes.org - UNtick 'Enable free trial of MBAM PRO' at the end of the installation -  and update it, then run a full scan  in your main account, and Quick scans in any other user accounts.

     

    Delete everything it finds   

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Wednesday, August 28, 2013 11:37 AM
    Moderator