8100030d - sign into live messenger failed

Discussion in 'Windows Live Messenger' started by Shine, Aug 17, 2006.

  1. Shine

    Shine Guest

    One my work laptop I keep getting this error when I try to sign into msn. It
    doesn't matter which ID I use I get the same error. Does anyone know how to
    fix this?

    I've tried to a reinstall but it didn't help.
    Shine, Aug 17, 2006
    1. Advertisements

  2. Shine

    Robyn D.B. Guest

    I get this frequently, maybe once every other day at some point but when I
    click retry it will connect after the second try or third. I don't think you
    can fix it, I think only MSN can fix it. I assumed it was server overload
    since I was able to connect after retrying it once or twice.
    Robyn D.B., Aug 17, 2006
    1. Advertisements

  3. Shine

    Shine Guest

    Its been like this for nearly 3 weeks now :(

    Shine, Aug 17, 2006
  4. Greetings Shine,

    Since you can't immediately login, remember that you can try logging into the Web Messenger,
    at least until you can restore your normal Messenger functionality:

    However, here are some suggestions you should check/try if you haven't already.

    1. If you haven't done so already, upgrade to the latest version of MSN Messenger:
    2. The date on your computer needs to be set properly -- double click the clock verify that
    the time and date are set.
    3. If you use a firewall (like ZoneAlarm, Norton Internet Security etc. ), it's possible
    that Messenger doesn't have the correct rights to access the Internet, especially since you
    upgraded. You may need to re/add Messenger to the allowed list of programs in your firewall
    if this is the case.
    4. If you disabled your firewall in the past, it still may be blocking Messenger -- try
    restarting it and see if that helps the situation. You also might try uninstalling an
    installed firewall, to verify that it isn't causing a problem (even if it is disabled).
    5. Check your IE Security settings -- open Internet Explorer, click the Tools menu, then
    Internet Options, then Advanced tab, scroll to the Security section, and verify that "Check
    for server certificate revocation" is unchecked. Also verify that 'Use SSL 2.0' and Use SSL
    3.0' is checked, then click OK.
    6. Click Start, then Run, and enter the following:
    regsvr32 softpub.dll
    then click OK
    and do the same for the following:
    regsvr32 wintrust.dll
    regsvr32 initpki.dll
    regsvr32 MSXML3.dll
    Jonathan Kay [MVP], Aug 17, 2006
  5. Shine

    Shine Guest


    Thanks for your reply. I'm using Trillian until Messenger is working again.
    Answers to your questions:
    I'm using version 8.0 build 8.0.0812.00
    The date and time are set correctly.
    There are no firewalls on this pc and never have been.
    see above
    I've checked 'Use SSL 2.0' and tried using Messenger again but it still fails.
    Again, no affect, I still get the error.
    Shine, Aug 18, 2006
  6. Shine

    lorenz1402 Guest

    Hi Jonathan Kay,

    i just installed Vista Home Premium, and i have aswell the problem that i
    can´t sign in at all (8100030D) i tried all, but it doesnt change anything,
    it still doesnt work, its not the firewall and non of the above things. is
    there anything else i can do?

    i also did a msn connection check and it always fails with the ip adress.


    lorenz1402, Mar 28, 2007
  7. Shine

    Bigi Guest

    Bigi, Apr 10, 2007
  8. Shine

    pea jay Guest

    its been like this on mine for 5 months !!!!!!!!!!!!!!!!!!!!!
    pea jay, Apr 24, 2007
  9. Shine

    grez868 Guest

    ignore all the information that other people are posting if you are using a

    all you need to do is torn off your computer and unplug the router, plug it
    back in and turn on the computer and your msn problem will be solved

    dont even listen to emails you may recieve from microsoft customer services
    cos they havent got a clue when it comes to using a router
    grez868, May 7, 2007
  10. Shine

    N. Miller Guest

    And, because you didn't quote the article you responded to, nobody has a
    clue that you know what you are talking about. Neither the MSFT NNTP
    servers, nor Google Groups, has a copy of this mysterious article...

    References: <>
    N. Miller, May 7, 2007
  11. Shine

    Satish Guest

    I dont think its the files that are corrupt. From my understanding its
    Microsoft servers kicking you out.

    My MSN manages to connect, but disconnects immediately. Then i get the same

    However, this happens for me only if I login from my GPRS/cellular
    connection beiung used as a modem. It works fine otherwise should I use a DSL
    / Cable connection. This is on the SAME MACHINE and SAME messenger. Thats why
    I really doubt the problem are the dll files.

    I would think microsoft has put some kind of restrictions on the ip address
    /block range? or packet size. OR more likely it could be the isp closing the
    connection too early before your registration goes through or the entire
    transaction is complete OR the msn server thinks the connection is dead cause
    its going slow and kills the connection ? Or it could be even the lack of a
    decent rDNS on your ip address. These ofcourse are just my wildest guesses,
    the truth could be something else ALL together.

    But I really would doubt its the DLL files causing problems as the
    connection works fine should I login from a different provider.
    Satish, May 22, 2007
    Damzil in Distress, Jul 8, 2007
  13. I’ve tried repairs, reinstalls doing all of the above that you have suggested
    I still haven’t been able to log on now for a few months, I will also add
    that I am connecting via my N95 as a modem

    Help please!!!
    Damzil in Distress, Jul 8, 2007
  14. Shine

    rednaS Guest

    I am having the exact same problem, but when i use my other hotmail account
    it just works!
    How is this possible?
    Maybe some personal files that got mixed up by upgrading to 8.1
    rednaS, Jul 16, 2007
  15. Shine

    Zobo Guest

    I have the exact same behavior. Here are my observations:

    When I try to connect from work, I get this error code (8100030d). If I try
    connect from home with the same address, it works just fine (all this with
    WLM). Then, you might think that the problem is somehow with the setup at
    work. But the tricky part is that my colleague just logged in with his
    address without any problem on my computer at work. Same computer, same user
    profile, just switch the loggin id. So, it can't be anything with a .dll or
    registry key. It seems it's some combination of "who" is logging and "from
    where". I tried many things such as reinstalling, deleting ntuser.dat, etc.
    but nothing worked so far.

    When I tried to log in from msn 7.5, it works just fine!!! So, the problem
    is a combination of WLM, my computer at work and my login. Change any of
    these three and it will work...

    Zobo, Sep 14, 2007
  16. Shine

    GordonK Guest

    Similar issues to Satish.

    Had a laptop with Xp and a UMTS celluar card. Worked fine using it.

    Upgraded (Clean install) of Vista to same hardware with new drivers from
    vendor etc but all works fine for everything except Live Messanger.

    The Laptop works fine when on a lan...both work and home..it is ONLY when i
    use DUN for Live Messenger that it fails. And it never faile don XP ..ONLY
    fails on DUN with VISTA..

    I don't use Zonealarm , Live Messenger is installed properly ..all DLL's are

    There is a setting somewhere that is causing this and I suspect it's the
    anal way Vista treats your network connectivity.

    Anyone got a real fix for this...
    GordonK, Oct 18, 2007
  17. hi
    Jonathon Kay [MVP] seems to think the problem could be something to do with
    Messanger client cache under the user account. I am waiting for him to get
    back to me to confirm this.
    Gary Whitmarsh, Oct 18, 2007
  18. Shine

    GordonK Guest

    The assumption he/she makes is wrong. By all means reset your router but to
    assert it is the answer to this for everyone is wrong....but it might fix the
    odd problem though i imagine for those of us with DUN issues it's hardly
    close to the solution.
    GordonK, Oct 24, 2007
  19. Shine

    GordonK Guest

    Any news on this potential fix?

    GordonK, Oct 24, 2007
  20. Shine

    Paul Guest

    This worked for me
    Paul, Nov 18, 2007
    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.