locked
Unauthorized change to windows RRS feed

  • Question

  •  Little background on the problem, PSU went out in Comp and switched over to new case, one of the drives of a swRAID5 array wasn't plugged in properly so system started in degraded mode but booted in to windows vista fine then after update reboot with new update get this message of unauthorized change, I am extremely unhappy with this. Complete rebuild of array but still this ____ comes up. 

    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: *****-*****-949V4-6P9B8-47MYP
    Windows Product Key Hash: XN79QAgaDNvQE8VINQcBx9Mw8mM=
    Windows Product ID: 89580-OEM-7300542-23666
    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: {DAC4ABB0-32FF-4665-9D40-3D88F1BBAF43}(1)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.7.69.2
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Ultimate
    Architecture: 0x00000000
    Build lab: 6000.vista_gdr.071023-1545
    TTS Error: M:20080912232138181-
    Validation Diagnostic:
    Resolution Status: N/A

    WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: 6.0.6002.16398

    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 Standard 2007 - 100 Genuine
    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\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>{DAC4ABB0-32FF-4665-9D40-3D88F1BBAF43}</UGUID><Version>1.7.0095.0</Version><OS>6.0.6000.2.00010100.0.0.001</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-47MYP</PKey><PID>89580-OEM-7300542-23666</PID><PIDType>3</PIDType><SID>S-1-5-21-79407290-1746774850-2365561088</SID><SYSTEM><Manufacturer>NVIDIA</Manufacturer><Model>AWRDACPI</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>6.00 PG</Version><SMBIOSVersion major="2" minor="2"/><Date>20060406000000.000000+000</Date></BIOS><HWID>91303507018400F6</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><BRT/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0012-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Standard 2007</Name><Ver>12</Ver><Val>7864B78EFFE4710</Val><Hash>T3pvuJMgTZ8AktN9JExqSnTbVQc=</Hash><Pid>81607-904-4713184-64762</Pid><PidType>1</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" 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: U1BMRwEAAAAAAQAABAAAAMoXAAAAAAAAWmICADAgAAB6aXCU2BTJAdArSr9MLECc5R83cvYPeMxqNc7pJrUUbIJGs1GKH+gYojXHJHLzmoRmDJB0JzW2kisMPgesORnDUv5v8xZITziGiySoT6BSpBonynGbGg8AGD817S8Cu1HUlGNHVFBLTl0BpRsD6Dwtx6AnxzEU2IlE7oPk/SPeaYoTWCOSbwhb0nMat38/Ij8WvwlN0LR7075lEnTDuN88OYnM4xG1aQcN9TFRMCUKDVZZnS95CyflM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMCWCQnxm4d4P3UZAfywXMLUsYdoBNLRRVb77mp3ulVHMrDD4HrDkZw1L+b/MWSE84whhe51a9GPrfphz4bAvulxg/Ne0vArtR1JRjR1RQS05dAaUbA+g8LcegJ8cxFNiJRO6D5P0j3mmKE1gjkm8IW9JzGrd/PyI/Fr8JTdC0e9O+ZRJ0w7jfPDmJzOMRtWkHDfUxUTAlCg1WWZ0veQsn5TOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zCG4NPJiwyXr1+sQUvl88go9CWgIIu6XyZXbSfZPbVmoKww+B6w5GcNS/m/zFkhPOL7vNdVnJ81Co9vhq1kLLIwYPzXtLwK7UdSUY0dUUEtOXQGlGwPoPC3HoCfHMRTYiUTug+T9I95pihNYI5JvCFvScxq3fz8iPxa/CU3QtHvTvmUSdMO43zw5iczjEbVpBw31MVEwJQoNVlmdL3kLJ+UzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMzxpVls8XgfkSfyEMEQRxa5sb/rcdrl4RlDCp4CtKQ9TSsMPgesORnDUv5v8xZITzii/11PltnrABkqkqSESEXeGD817S8Cu1HUlGNHVFBLTl0BpRsD6Dwtx6AnxzEU2IlE7oPk/SPeaYoTWCOSbwhb0nMat38/Ij8WvwlN0LR7075lEnTDuN88OYnM4xG1aQcN9TFRMCUKDVZZnS95CyflM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jM7pvkPjMcKAssulNHSOpslygbFtAxQSsYjYErBywLyv8rDD4HrDkZw1L+b/MWSE84/gtpQAH9wsUl0n33hACuORg/Ne0vArtR1JRjR1RQS05dAaUbA+g8LcegJ8cxFNiJRO6D5P0j3mmKE1gjkm8IW9JzGrd/PyI/Fr8JTdC0e9O+ZRJ0w7jfPDmJzOMRtWkHDfUxUTAlCg1WWZ0veQsn5TOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM



    • Changed type Stephen Holm Monday, September 15, 2008 5:24 PM Changed to a question
    Saturday, September 13, 2008 6:40 AM

Answers

  • Hello Onlyoneskwalla,

    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 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 may 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 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 an 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, 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,


    Stephen Holm, MS
    WGA Forum Manager 

     

     

    Type:  rpcrt4.dll

    Symptoms:

    ·         Has Spsys.log Contents

    ·         Has a TTS that starts with “M” (example M:20080226114924778-)

    ·         Have any Mismatched files listed under “File Scan Data-->”

    ·         The Mismatched file Must be rpcrt4.dll

     

    Resolution Steps:

     

    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.

     

      From your Diagnostic Report, I see you have a On Disk type Mod-Auth. Meaning there is a critical system file (in your case rpcrt4.dll) that has either been Modified or has become Corrupt. You can see this file listed in your Diagnostic Report by looking for the words "File Mismatch:" under the "File Scan Data-->" line

     

        To resolve the issue, we need to replace the bad file with a unmodified/uncorrupted (known good) copy. You have two options to choose from, to do this:

     

    A) Re-install a past Update that contains this file, which for file rpcrt4.dll would be update KB933729. Unfortunately, most Vista updates can only be installed once. If you were to try to install an update that has already been installed on a system, you will usually get the error "This update does not apply to your system". So, to get around this, you will need to uninstall the update and then re-install the update. To do so, please follow the below steps:

     

    1)  Try installing update KB933729  from this link http://www.microsoft.com/downloads/details.aspx?FamilyID=ceca7f8c-7b56-48fc-8c17-87ffadf25629&DisplayLang=en if you receive the error "This update does not apply to your system" then Vista isn't going to allow you to re-install this update, so you will need to uninstall it first, then reinstall. (Continue to step 2)

     

    2) Log into Vista in Safe Mode

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

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

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

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

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

    8) Right-Click on the update 'KB933729' and select 'Unistall'.

    9) Reboot into Normal Mode

    10) Install update KB933729  from this link http://www.microsoft.com/downloads/details.aspx?FamilyID=ceca7f8c-7b56-48fc-8c17-87ffadf25629&DisplayLang=en

     

     

    B) Install Service Pack 1 for Vista (found at http://www.microsoft.com/downloads/details.aspx?FamilyID=b0c7136d-5ebb-413b-89c9-cb3d06d12674&DisplayLang=en). File rpcrt4.dll should be included in the SP1 install.

    (Note: this is the simpler way to resolve, but be aware that I have not received confirmation that rpcrt4.dll is, in fact, included in SP1. So if this option does not resolve the issue, please see option A).

     

     

    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

     

    Thank you,

    Darin Smith

    WGA Forum Manager

     

     

     

    Type:  slc.dll

    Symptoms:

    ·         Has Spsys.log Contents

    ·         Has a TTS that starts with “M” (example M:20080226114924778-)

    ·         Have any Mismatched files listed under “File Scan Data-->”

    ·         The Mismatched file Must be slc.dll

     

    Resolution Steps:

    The core to your particular issue centers on the line in your Diagnostic Report, that reads:

     

    File Scan Data-->

    File Mismatch: C:\Windows\system32\slc.dll[6.0.6000.16509]



    This line means that the critical system file slc.dll has either

    a)     Been tampered/modified/become corrupt to the point that its Signature Hash no longer matches the Signature Hash listed in Vista's System Catalog.

    Or

    b)     Been updated but the file's Signature Hash was not updated, in Vista's System Catalog to reflect the updated file's new Signature Hash.

     

      Vista compares a Critical System file's Signature Hash with the Signature Hash listed in its System Catalog to determine if that Critical System file has been tampered with. When this happens, depending on the file that has been tampered, Vista may show as Genuine or Non-Genuine, but either way, Vista won't Validate correctly and may also exhibit other strange behavior.

     

      To resolve your issue, we need to replace or repair the file so it's Signature Hash matches what is listed in Vista System Catalog. I can provide a couple of suggestions to do this:

     

    A)    Install Service Pack 1 for Vista (found at http://www.microsoft.com/downloads/details.aspx?FamilyID=b0c7136d-5ebb-413b-89c9-cb3d06d12674&DisplayLang=en). File slc.dll may be included in the SP1 install and if so, SP1 will overwrite the bad file with a Known-Good copy.

     

    (Note: this is the simpler way to resolve, but be aware that I have not received confirmation that slc.dll.dll is, in fact, included in SP1. So if this option does not resolve the issue, please see option B).

     

    B)    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

     

       If neither of these solutions resolves your issue, the last resort, that I can provide, is to reinstall Vista. But before you do that, create a (no cost) support request at http://go.microsoft.com/fwlink/?linkid=52029 and see if they can provide any alternatives.

     

    Thank you,

    Darin Smith

    WGA Forum Manager
    Stephen Holm
    • Marked as answer by Stephen Holm Monday, September 15, 2008 5:38 PM
    Monday, September 15, 2008 5:36 PM