locked
Validation Error and Windows Will Not Start - Diagnostic Results RRS feed

  • Question

  • I would appreciate a timely response how to fix this.  I cannot use my computer, which was bought directly from Dell and is very new.

     

     

    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: *****-*****-F4GJK-KG77H-B9HD2
    Windows Product Key Hash: iJAth4TbScMi8HdcPurlASXdEkw=
    Windows Product ID: 89578-OEM-7332157-00204
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6000.2.00010300.0.0.003
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {C9E8250D-9BBB-46A7-8253-F8945945321F}(1)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.7.69.2
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6000.vista_gdr.071009-1548
    TTS Error: M:20080615145006248-
    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 Home and Student 2007 - 100 Genuine
    OGA Version: Registered, 1.6.28.0
    Signed By: Microsoft
    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\dnsapi.dll[6.0.6000.16615]
    File Mismatch: C:\Windows\system32\oleaut32.dll[6.0.6000.16607]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{C9E8250D-9BBB-46A7-8253-F8945945321F}</UGUID><Version>1.7.0095.0</Version><OS>6.0.6000.2.00010300.0.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-B9HD2</PKey><PID>89578-OEM-7332157-00204</PID><PIDType>2</PIDType><SID>S-1-5-21-942650028-2826268872-3929966280</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>MXC061                          </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A10</Version><SMBIOSVersion major="2" minor="4"/><Date>20070402000000.000000+000</Date></BIOS><HWID>29303507018400FE</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><OEMID>DELL  </OEMID><OEMTableID>M07    </OEMTableID></OEM><BRT/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><Val>1E0774FA83D3DB0</Val><Hash>xblxvrPlQ19E9VAQXW1DbJEE6GA=</Hash><Pid>81602-OEM-6872813-56815</Pid><PidType>4</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAIwKAAAAAAAAYWECADAgAABADY2np83IAdArSr9MLECc5R83cvYPeMyKvJ4gbJZeuW2OwsnEkM8xe6dtCUhAVRCQvKIaF2SYovmA2FF124VnPMn56Nv0G9FrZfndP4GBmNtBuDTRju3JGD817S8Cu1HUlGNHVFBLTl0BpRsD6Dwtx6AnxzEU2ImHkFGGR5j2BWyOcad6J+yR0nMat38/Ij8WvwlN0LR706J/AdUP4L3wi2m/Gi/9qyM7UcmmKQdXOYNsqcu4BNLbM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMdDbFhDEWg4XhFW0h9zt9jw3fFy8q69Qp1rEmLFWn3bX5gNhRdduFZzzJ+ejb9BvRkCy7HgbdWudfUsiMxOvVohg/Ne0vArtR1JRjR1RQS05dAaUbA+g8LcegJ8cxFNiJh5BRhkeY9gVsjnGneifskdJzGrd/PyI/Fr8JTdC0e9OifwHVD+C98Itpvxov/asjO1HJpikHVzmDbKnLuATS2zOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zBgVr5+9sraMXhzI6Y3HUTqK0ohTmIqL440/krNz+MH++YDYUXXbhWc8yfno2/Qb0Qv7jeOxl8jpuVQRSnk9tl0YPzXtLwK7UdSUY0dUUEtOXQGlGwPoPC3HoCfHMRTYiYeQUYZHmPYFbI5xp3on7JHScxq3fz8iPxa/CU3QtHvTon8B1Q/gvfCLab8aL/2rIztRyaYpB1c5g2ypy7gE0tszkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDA==

     

    Sunday, June 15, 2008 8:16 PM

Answers

  • Hi BubbaScales,

     

     

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

     

    File Scan Data-->

    File Mismatch: C:\Windows\system32\dnsapi.dll[6.0.6000.16615]

    File Mismatch: C:\Windows\system32\oleaut32.dll[6.0.6000.16607]

     

    This line means that the critical system fileseither

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

    Or

    b)     The files have recently been updated but the file's Signature Hash was not updated, in Vista's System Catalog to reflect the updated dnsapi.dll 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.

     

       In the case of the Critical System file dnsapi.dll, on April 8th 2008, Windows Update released Update KB945553. One of the things that this update did was to update Critical System file dnsapi.dll. We believe that, in some rare cases, after the Update updated dnsapi.dll, it failed to update Vista's System Catalog with the file's new Signature Hash.

     

      As for oleaut32.dll there are a number of Updates that contain that file, but none of them were released recently.  So, it may have been caused the same way as the dnsapi.dll file, but I think the more likely cause that some other (non-Update related) event occured to modify or make that file corrupt.

     

      However the issue was caused, the fix is to either repair the bad files or replace them with known-good ones.

     

    1A)    Uninstall/Reinstall Update KB945553 (dnsapi.dll): 

    By doing this, you will overwrite the bad dnsapi.dll with a known-good copy

     

    1.     Reboot Vista into Safe Mode

    2.     Go to Control Panel

    3.     On the left hand side of the Controlee panel window, Click on "Classic View"

    4.     Double-click "Programs and Features"

    5.     On the left hand side, under "Tasks" click "View installed updates"

    6.     Sort the updates by "Installed On" date

    7.     Find the Updates installed on (or after) April 8th

    8.     Find the Updated titled "Security Update for Windows Vista (KB945553)"

    9.     Right-Click on the Update and select "Uninstall"

    10.   Reboot into normal mode

    11.   Vista should no longer be in Reduced Functionality mode

     

    12.   You can manually reinstall Update KB945553 by going to http://download.microsoft.com and search for KB945553. Then pick the update that has KB945553 in the name and that applys to your version of Windows.  click the "Download" button, then click "open" (if any other windows pop-up, click the 'Allow" or Continue" button.

    13.   When the update is complete, reboot the computer. When the computer reboots, you should see a screen that says something like "Configuring Update..." Do not turn off or reboot your computer until Vista has completed configuring the update.

     

    1B)    Uninstall/Reinstall Update KB938371, KB943055 or KB943899(oleut.dll): 

    oleut.dll comes in a number of updates, try each till the issue is resolved

    1.     Follow the same steps as in 1A for KB938371, KB943055 or KB943899

     

    Or

     

    2)    Repair Windows using System Restore:

    1.     Reboot Vista into Safe Mode

    2.     Go to Control Panel

    3.     On the left hand side of the Controlee 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"

                                              i.    If the last thing that you installed was Update KB945553, then select the "Recommended Restore"

                                             ii.    If you have since installed other software, drivers or updates, then 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 you installed Update KB945553 (would be around April 8th or after).

    6.     Click the "Next" button.

    7.     Reboot back into Normal mode

    8.     Vista should no longer be in Reduced Functionality mode

     

    9.     You can manually reinstall Update KB945553 by going to http://www.microsoft.com/downloads/details.aspx?FamilyID=8203d303-c855-4579-9bbf-b06ddf5c1b87&DisplayLang=en  click the "Download" button, then click "open" (if any other windows pop-up, click the 'Allow" or Continue" button.

    10.   When the update is complete, reboot the computer. When the computer reboots, you should see a screen that says something like "Configuring Update..." Do not turn off or reboot your computer until Vista has completed configuring the update.

     

    3)    Repair Windows using System Restore:

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

     

    Thank you,

    Darin Smith

    WGA Forum Manager

    Monday, June 16, 2008 11:16 PM