My Solution For Error 800A138F Windows Update

Discussion in 'Windows Update' started by Ekenthor, Dec 3, 2003.

  1. Ekenthor

    Ekenthor Guest

    S T A T U S
    WINDOWS UPDATE ERROR /Error 0x800A138F
    Line in c:\windows\windows update.log = Querying software
    update catalog (Error 0x800C0002)

    S O L U T I O N
    For me the solution IS to run this ...
    https://V4.Windowsupdate.microsoft.com

    [Important:https not http], Earthquake for Just a S but
    why, is it for have spywares with akamai.net adresses or
    what?
    NB:if you use spyblocker, it ads a line in hosts file,
    "127.0.0.1 a248.e.akamai.net" wich can be used for the
    update since wormblaster event (Error 80072EFD)..try to
    unload spyblocker before update.
     
    Ekenthor, Dec 3, 2003
    #1
    1. Advertisements

  2. Ekenthor

    Don Guest

    Thank you so much for your posting. This got me past the
    error and I suppose could update should I chose to
    continue. At this time I have no idea as to why I started
    to get this error. I have a suspicion as to what the
    cause might be. I am running WIN98 2nd Ed, with updates,
    but not the latest. I will update my reply when I have
    more info. Again thanks.
     
    Don, Dec 3, 2003
    #2
    1. Advertisements

  3. Ekenthor

    Lucy [MS] Guest

    Error 0x800A138F - 0x800C0002

    The problem is due to caching on the proxy. We released a new file for the
    site which is more than likely being cached by your ISP.
    As a temporary workaround try using the secured link to access Windows
    Update: https://v4.windowsupdate.microsoft.com

    Internet Service Providers typically clear the proxy cache every 3-5 days,
    once the proxy is cached you can again access the site
    using the default link http://v4.windowsupdate.microsoft.com

    --
    Thanks,
    Lucy [MS]

    This posting is provided "AS IS" with no warranties, and confers no rights.


     
    Lucy [MS], Dec 3, 2003
    #3
  4. Clearing the cache in IE solved this for me.

    -Yves

     
    Yves Konigshofer, Dec 3, 2003
    #4
  5. Ekenthor

    david9000 Guest

    It worked for me, too. I had just reinstalled XP, cut off
    ZoneAlarm, Uninstalled Norton AV, and tried a few of the
    MS workarounds, etc.-to no avail. Thanks again.
     
    david9000, Dec 3, 2003
    #5
  6. Ekenthor

    Mark Guest

    This did not work for me! Probably just a coincidence.
     
    Mark, Dec 4, 2003
    #6
    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.