locked
Invalid key error after latest updates RRS feed

  • Question

  •  

    I have an Acer laptop that has Vista Home edition preinstalled.  After processing the Vista updates yesterday the computer fails to start.  It simply gives an error saying that an unauthorized change has been detected and the option to validate.  The validation fails.  The results of the WGA diagnostics tool is:

     

    Diagnostic Report (1.7.0069.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0x80070426
    Cached Validation Code: N/A, hr = 0x80004005
    Windows Product Key: *****-*****-XY9X3-JDXYP-6CJ97
    Windows Product Key Hash: xFQJU8srKsovk6p1Lk1yW93in4E=
    Windows Product ID: 89578-OEM-7332157-00211
    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: {67E8A13C-6355-4BF9-9FBB-C5090AE076B1}(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:20080410034608535-
    Validation Diagnostic:
    Resolution Status: N/A

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

    Notifications Data-->
    Cached Result: N/A
    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 Data-->
    Office Status: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: FCEE394C-2920-80070002_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\gdi32.dll[6.0.6000.16643]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{67E8A13C-6355-4BF9-9FBB-C5090AE076B1}</UGUID><Version>1.7.0069.0</Version><OS>6.0.6000.2.00010300.0.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-6CJ97</PKey><PID>89578-OEM-7332157-00211</PID><PIDType>2</PIDType><SID>S-1-5-21-1173709415-1901758107-3760628354</SID><SYSTEM><Manufacturer>Acer            </Manufacturer><Model>Aspire 5610Z    </Model></SYSTEM><BIOS><Manufacturer>Acer</Manufacturer><Version>V3.50</Version><SMBIOSVersion major="2" minor="33"/><Date>20070213000000.000000+000</Date></BIOS><HWID>49323507018400EE</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>ACRSYS</OEMID><OEMTableID>ACRPRDCT</OEMTableID></OEM><BRT/></MachineData><Software><Office><Result>109</Result><Products/></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAADgTAAAAAAAAYWECADAgAAC1huoBTprIAdArSr9MLECc5R83cvYPeMyAQlEXjkU56TisGtil1G4nKSdmrIlw6bXczcRtvy8rB6CoTUWXhhgs1m231mF4QnDYO7HiGsIvXqfT5xpvbVlg27OKLWTN3/xFyngmD3afWQd5BWut+vD3FqOkH5qwY3oKzOF7eXdqQzOdQlJCgYTeP9KSju/t9vu9LXUgneZO8FY4AE64zboqR4C2wZdpMQu8VjbvFjoDZ5k4mh5m+ukRM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMnlll5kLxTgtydSQqscj+m1evCaiqozJX/fqPyS3ZNUSgqE1Fl4YYLNZtt9ZheEJwkKW7oVifQjIeuHnUHzOtgduzii1kzd/8Rcp4Jg92n1kHeQVrrfrw9xajpB+asGN6Cszhe3l3akMznUJSQoGE3j/Sko7v7fb7vS11IJ3mTvBWOABOuM26KkeAtsGXaTELvFY27xY6A2eZOJoeZvrpETOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zAMED4wm8emQgSEA7YMtoYrI574ljRORbajG3DegCpcEoKhNRZeGGCzWbbfWYXhCcHq9NgvE/OUiPnpgSB53mBHbs4otZM3f/EXKeCYPdp9ZB3kFa6368PcWo6QfmrBjegrM4Xt5d2pDM51CUkKBhN4/0pKO7+32+70tdSCd5k7wVjgATrjNuipHgLbBl2kxC7xWNu8WOgNnmTiaHmb66REzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMytC3oI7uELz5b1N7BB6hiGhG0gYL8EYIq7lr/fGjYGk6CoTUWXhhgs1m231mF4QnB6vTYLxPzlIj56YEged5gR27OKLWTN3/xFyngmD3afWQd5BWut+vD3FqOkH5qwY3oKzOF7eXdqQzOdQlJCgYTeP9KSju/t9vu9LXUgneZO8FY4AE64zboqR4C2wZdpMQu8VjbvFjoDZ5k4mh5m+ukRM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMFkyu+/VIdpKGPhtDiu23IdiebDjA+y471aLPqn+KjYCgqE1Fl4YYLNZtt9ZheEJwxHplEz3FaE97WV30+XnGZ9uzii1kzd/8Rcp4Jg92n1kHeQVrrfrw9xajpB+asGN6Cszhe3l3akMznUJSQoGE3j/Sko7v7fb7vS11IJ3mTvBWOABOuM26KkeAtsGXaTELvFY27xY6A2eZOJoeZvrpETOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zMyIJACjTx02EvO0tl4b2w0p9Iek0Jo59hR6Ix+vadP6oKhNRZeGGCzWbbfWYXhCcIRNJI35ZvHkF2UzFrMHf1Dbs4otZM3f/EXKeCYPdp9ZB3kFa6368PcWo6QfmrBjegrM4Xt5d2pDM51CUkKBhN4/0pKO7+32+70tdSCd5k7wVjgATrjNuipHgLbBl2kxC7xWNu8WOgNnmTiaHmb66REzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMz1wJDePSoigXQKNWD7KwtgysgLM5uI9N4S4LciSQ+Z06CoTUWXhhgs1m231mF4QnDHgCHLEm/Me03Fq3uHjzRy27OKLWTN3/xFyngmD3afWQd5BWut+vD3FqOkH5qwY3oKzOF7eXdqQzOdQlJCgYTeP9KSju/t9vu9LXUgneZO8FY4AE64zboqR4C2wZdpMQu8VjbvFjoDZ5k4mh5m+ukRM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

     

     

    Any help would be greatly appreciated.

    Thursday, April 10, 2008 11:48 PM

Answers

  • 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 did 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 file listed under the "File Scan Data-->" line of your Diagnostic Report, your issue is an On Disk Mod-Auth. The Mismatched file (gdi32.dll) is the file that has been Modified or has become corrupted.

     

      Normally, I would just have you re-install a past update that contained the file. This would replace the bad file with an unmodified/corrupted copy. But I am unable to find any update that contains file gdi32.dll. Therefor I am only able to suggest 2 other options and neither are very good.

     

    1) You can try installing Service Pack 1 for Vista (http://www.microsoft.com/downloads/details.aspx?FamilyID=b0c7136d-5ebb-413b-89c9-cb3d06d12674&DisplayLang=en). I do not know for sure, but it is possible that file gdi32.dll could be included in SP1. If it is, your issue will be resolved, but if it doesn't, then you will have to go to option 2

     

    2) Reinstall Vista. I don't like suggesting this, but I know of no other way to replace that file and untill that file is replaced or repaired, this issue will continue.

     

    Sorry I couldn't be more help

    Darin Smith

    WGA Forum Manager

     

    Friday, April 11, 2008 12:06 AM
  • Hello Ironbreeze,

     

      Computers built by large manufacturers, that come with Vista Pre-installed come with Windows Restore software that allows the user to return Vista back to how it was from the factory. The Windows Restore software may be on a CD/DVD or it may be in a partition on the computer's hard drive. Please see the documentation, that came with your computer, (or contact the computer manufacturer) in conducting the Windows Restore process. 

     

      It sounds like there may have been an error while applying those updates you installed. It is most likely the cause of this file being Modified/Corrupted.  There is another option you may try. There is a function in Vista that allows you to repair back to a past Restore Point. Meaning you could restore to a point prior to when you installed those updates (Note: This is different then the Windows Restore process that I describe above)

      To do a System Restore to a past Restore Point, reboot your computer into Safe Mode. Once in safe mode, go to the Control Panel then double click "Backup and Restore Center". In the "Backup and Restore Center" windows, click "Repair Windows using System Restore" (listed under "Tasks" on the left hand side of the window). Follow the directions to undo the Update install. After that is done, try re-instaling the updates and see if they install correctly, this time.  If you re-install the updates and get the same issue, you may want to contact Windows Update suport at http://support.microsoft.com/ph/6527 or go to http://support.microsoft.com for further Vista support options.

     

      If the System Restore to a past Restore Point doesn't resolve your issue, my only other suggestion is to re-install using the Windows Restore software, included with your computer.

     

     Ironbreeze wrote:

    .  Something interesting however is that I compared the product key on the sticker on the bottom of the laptop and it does not match the wga product key being reported.  I then ran wga on this computer and compared the reported product key with the sticker and it doesn't match either, however everything checks out fine on this computer so that may be a red herring as far as my current problem is concerned.

     

      This is normal and expected. Computers built by large manufacturers, that come with Vista Pre-installed come with two (2) Product Keys:

     

     

    1) OEM SLP: This key come in Vista when it comes from the Factory. This key is geared to work with the special instructions found only on that Manufacturer's computer hardware. So when Vista was installed using the OEM SLP key  (at the factory) Vista looks at the motherboard and see the special instructions and Activates itself. (that's why you did not need to Activate your computer after you brought it home)

     

    2) COA SLP: This is the Product key that you see on the sticker on the side of your computer. It's a valid product key, but should only be used in limited situations. The key does require activation, but you must Activate by Phone.

     

      You can see in your Diagnostic Report that your Vista currently is using the OEM SLP key, therefore it will not match the COA SLP key, listed on the sticker on the side of your computer. 

     

      

    Thank you,

    Darin Smith

    WGA Forum Manager

    Friday, April 11, 2008 6:21 PM

All replies

  • 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 did 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 file listed under the "File Scan Data-->" line of your Diagnostic Report, your issue is an On Disk Mod-Auth. The Mismatched file (gdi32.dll) is the file that has been Modified or has become corrupted.

     

      Normally, I would just have you re-install a past update that contained the file. This would replace the bad file with an unmodified/corrupted copy. But I am unable to find any update that contains file gdi32.dll. Therefor I am only able to suggest 2 other options and neither are very good.

     

    1) You can try installing Service Pack 1 for Vista (http://www.microsoft.com/downloads/details.aspx?FamilyID=b0c7136d-5ebb-413b-89c9-cb3d06d12674&DisplayLang=en). I do not know for sure, but it is possible that file gdi32.dll could be included in SP1. If it is, your issue will be resolved, but if it doesn't, then you will have to go to option 2

     

    2) Reinstall Vista. I don't like suggesting this, but I know of no other way to replace that file and untill that file is replaced or repaired, this issue will continue.

     

    Sorry I couldn't be more help

    Darin Smith

    WGA Forum Manager

     

    Friday, April 11, 2008 12:06 AM
  • Ok, tried the sp1 update but still have a problem with the gdi32.dll.  As for reinstalling Vista no disk came with the laptop not to mention all the other software/data that would need to be reinstalled/restored.  I have another laptop that doesn't have a problem after the update, therefore a "non-corrupt" gdi32.dll.  I could copy the good dll over to this computer but access is denied.  Here's the another wga diag dump after installing the sp1.

     

    Diagnostic Report (1.7.0069.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0x80070426
    Cached Validation Code: N/A, hr = 0x80070426
    Windows Product Key: *****-*****-XY9X3-JDXYP-6CJ97
    Windows Product Key Hash: xFQJU8srKsovk6p1Lk1yW93in4E=
    Windows Product ID: 89578-OEM-7332157-00211
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6001.2.00010300.1.0.003
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {67E8A13C-6355-4BF9-9FBB-C5090AE076B1}(3)
    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: 6001.longhorn_rtm.080118-1840
    TTS Error: M:20080410203644413-
    Validation Diagnostic:
    Resolution Status: N/A

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

    Notifications Data-->
    Cached Result: N/A
    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 Data-->
    Office Status: 109 N/A
    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\gdi32.dll[6.0.6001.18023]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{67E8A13C-6355-4BF9-9FBB-C5090AE076B1}</UGUID><Version>1.7.0069.0</Version><OS>6.0.6001.2.00010300.1.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-6CJ97</PKey><PID>89578-OEM-7332157-00211</PID><PIDType>2</PIDType><SID>S-1-5-21-1173709415-1901758107-3760628354</SID><SYSTEM><Manufacturer>Acer            </Manufacturer><Model>Aspire 5610Z    </Model></SYSTEM><BIOS><Manufacturer>Acer</Manufacturer><Version>V3.50</Version><SMBIOSVersion major="2" minor="33"/><Date>20070213000000.000000+000</Date></BIOS><HWID>49323507018400EE</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>ACRSYS</OEMID><OEMTableID>ACRPRDCT</OEMTableID></OEM><BRT/></MachineData><Software><Office><Result>109</Result><Products/></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAADgTAAAAAAAAYWECADAgAAC1huoBTprIAdArSr9MLECc5R83cvYPeMyAQlEXjkU56TisGtil1G4nKSdmrIlw6bXczcRtvy8rB6CoTUWXhhgs1m231mF4QnDYO7HiGsIvXqfT5xpvbVlg27OKLWTN3/xFyngmD3afWQd5BWut+vD3FqOkH5qwY3oKzOF7eXdqQzOdQlJCgYTeP9KSju/t9vu9LXUgneZO8FY4AE64zboqR4C2wZdpMQu8VjbvFjoDZ5k4mh5m+ukRM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMnlll5kLxTgtydSQqscj+m1evCaiqozJX/fqPyS3ZNUSgqE1Fl4YYLNZtt9ZheEJwkKW7oVifQjIeuHnUHzOtgduzii1kzd/8Rcp4Jg92n1kHeQVrrfrw9xajpB+asGN6Cszhe3l3akMznUJSQoGE3j/Sko7v7fb7vS11IJ3mTvBWOABOuM26KkeAtsGXaTELvFY27xY6A2eZOJoeZvrpETOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zAMED4wm8emQgSEA7YMtoYrI574ljRORbajG3DegCpcEoKhNRZeGGCzWbbfWYXhCcHq9NgvE/OUiPnpgSB53mBHbs4otZM3f/EXKeCYPdp9ZB3kFa6368PcWo6QfmrBjegrM4Xt5d2pDM51CUkKBhN4/0pKO7+32+70tdSCd5k7wVjgATrjNuipHgLbBl2kxC7xWNu8WOgNnmTiaHmb66REzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMytC3oI7uELz5b1N7BB6hiGhG0gYL8EYIq7lr/fGjYGk6CoTUWXhhgs1m231mF4QnB6vTYLxPzlIj56YEged5gR27OKLWTN3/xFyngmD3afWQd5BWut+vD3FqOkH5qwY3oKzOF7eXdqQzOdQlJCgYTeP9KSju/t9vu9LXUgneZO8FY4AE64zboqR4C2wZdpMQu8VjbvFjoDZ5k4mh5m+ukRM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMFkyu+/VIdpKGPhtDiu23IdiebDjA+y471aLPqn+KjYCgqE1Fl4YYLNZtt9ZheEJwxHplEz3FaE97WV30+XnGZ9uzii1kzd/8Rcp4Jg92n1kHeQVrrfrw9xajpB+asGN6Cszhe3l3akMznUJSQoGE3j/Sko7v7fb7vS11IJ3mTvBWOABOuM26KkeAtsGXaTELvFY27xY6A2eZOJoeZvrpETOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zMyIJACjTx02EvO0tl4b2w0p9Iek0Jo59hR6Ix+vadP6oKhNRZeGGCzWbbfWYXhCcIRNJI35ZvHkF2UzFrMHf1Dbs4otZM3f/EXKeCYPdp9ZB3kFa6368PcWo6QfmrBjegrM4Xt5d2pDM51CUkKBhN4/0pKO7+32+70tdSCd5k7wVjgATrjNuipHgLbBl2kxC7xWNu8WOgNnmTiaHmb66REzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMz1wJDePSoigXQKNWD7KwtgysgLM5uI9N4S4LciSQ+Z06CoTUWXhhgs1m231mF4QnDHgCHLEm/Me03Fq3uHjzRy27OKLWTN3/xFyngmD3afWQd5BWut+vD3FqOkH5qwY3oKzOF7eXdqQzOdQlJCgYTeP9KSju/t9vu9LXUgneZO8FY4AE64zboqR4C2wZdpMQu8VjbvFjoDZ5k4mh5m+ukRM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMt97PqcXnQ3wM3FgaW7Aij0qIWQBNICw3ckcXbGdxzUOgqE1Fl4YYLNZtt9ZheEJwygpm81A3xZhRUHVYOMFVB9uzii1kzd/8Rcp4Jg92n1kHeQVrrfrw9xajpB+asGN6Cszhe3l3akMznUJSQoGE3j/Sko7v7fb7vS11IJ3mTvBWOABOuM26KkeAtsGXaTELvFY27xY6A2eZOJoeZvrpETOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM

     

     

    This computer is used for our small business and needed in the morning, so any help on the next step to resolve this would be appreciated.   

     

    Friday, April 11, 2008 5:22 AM
  •  

    While using the laptop that's having the problem and waiting for a response it restarted automatically then started process 3 of 3 of the sp istall (starting around 70% or 80% complete).  This happened even though all 3 steps said that they had completed prior to making that last post.  After four or five hours the sp says it failed to install and is currently in the Reverting changes stage.  There is no progress indicator so I have no idea how long that will take but hopefully a lot faster than it took to install it.   Assumming that the computer will have the same problem when it reverts back to where we started from how can I move the good gdi32.dll that's on this machine to overwrite the corrupt .dll on the machine having problems?

     

    Thank you

    Friday, April 11, 2008 3:01 PM
  • Ok, the reverting changes is complete and as expected the gdi32 error still exists.  Something interesting however is that I compared the product key on the sticker on the bottom of the laptop and it does not match the wga product key being reported.  I then ran wga on this computer and compared the reported product key with the sticker and it doesn't match either, however everything checks out fine on this computer so that may be a red herring as far as my current problem is concerned.  It's been a while since I've gotten any reply from support, any help would be appreciated.

    Friday, April 11, 2008 3:50 PM
  • Hello Ironbreeze,

     

      Computers built by large manufacturers, that come with Vista Pre-installed come with Windows Restore software that allows the user to return Vista back to how it was from the factory. The Windows Restore software may be on a CD/DVD or it may be in a partition on the computer's hard drive. Please see the documentation, that came with your computer, (or contact the computer manufacturer) in conducting the Windows Restore process. 

     

      It sounds like there may have been an error while applying those updates you installed. It is most likely the cause of this file being Modified/Corrupted.  There is another option you may try. There is a function in Vista that allows you to repair back to a past Restore Point. Meaning you could restore to a point prior to when you installed those updates (Note: This is different then the Windows Restore process that I describe above)

      To do a System Restore to a past Restore Point, reboot your computer into Safe Mode. Once in safe mode, go to the Control Panel then double click "Backup and Restore Center". In the "Backup and Restore Center" windows, click "Repair Windows using System Restore" (listed under "Tasks" on the left hand side of the window). Follow the directions to undo the Update install. After that is done, try re-instaling the updates and see if they install correctly, this time.  If you re-install the updates and get the same issue, you may want to contact Windows Update suport at http://support.microsoft.com/ph/6527 or go to http://support.microsoft.com for further Vista support options.

     

      If the System Restore to a past Restore Point doesn't resolve your issue, my only other suggestion is to re-install using the Windows Restore software, included with your computer.

     

     Ironbreeze wrote:

    .  Something interesting however is that I compared the product key on the sticker on the bottom of the laptop and it does not match the wga product key being reported.  I then ran wga on this computer and compared the reported product key with the sticker and it doesn't match either, however everything checks out fine on this computer so that may be a red herring as far as my current problem is concerned.

     

      This is normal and expected. Computers built by large manufacturers, that come with Vista Pre-installed come with two (2) Product Keys:

     

     

    1) OEM SLP: This key come in Vista when it comes from the Factory. This key is geared to work with the special instructions found only on that Manufacturer's computer hardware. So when Vista was installed using the OEM SLP key  (at the factory) Vista looks at the motherboard and see the special instructions and Activates itself. (that's why you did not need to Activate your computer after you brought it home)

     

    2) COA SLP: This is the Product key that you see on the sticker on the side of your computer. It's a valid product key, but should only be used in limited situations. The key does require activation, but you must Activate by Phone.

     

      You can see in your Diagnostic Report that your Vista currently is using the OEM SLP key, therefore it will not match the COA SLP key, listed on the sticker on the side of your computer. 

     

      

    Thank you,

    Darin Smith

    WGA Forum Manager

    Friday, April 11, 2008 6:21 PM