locked
I get a 0xC004D401 error and WGA tells me my copy of Vista is not Genuine, plus other problems RRS feed

  • Question

  • 0xC004D401 Error - Windows Vista flagged up as not valid.

     

    I bought a new Acer Aspire T671 machine a month ago, with OEM installed Windows Vista Home Premium  I have installed software that I used previously on my previous XP-based system, viz:

     

    Microsoft Office 2003 Professional (updated to SP3)

    Microsoft Money 2001

    Adobe Photoshop Elements 2

    Whisper 32 (forpassword reminders)

    Adobe Reader 8 (updated from 7 which was pre-installed on the machine)

     

    I attempted to load Sierra Generations Grand Suite 8 and at about the same time updated my ATI driver in response to a prompt.  It was about then that I first got the 0xC004D401 pop-up, and Windows Vista then failed validation. Office validates OK. I uninstalled Generations but this did not solve the problem.

     

    Other issues I have which may or may not be part of the same issue: 

     

    When starting up most (but not all) applications I get an error message which says 'Ordinal 442 not found in OLEAT32.DLL'  This does not appear to inhibit operation but is annoying.

     

    I have bought Roxio Easy Media Creator 10 (as I was advised 7.5 was not compatible) but can't get it to work fully and it often hangs.

     

    If I try a system restore it fails at all the restore points I have tried, although it appears to partially work (i.e some things roll back, others do not)

     

    I found a thread for OxC004D401 which told me to get a diagnostic report (but which I now cannot get back to!), but here is the report

     

    Diagnostic Report (1.7.0066.0):

    -----------------------------------------

    WGA Data-->

    Validation Status: Invalid License

    Validation Code: 50

    Online Validation Code: 0xc004d401

    Cached Validation Code: N/A, hr = 0xc004d401

    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: {66A77387-A7E7-4C6A-B83E-6861C11DCF8E}(1)

    Is Admin: Yes

    TestCab: 0x0

    WGA Version: Registered, 1.7.59.1

    Signed By: Microsoft

    Product Name: Windows Vista (TM) Home Premium

    Architecture: 0x00000000

    Build lab: 6000.vista_gdr.071009-1548

    TTS Error: M:20080208173327651-

    Validation Diagnostic:

    Resolution Status: N/A

     

    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: 100 Genuine

    OGA Version: Registered, 1.6.21.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\oleaut32.dll[2.40.4275.1]

     

    Other data-->

    Office Details: <GenuineResults><MachineData><UGUID>{66A77387-A7E7-4C6A-B83E-6861C11DCF8E}</UGUID><Version>1.7.0066.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-2967637801-238350057-3586256053</SID><SYSTEM><Manufacturer>Acer</Manufacturer><Model>Aspire T671</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>R01-A4</Version><SMBIOSVersion major="2" minor="4"/><Date>20070306000000.000000+000</Date></BIOS><HWID>86303507018400FA</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00: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>100</Result><Products><Product GUID="{91110409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>943809A03444F78</Val><Hash>nIGYjWnckfwrCH0jAfKuIlQOdks=</Hash><Pid>70145-OEM-5795621-36556</Pid><PidType>5</PidType></Product></Products></Office></Software></GenuineResults> 

     

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAKJSAQAAAAAAYWECADAgAAAqXX0HEF3IAdArSr9MLECc5R83cvYPeMzCVNB8lbCXryk2lHwwCj6VHvAxetj8rqapAIW42EqOaNWMYijKW7xepC08AN1u911/PiMHbBU5IZ7KgAvg0O70qiy06+216T3+3YpHs/4iZ+S8PGJVzATbEeSmtmHv23GaQUUogaFO7xGwZOZnh8mbNKSqzmEoZxPMqvgdiGIQOT9vjSLV9dzF//x4MzHjERbaK7PNt1woZspXMzGfFYMVmm/PaAAXfTw3mjuFacsnhDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMsTa19iAlLgtPshFHtroupjSvCaxr4y0Zl+L+B5nria7VjGIoylu8XqQtPADdbvddfz4jB2wVOSGeyoAL4NDu9KostOvttek9/t2KR7P+ImfkvDxiVcwE2xHkprZh79txmkFFKIGhTu8RsGTmZ4fJmzSkqs5hKGcTzKr4HYhiEDk/b40i1fXcxf/8eDMx4xEW2iuzzbdcKGbKVzMxnxWDFZpvz2gAF308N5o7hWnLJ4QzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zNdYfWTBzmaxk2XsQgPhYU2lXvm3b+RTSnoLdNuFsrKZ1YxiKMpbvF6kLTwA3W73XX8+IwdsFTkhnsqAC+DQ7vSqLLTr7bXpPf7dikez/iJn5Lw8YlXMBNsR5Ka2Ye/bcZpBRSiBoU7vEbBk5meHyZs0pKrOYShnE8yq+B2IYhA5P2+NItX13MX//HgzMeMRFtors823XChmylczMZ8VgxWab89oABd9PDeaO4VpyyeEM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMw10yy+dXJ/Cpt0B98pQktak19V/j6sCYO7YlYlBZnrEdWMYijKW7xepC08AN1u911/PiMHbBU5IZ7KgAvg0O70qiy06+216T3+3YpHs/4iZ+S8PGJVzATbEeSmtmHv23GaQUUogaFO7xGwZOZnh8mbNKSqzmEoZxPMqvgdiGIQOT9vjSLV9dzF//x4MzHjERbaK7PNt1woZspXMzGfFYMVmm/PaAAXfTw3mjuFacsnhDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

     

     

    Saturday, February 9, 2008 11:27 PM

Answers

  •  

    Hi David,

     

      Your Vista is suffering from a "On Disk" Mod-Auth Tamper. A Mod-Auth tamper is caused when a Critical System File has been tampered either In Memeory or On Disk.

     

    In Memory - This type of Mod-Auth is caused by a incompatible program trying to Hook into or Shim (i.e. modify) a Critical System File resident in memory.

     

    On Disk - This type of Mod-Auth is when the Critical System File itself (on disk) has been modified or has become corrupted.

     

      In your Diagnostic Report (under the "File Scan Data-->" line) you see that file oleaut32.dll[2.40.4275.1] is listed as Mismatched. This means this is the file that has been modified or corrupted.

     

      A related issue is that the number [2.40.4275.1] seen next to the oleaut32.dll file is it's build/version number.  The build/version number [2.40.4275.1] is very old (example, the build/version number for oleaut32.dll in my Vista is [6.6000.16386]).  The oleaut32.dll build/version number [2.40.4275.1] file can be traced back to the "Visual Basic 6.0 SP6 run-time files" released in March 2004.

     

      I have talked with my Devs and the hypothesis we came up with to explain how you got an this older oleaut32.dll file, as well as why it is causing the Mod-Auth tamper event is:

     

    a) An old program, that you installed, replaced your Vista's current oleaut32.dll file with the older [2.40.4275.1] build/version.

     

    and

     

    b) While installing the older file, it may have corrupted it or the older file was corrupted some time after it was installed (for unknown reasons).

     

      My Devs also believe that even if your Vista wasn't suffering from a Mod-Auth Tamper state, that (because of the out dated oleaut32.dll file) your Vista may act unstable and/or unpredictable. Therefore, they think it is importent to update that file to a current build/version.

     

      So, we know there are a few Windows Updates that contain an updated build/version of the file oleaut32.dll, so we believe that to fix both of your issues, that you should install one of these updates. The Update would replace the old and corrupted oleaut32.dll file with a more current and uncorrupted file.

     

    Below are the Vista Updates that contain a current version of the oleaut32.dll file. Some of these updates can only be installed once so if you receive the error similar to "This update does not apply to your system" then the update is already installed (or you tried to install the version of that update that is for a different version of Windows).

     

    Lastly, if you already have all of these updates installed already and Vista won't let you re-install them, then login to Vista in Safe Mode, go to the control panel, then double-click "programs and features" and then click "View installed updates". Once the list of updates populates find one of the below updates, in that list, and uninstall it. After you have uninstalled that update, reboot back into normal mode and re-install that update you just uninstalled.

     

    Update for Windows Vista (KB938371):

    http://www.microsoft.com/downloads/details.aspx?FamilyID=695d7c32-252c-40e8-a15d-81029bec7d76&DisplayLang=en

     

    Security Update for Windows Vista (KB943055):

    http://www.microsoft.com/downloads/details.aspx?FamilyID=c67ec357-0f86-4f7d-9af0-d63d8b765f44&DisplayLang=en

     

    Update for Windows Vista (KB943899):

    http://www.microsoft.com/downloads/details.aspx?FamilyID=a23e4401-74b7-4987-96ab-86735f718a8e&DisplayLang=en

     

     

    Thank you,

    Darin Smith

    WGA Forum Manager

    Tuesday, February 12, 2008 8:39 PM

All replies

  •  

    Hi David,

     

      Your Vista is suffering from a "On Disk" Mod-Auth Tamper. A Mod-Auth tamper is caused when a Critical System File has been tampered either In Memeory or On Disk.

     

    In Memory - This type of Mod-Auth is caused by a incompatible program trying to Hook into or Shim (i.e. modify) a Critical System File resident in memory.

     

    On Disk - This type of Mod-Auth is when the Critical System File itself (on disk) has been modified or has become corrupted.

     

      In your Diagnostic Report (under the "File Scan Data-->" line) you see that file oleaut32.dll[2.40.4275.1] is listed as Mismatched. This means this is the file that has been modified or corrupted.

     

      A related issue is that the number [2.40.4275.1] seen next to the oleaut32.dll file is it's build/version number.  The build/version number [2.40.4275.1] is very old (example, the build/version number for oleaut32.dll in my Vista is [6.6000.16386]).  The oleaut32.dll build/version number [2.40.4275.1] file can be traced back to the "Visual Basic 6.0 SP6 run-time files" released in March 2004.

     

      I have talked with my Devs and the hypothesis we came up with to explain how you got an this older oleaut32.dll file, as well as why it is causing the Mod-Auth tamper event is:

     

    a) An old program, that you installed, replaced your Vista's current oleaut32.dll file with the older [2.40.4275.1] build/version.

     

    and

     

    b) While installing the older file, it may have corrupted it or the older file was corrupted some time after it was installed (for unknown reasons).

     

      My Devs also believe that even if your Vista wasn't suffering from a Mod-Auth Tamper state, that (because of the out dated oleaut32.dll file) your Vista may act unstable and/or unpredictable. Therefore, they think it is importent to update that file to a current build/version.

     

      So, we know there are a few Windows Updates that contain an updated build/version of the file oleaut32.dll, so we believe that to fix both of your issues, that you should install one of these updates. The Update would replace the old and corrupted oleaut32.dll file with a more current and uncorrupted file.

     

    Below are the Vista Updates that contain a current version of the oleaut32.dll file. Some of these updates can only be installed once so if you receive the error similar to "This update does not apply to your system" then the update is already installed (or you tried to install the version of that update that is for a different version of Windows).

     

    Lastly, if you already have all of these updates installed already and Vista won't let you re-install them, then login to Vista in Safe Mode, go to the control panel, then double-click "programs and features" and then click "View installed updates". Once the list of updates populates find one of the below updates, in that list, and uninstall it. After you have uninstalled that update, reboot back into normal mode and re-install that update you just uninstalled.

     

    Update for Windows Vista (KB938371):

    http://www.microsoft.com/downloads/details.aspx?FamilyID=695d7c32-252c-40e8-a15d-81029bec7d76&DisplayLang=en

     

    Security Update for Windows Vista (KB943055):

    http://www.microsoft.com/downloads/details.aspx?FamilyID=c67ec357-0f86-4f7d-9af0-d63d8b765f44&DisplayLang=en

     

    Update for Windows Vista (KB943899):

    http://www.microsoft.com/downloads/details.aspx?FamilyID=a23e4401-74b7-4987-96ab-86735f718a8e&DisplayLang=en

     

     

    Thank you,

    Darin Smith

    WGA Forum Manager

    Tuesday, February 12, 2008 8:39 PM
  • I installed the first of the updates listed above and the validation problem and the OLEAT32.DLL message problems seem to be cured.  I have yet to scheck System restore (as I don't want to do it) and intend to re-install Roxio EMC10.

     

    Thanks for your help

     

    David

     

    Wednesday, February 13, 2008 6:04 PM
  • Hi David,

     

      Great!  If you have any other Validation or Activation issues, don't hesitate to post again.

     

    Darin

     

    Wednesday, February 13, 2008 7:31 PM