Fix Error Code 80072efd in Windows Live Messenger

Posted In Messenger - By Admin On Friday, April 15th, 2011 With 1 Comment

When you start Windows Live Messenger you cannot sign in, and you get error code 80072efd along with the message:

Sorry, we were unable to sign you into Windows Live Messenger at this time. Please try again later.

Error code: 80072efd

Explanation and Possible solution

Error code 80072efd usually occurs when there is a problem with the .NET Messenger service. one or more of the servers providing it might be down or having problems, with as result that you can no longer sign in. This normally won’t take longer then a few minutes/hours. For more information you can check the .NET Messenger Service Status

This is how the Service Status looks with a normal situation

Please note that the Service Status is known to not always be very accurate, if problems do appear the best thing to do is wait them out. Surely there are many other very interesting things to do. If the error keeps bothering you for over a few days there are some more things you can try below.

Other steps that might help

If there are no reported problems with the Messenger servers, see if your proxy settings are correct: click “Tools” and then “Options” at your Messenger main window. In the options screen click “Connection” in the list to the left. Next, click the “Advanced Settings…” button. If you (likely) do not use a proxy server, try unchecking all the checkboxes except for the one labeled TCP and see if you can connect now. (You might have to fully close and start Messenger again before retrying to connect). If you are on a large network, the network administrator can probably tell you if you should have proxy settings in Messenger.

In Internet Explorer: click Tools, then Internet Options, select the “connections” tab. Try unchecking (if checked) “Use a proxy server for LAN” and check “Automatically detect settings”. This should enable both Internet Explorer and Messenger to automatically find the best way to connect to the internet.

If the error continues to appear it is most likely because the Windows digital signatures system is damaged or corrupt. To resolve this you will have to register several dll files that are required for Messenger. You can do this automatically by running a batch file we created or if you prefer by executing the commands yourself.

Automatic solution

First you will have to download register-dll-for-messenger which includes a batch file that can register the dll files for you. After downloading unzip it and run register-dll-for-messenger.exe,

a black screen will pop up and update you on the process. When done your Messenger should work again!

fix-dll-files-run-2

Manual solution

First open a run window by clicking start, then run. Now, type the following command and press enter:

regsvr32 softpub.dll Wintrust.dll Initpki.dll Rsaenh.dll Mssip32.dll Cryptdlg.dll

fix-dll-files-run-2

The run screen where you can execute a command in Windows

If you use Windows XP you should open another run window after running the previous commands then type the following command:

regsvr32 Dssenh.dll Gpkcsp.dll Slbcsp.dll Sccbase.dll

fix-dll-files-run-2

The run screen where you can execute a command in Windows

And restart your pc – Done…!

Don't forget to follow our RRS feed for the latest technology news, windows tips, tutorials and IT knowledge, and also follow us on Facebook and Twitter

Incoming search terms:

About -

Displaying 1 Comments
Have Your Say

  1. The vast majority of windows errors are caused by corrupted entries in Windows registry. These registry entries are responsible for how windows manages programs that are installed and all information stored on the computer. If the registry fails, so will the windows.
    Go to this link for more information about the Windows Error and how to fix.

Leave a comment

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

 
105 queries in 0.738 seconds.