Walker News

Two Possible Tricks To Fix Windows Live Messenger Error Code 80048820

Having Windows Live Messenger login problem again, rejected with the same error code 80048820, but I am glad it can fixed in no time.

During the last encounter at about three months ago, I forgot I had made a note on how to fix this 80048820 error, including a “silent” screencast on YouTube, as I pretty sure the “Check for server certificate revocation” option was disabled.

So, I spent some times on Google and then suspect that had something to do with WinHTTP proxy settings again, which had noted in 2nd post.

Now, I certainly believe that is the case – as soon as the WinHTTP proxy setting is corrected, Windows Live Messenger is able to login successfully again, no more seeing that unfriendly error code 80048820 and its general error description.

Summary of the two possible tricks to fix WLM Error 80048820:
This guide is based on Windows Live Messenger 2009 Build 14.0.8089.726 and Windows 7 Enterprise Build 7600, but it should be good to serve as general reference.

Disable check for server certificate revocation

1) Open Internet Options dialog box, from either Internet Explorer or Control Panel. Alternatively, click the Windows 7/Vista Start button, type inetcpl.cpl and press ENTER key.

2) Go to Advanced tab and disable the “Check for server certificate revocation” option under the Security settings. (In my test just now, however, this option seems no longer applicable – whether it is enabled or disabled, WLM stills work correctly.)

Confirm all proxy server settings are correct

If your network requires proxy server to browse the Web and the computer doesn’t join a domain (if any) or the computer is not configured to automatically detect proxy settings in the network, then make sure you have configured the proxy server settings in these various places:

1) Internet Explorer
  • Open Internet Options dialog box, go to Connections tab, click LAN Settings button.

2) Windows Live Messenger
  • Press ALT+T to bring up Tools menu and select Options, click Connection on the left pane of Options dialog box, click Advanced Settings button, enter the proxy server credentials, and click Test button to confirm.

3) WinHTTP – this is the culprit in my case that happened this morning.
  • Open an elevated Command Prompt window and execute these netsh commands:
    To view the WinHTTP proxy server setting:
    netsh winhttp show proxy
    

    To update or change the WinHTTP proxy setting (e.g. to IP 192.168.1.40 port 80):
    netsh winhttp set proxy 192.168.1.40:80
    

    To disable WinHTTP from using proxy server, i.e. no proxy server should be used:
    netsh winhttp reset proxy
    

If you have other tricks, please leave a comment. Good luck.

Custom Search

2017  •  Privacy Policy