Another possible fix for the 0x800A138F error

Discussion in 'Windows Update' started by Scott Hagen, Aug 30, 2003.

  1. Scott Hagen

    Scott Hagen Guest

    I tried all of the fixes for the Windows Update Error
    0x800A138F suggested on Marc Liron's website at to no avail.

    Here is my solution. Try this at your own risk!


    In the registry, I changed all occurrences of:




    and my Windows Update problems were solved.


    I initially had a problem where the management console
    refused to load, in addition to windows update returning
    the error 0x8007007E. Someone on google suggested looking
    the registry entry:


    The default value for the InProcServer32 was:


    I changed this to:

    "C:\Windows\System32\msxml3.dll" (I don't know
    why 'C:\Windows' was suggested instead of %SystemRoot%)

    and my MMC problems were fixed, but Windows Update started
    returning the 0x800A138F error. On a hunch, I searched the
    registry and found numerous references
    to '$NtServicePackUninstall$\msxml3.dll'. I changed all of
    these to 'System32\msxml3.dll', and Windows Update was
    back in business.

    This also solved many other quirky problems I was having,
    such as the Windows Explorer search window not working,
    and Outlook not connecting to my hotmail account.

    FYI the 'Windows Update.log' file was showing the error:
    tmanifest.asp (Error 0x8007045A: A dynamic link library
    (DLL) initialization routine failed.)

    A reinstall postponed for another day...

    Scott Hagen.
    Scott Hagen, Aug 30, 2003
    1. Advertisements

  2. Scott Hagen

    Scott Hagen Guest

    Scott Hagen, Aug 31, 2003
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.