My windows live messenger recently updated. Norton approved the software. I can't login on my windows live messenger. I am getting this error.
Error 8100030d: Cannot Sign-in to Windows Live Messenger
However, my firewall and virus protection are not blocking the program. My internet is land line.
Does anyone have any idea what the problem could be?
If you followed the steps seen there and still are not getting anywhere the best solution would be to remove the program side entirely and then sign in to download a fresh install of the Live options. I ran into similar problems on previous occasions with the older version of WLM and cleaned that up by redoing things over.
You won't manually be deleting any of the folders under your user account but allow the installer to replace all the Live components. Once a fresh install is on you simply log into the same account fresh.
Note this is one solution if you already restarted the system a few times inbetween the update and now. If you haven't restarted but only went into hibernation a full restart may be all you need. The reinstall is for when nothing else has worked.
Thanks for the reply.
I uninstalled then reinstalled the program, but it still does not allow me to login. Is windows live having a downtime? Norton still labels it as a safe program to use, so nothing is blocking it.
I've had occasions here when I couldn't log onto either WLM or the Inbox. For mail I solved that one by having the Live Mail option installed locally on the drive where I simply click on the desktop shortcut created from the Start>All Programs>Windows Live folder there.
I just logged in here on the spot without any problems while at times the login may be delayed if the MS servers are busy.
I do have great news! Windows have annouced a problem with LiveID. Hopefully I can login soon.
Error 8100030d: Cannot Sign-in to Windows Live Messenger
Ok so now you have to look over your firewall settings if you have the Windows Firewall or other program running to see if that is not allowing WLM as an exception. One way to verify the present protections are not the cause would be temporarily shutting them down long enough to make a few more attempts at logging in if you haven't already tried that out.
The page you can come across at the WindowsLivehelp site is very familiar to the Dec. 2009 posting seen at Error: 8100030d - Windows Live
Apparently they finally got around to updating the support information on the help site. But that was also the same page you posted at the start of the thread.
The question now would be the particular firewall and av protection you are presently running if not AVG as referred to on those pages? The FAQs section at the software company's own support site may also have a few things to try out.
I know it is the same page. I was referring to the message highlighted in golden yellow on the page.
My firewall is not blocking the program.
The next step would be looking at whatever else you have set to start with Windows in case you are seeing a software clash of some type. One idea would be disabling a few items in the startup and services tabs of the msconfig utiliy also known as the system configuration utility in order to isolate each one to see you can ID one program in particular.
Mostly you would looking for any programs that automatically connect online to update themselves automatically since you have been able to rule out the firewall program. How about the av program? If that can also be ruled out that will make the second you can also rule out.
The error itself does point to 3rd party softwares interferring with WLM as the reason. You may end up needing a fresh install of WLM all over while Norton and other things are disabled to see that will allow you to login. If something didn't on right the first time a fresh download/install could end up correcting the problem.
Quote