locked
Unauthorized change to Windows RRS feed

  • Question

  • Hello there,

    New Dell XPS M1330 with Vista Ultimate - have been having problems with installing the Palm Desktop for my wife's Palm.  Uninstalling the software and rebooting landed me in this state.

    Here's my diagnostic report - any help would be greatly appreciated.

    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: *****-*****-9364X-37XGX-24W6P
    Windows Product Key Hash: aA067NOL80NWIZ94L6hWVdZMoIo=
    Windows Product ID: 89580-OEM-7332132-00141
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6001.2.00010100.1.0.001
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {7A03B939-0FEB-43AC-93F1-8A1DC99FA901}(1)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Ultimate
    Architecture: 0x00000000
    Build lab: 6001.vistasp1_gdr.080425-1930
    TTS Error: M:20080810171409299-
    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 Professional Edition 2003 - 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\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-->
    File Mismatch: C:\Windows\system32\gdi32.dll[6.0.6001.18023]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{7A03B939-0FEB-43AC-93F1-8A1DC99FA901}</UGUID><Version>1.7.0095.0</Version><OS>6.0.6001.2.00010100.1.0.001</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-24W6P</PKey><PID>89580-OEM-7332132-00141</PID><PIDType>2</PIDType><SID>S-1-5-21-135809689-2858099741-126869846</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>XPS M1330                       </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A11</Version><SMBIOSVersion major="2" minor="4"/><Date>20080619000000.000000+000</Date></BIOS><HWID>37313507018400FA</HWID><UserLCID>1009</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL  </OEMID><OEMTableID>M08    </OEMTableID></OEM><BRT/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91110409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>9ABBDC2E49675DE</Val><Hash>3+4WM3rmFPNs4g0Xvvuxxkgn/QI=</Hash><Pid>70145-751-4723156-57479</Pid><PidType>1</PidType></Product></Products><Applications><App Id="15" Version="11" Result="100"/><App Id="16" Version="11" Result="100"/><App Id="18" Version="11" Result="100"/><App Id="19" Version="11" Result="100"/><App Id="1A" Version="11" Result="100"/><App Id="1B" Version="11" Result="100"/><App Id="44" Version="11" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAANIHAAAAAAAAYWECAASQSoi4U8ZIJfvIAdArSr9MLECc5R83cvYPeMyACmQ5Y1IqvJLFPm9nZ+rWRxa2H2kKWNa4VVmqJRtX+6CoTUWXhhgs1m231mF4QnBCZkj01LUhzjw/989ILwHc27OKLWTN3/xFyngmD3afWQd5BWut+vD3FqOkH5qwY3q1CzF0U07jqdyoAL0aULPNP9KSju/t9vu9LXUgneZO8FY4AE64zboqR4C2wZdpMQu8VjbvFjoDZ5k4mh5m+ukRM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMNLEOxTUzdvO4GZf4iLV2GTByCj4L+8KP0WPvSgY7VICgqE1Fl4YYLNZtt9ZheEJw2cyzpItQ1k9IRyR2ndrrStuzii1kzd/8Rcp4Jg92n1kHeQVrrfrw9xajpB+asGN6tQsxdFNO46ncqAC9GlCzzT/Sko7v7fb7vS11IJ3mTvBWOABOuM26KkeAtsGXaTELvFY27xY6A2eZOJoeZvrpETOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zCVjY+7lUBb0g/iI7igCmAZwNioP3j5bdOS5I1JvWFmRoKhNRZeGGCzWbbfWYXhCcI0/TvKxgtGiUTyTHYzMQUrbs4otZM3f/EXKeCYPdp9ZB3kFa6368PcWo6QfmrBjerULMXRTTuOp3KgAvRpQs80/0pKO7+32+70tdSCd5k7wVjgATrjNuipHgLbBl2kxC7xWNu8WOgNnmTiaHmb66REzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMxX5w/BChIHXOaCRZd6qsMzRZYRUGKdoBVi1Y3QvFItXKCoTUWXhhgs1m231mF4QnCTf/TYxDIcmaQZ2tLmq8CV27OKLWTN3/xFyngmD3afWQd5BWut+vD3FqOkH5qwY3q1CzF0U07jqdyoAL0aULPNP9KSju/t9vu9LXUgneZO8FY4AE64zboqR4C2wZdpMQu8VjbvFjoDZ5k4mh5m+ukRM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=


    Sunday, August 10, 2008 9:28 PM

Answers

  •  
    Hello ayang_ca,

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

    File Scan Data-->
    File Mismatch: C:\Windows\system32\gdi32.dll[6.0.6001.18023]

    This line means that the critical system file gdi32.dllhas 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 gdi32.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 gdi32.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

     


    Attention Forum All Users: Please Do Not post your issue in someone else's Thread...Create your own.
    Monday, August 11, 2008 9:02 PM
  •  No, there are no other steps to 'stay' at a past restore point. 

     It sounds like once you restore to the past restore point, the issue is resolved, for a bit, but then re-occures.

     The only thing I can think of that could cause that to happen is if the issue was originally caused by a bad Update install. And then, after your restore, the same Update automaticly re-downloads, re-installs and (for some reason) re-fails.

     If this is, in fact, what is happening, then to avoid it, I suggest (temporarily) resetting Windows Update to NOT Automaticly install updates. To do this, first return to the past, good, restore point. (The issue should no longer be occuring, at this point) 

      Next, click the 'Start' button and type in "Windows Update" and hit 'Enter'. Once in the Windows Update window, click the "Change Settings" and select the "Download Updates but let me choose whether to install them" option.

      Once Windows finds available updates, only install one at a time (reboot after each update install). 

      At this point, one of two things may happen:

    1) Installing the Update, by itself, may allow the update to unstall without failing and your issue would be resolved. (After a good amount of time, you could then reset the Update setting back to Automatic)
    or
    2) After installing one of the Updates, the issue re-occures. This is a good/bad situation because your again have the issue, but now you know and Updated did, infact, cause the issue and you know which Update did it.

     You can then return to the good restore point and then go to http://download.microsoft.com and maunally download and install the Standalone version of the Update that was causing the problem. The Standalone version should Not fail during install.



    Just to be clear, I do not know that an update is causing this problem. The steps I provided above are to help prove/disprove if an update is causing the issue and, if it is, how to workaround it. 

    Also, even if your particular issue may have been caused by an Update, don't be fearfull of installing future updates. This is a very rare issue and the benefits of the updates outweighs the low possibility of this issue re-occuring.




    Hope that halps,
    Darin
    Attention Forum All Users: Please Do Not post your issue in someone else's Thread...Create your own.
    • Marked as answer by Darin Smith MS Tuesday, August 12, 2008 5:31 PM
    • Edited by Darin Smith MS Tuesday, August 12, 2008 5:37 PM added additional info
    Tuesday, August 12, 2008 5:30 PM

All replies

  •  
    Hello ayang_ca,

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

    File Scan Data-->
    File Mismatch: C:\Windows\system32\gdi32.dll[6.0.6001.18023]

    This line means that the critical system file gdi32.dllhas 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 gdi32.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 gdi32.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

     


    Attention Forum All Users: Please Do Not post your issue in someone else's Thread...Create your own.
    Monday, August 11, 2008 9:02 PM
  • Hi Darin,

    Thanks very much for your response. I've created a support request as per your suggestion.

    Unfortunately, the Vista SP1  installed at the link above ends early telling me that I already have SP1 installed.

    Now, the interesting thing is that I saw advice you have elsewhere in the forums and I went through the process of going back through previous restore points until I got one that worked.  I believe it rebooted fine once or twice after I found a restore point that worked, but when my wife booted up her laptop tonight, I was back to square one (natch).

    There isn't anything else I need to do to stay at a restore point is there?  Shouldn't the system be fine once I restore to an earlier point?

    Thanks,
    Andy
    Tuesday, August 12, 2008 12:32 AM
  •  No, there are no other steps to 'stay' at a past restore point. 

     It sounds like once you restore to the past restore point, the issue is resolved, for a bit, but then re-occures.

     The only thing I can think of that could cause that to happen is if the issue was originally caused by a bad Update install. And then, after your restore, the same Update automaticly re-downloads, re-installs and (for some reason) re-fails.

     If this is, in fact, what is happening, then to avoid it, I suggest (temporarily) resetting Windows Update to NOT Automaticly install updates. To do this, first return to the past, good, restore point. (The issue should no longer be occuring, at this point) 

      Next, click the 'Start' button and type in "Windows Update" and hit 'Enter'. Once in the Windows Update window, click the "Change Settings" and select the "Download Updates but let me choose whether to install them" option.

      Once Windows finds available updates, only install one at a time (reboot after each update install). 

      At this point, one of two things may happen:

    1) Installing the Update, by itself, may allow the update to unstall without failing and your issue would be resolved. (After a good amount of time, you could then reset the Update setting back to Automatic)
    or
    2) After installing one of the Updates, the issue re-occures. This is a good/bad situation because your again have the issue, but now you know and Updated did, infact, cause the issue and you know which Update did it.

     You can then return to the good restore point and then go to http://download.microsoft.com and maunally download and install the Standalone version of the Update that was causing the problem. The Standalone version should Not fail during install.



    Just to be clear, I do not know that an update is causing this problem. The steps I provided above are to help prove/disprove if an update is causing the issue and, if it is, how to workaround it. 

    Also, even if your particular issue may have been caused by an Update, don't be fearfull of installing future updates. This is a very rare issue and the benefits of the updates outweighs the low possibility of this issue re-occuring.




    Hope that halps,
    Darin
    Attention Forum All Users: Please Do Not post your issue in someone else's Thread...Create your own.
    • Marked as answer by Darin Smith MS Tuesday, August 12, 2008 5:31 PM
    • Edited by Darin Smith MS Tuesday, August 12, 2008 5:37 PM added additional info
    Tuesday, August 12, 2008 5:30 PM