locked
After Updating, Windows Tells Me my Copy is No Longer Genuine RRS feed

  • Question

  • Any ideas? I can't install SP1 because of this. I have no idea what I could of installed to cause this issue.A few other questions:How can I tell if I have SP1 installed? Is there a way I can check or manually download it?Please help me diagnose this problem.

    Heres the diagnostic report.

    Diagnostic Report (1.7.0095.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0x80070426
    Cached Validation Code: N/A, hr = 0x80070426
    Windows Product Key: *****-*****-K2VH3-GW2W7-CPCHF
    Windows Product Key Hash: gV7Kj7jSpNz6JaWJaSFdmvyGc/g=
    Windows Product ID: 89587-OEM-7300551-51626
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.0.6000.2.00010100.0.0.001
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {3ACD3A52-4CDE-4961-BD33-79EC4E0B3249}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Ultimate
    Architecture: 0x00000009
    Build lab: 6000.vista_gdr.071023-1545
    TTS Error: M:20080620132347066-
    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: 109 N/A
    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 (x86)\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-->
    File Mismatch: C:\Windows\system32\user32.dll[6.0.6000.16438]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{3ACD3A52-4CDE-4961-BD33-79EC4E0B3249}</UGUID><Version>1.7.0095.0</Version><OS>6.0.6000.2.00010100.0.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-CPCHF</PKey><PID>89587-OEM-7300551-51626</PID><PIDType>3</PIDType><SID>S-1-5-21-1646777919-2439155821-4055577931</SID><SYSTEM><Manufacturer>XFX78I</Manufacturer><Model>XFX nForce 780i 3-Way SLI</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>6.00 PG</Version><SMBIOSVersion major="2" minor="4"/><Date>20080324000000.000000+000</Date></BIOS><HWID>DD303507018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06: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/><Applications/></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAACAAAANQKAAAAAAAAYWECAID6//8uOff2qdDIAdArSr9MLECc5R83cvYPeMxWEHEI5TljVReF15U8CfLpOaFpgt+7ZF920BWdPauuuaPTNr0UEFCkVaUbxRmsJE3SoNeIuMpnV0y+oEalFG9Lqiy06+216T3+3YpHs/4iZ+S8PGJVzATbEeSmtmHv23Fszgift7ojEtbVSJvAMAEwNKSqzmEoZxPMqvgdiGIQOT9vjSLV9dzF//x4MzHjERZj7qSz1UKGdypAhr3Jq5d0KZNWwwdYiXpc/hINcaDhijOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMmSwW+1nAbBIsraNBThNrX4gDsYVcTznQkHud63pwvOyj0za9FBBQpFWlG8UZrCRNXa83PGvHj7TwpyUUOw9QEqostOvttek9/t2KR7P+ImfkvDxiVcwE2xHkprZh79txbM4In7e6IxLW1UibwDABMDSkqs5hKGcTzKr4HYhiEDk/b40i1fXcxf/8eDMx4xEWY+6ks9VChncqQIa9yauXdCmTVsMHWIl6XP4SDXGg4YozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zDLL+RlRok8CoDKrdu4DkgretRJaDj7R2YdN4u23hG9so9M2vRQQUKRVpRvFGawkTbwEI7+ts/o1/oKyNs/eTTCqLLTr7bXpPf7dikez/iJn5Lw8YlXMBNsR5Ka2Ye/bcWzOCJ+3uiMS1tVIm8AwATA0pKrOYShnE8yq+B2IYhA5P2+NItX13MX//HgzMeMRFmPupLPVQoZ3KkCGvcmrl3Qpk1bDB1iJelz+Eg1xoOGKM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDA==


    Friday, June 20, 2008 6:32 PM

Answers

  • Hello nodiquefb,

     

    Vista is in what is called 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 random file corruption, 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 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 may not occure.

     

    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 of the Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, (i.e. user32.dll[6.0.6000.16438]) your issue is a On Disk Mod-Auth

     

      To resolve the issue, we need to replace the bad file with a unmodified/uncorrupted copy. You can do this by one of following ways:

     

    A) Install Service Pack 1 for Vista (http://www.microsoft.com/downloads/details.aspx?FamilyID=b0c7136d-5ebb-413b-89c9-cb3d06d12674&DisplayLang=en). I believe SP1 contains an updated version of file user32.dll, that once installed, should resolve the issue.

     

    Or

     

    B) You can re-install a past Update that contained that file (in your case update KB925902) by following the below steps:

     

    First, uninstall the updates:

     

    1) Log into Vista in Safe Mode

    2) Click 'Start' button, then Click 'Control Panel'.

    3) Click 'Classic View' in the upper right of the Control Panel window.

    4) Double-Click the icon named 'Programs and Features'.

    5) Click the 'View installed updates' link in the upper right of the Program and Features window.

    6) It may take some time for the list of Updates to appear, please wait.

    7) Right-Click on the update 'KB925902' and select 'Uninstall'.

    8) Reboot into Normal Mode

     

    Now, manually reinstall the updates:

    (At this point, Vista may or may not be in reduced functionality, the below steps assume that Vista is in reduced functionality)

     

    9) Log in to Vista and select the options that brings up the Internet Browser.

    10) Go to http://www.microsoft.com/downloads

    11) Search for KB925902

    12) In the search results, click the update that has "KB925902" in the name.

    13) Click the 'Download' button.

    14) You will be given the choice to Save or Run, select Run

    15) Reboot 2 times. 

     

    Or

     

    C) Repair Windows using System Restore:

     

    1) Reboot Vista into Safe Mode

    2) Go to Control Panel

    3) On the left hand side of the Control Panel window, Click on "Classic View"

    4) Double-click "Backup and Restore Center"

    5) On the left hand side of the window, click "Repair Windows using system restore"

    6) Select "Choose Different Restore Point", Put a check in the box that says "Show restore points older than 5 days", select the restore point that corresponds to the date Before you first noticed the issue.

    7) Click the "Next" button.

    8) Reboot back into Normal mode

    9) Vista should no longer be in Reduced Functionality mode

     

     And lastly, if none of these suggestions resolves your issue, open a (no cost) support request at http://go.microsoft.com/fwlink/?linkid=52029 for additional assistance.

     

    Thank you,

    Darin Smith

    WGA Forum Manager

    Friday, June 20, 2008 7:31 PM

All replies

  • Hello nodiquefb,

     

    Vista is in what is called 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 random file corruption, 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 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 may not occure.

     

    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 of the Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, (i.e. user32.dll[6.0.6000.16438]) your issue is a On Disk Mod-Auth

     

      To resolve the issue, we need to replace the bad file with a unmodified/uncorrupted copy. You can do this by one of following ways:

     

    A) Install Service Pack 1 for Vista (http://www.microsoft.com/downloads/details.aspx?FamilyID=b0c7136d-5ebb-413b-89c9-cb3d06d12674&DisplayLang=en). I believe SP1 contains an updated version of file user32.dll, that once installed, should resolve the issue.

     

    Or

     

    B) You can re-install a past Update that contained that file (in your case update KB925902) by following the below steps:

     

    First, uninstall the updates:

     

    1) Log into Vista in Safe Mode

    2) Click 'Start' button, then Click 'Control Panel'.

    3) Click 'Classic View' in the upper right of the Control Panel window.

    4) Double-Click the icon named 'Programs and Features'.

    5) Click the 'View installed updates' link in the upper right of the Program and Features window.

    6) It may take some time for the list of Updates to appear, please wait.

    7) Right-Click on the update 'KB925902' and select 'Uninstall'.

    8) Reboot into Normal Mode

     

    Now, manually reinstall the updates:

    (At this point, Vista may or may not be in reduced functionality, the below steps assume that Vista is in reduced functionality)

     

    9) Log in to Vista and select the options that brings up the Internet Browser.

    10) Go to http://www.microsoft.com/downloads

    11) Search for KB925902

    12) In the search results, click the update that has "KB925902" in the name.

    13) Click the 'Download' button.

    14) You will be given the choice to Save or Run, select Run

    15) Reboot 2 times. 

     

    Or

     

    C) Repair Windows using System Restore:

     

    1) Reboot Vista into Safe Mode

    2) Go to Control Panel

    3) On the left hand side of the Control Panel window, Click on "Classic View"

    4) Double-click "Backup and Restore Center"

    5) On the left hand side of the window, click "Repair Windows using system restore"

    6) Select "Choose Different Restore Point", Put a check in the box that says "Show restore points older than 5 days", select the restore point that corresponds to the date Before you first noticed the issue.

    7) Click the "Next" button.

    8) Reboot back into Normal mode

    9) Vista should no longer be in Reduced Functionality mode

     

     And lastly, if none of these suggestions resolves your issue, open a (no cost) support request at http://go.microsoft.com/fwlink/?linkid=52029 for additional assistance.

     

    Thank you,

    Darin Smith

    WGA Forum Manager

    Friday, June 20, 2008 7:31 PM
  • Also, to tell if you have SP1 installed or not, look at your Diagnostic Report for the line that reads: "Build lab:"

     

    If the Build Lab shows 6000.vista_gdr.071023-1545 (as yours does) then you do not have SP1 installed.

    If the Build Lab shows 6001.longhorn.080101-1935 (or similar) then you do have SP1 installed.

     

     

    Darin

    Friday, June 20, 2008 7:36 PM