You wonder why no emoticons are showing up in chats with your friends? Here’s a solution.
Since last week, there are quite a few users receiving Messenger error code 85ae000b when they try to sign in. Are you among them? Here is the explanation.
Are you trying out the current Windows Live Messenger Wave 4 Public Beta? You might receive the error code 81000395 when you try to sign in. The Windows Live team has published a workaround for this error code.
You’re getting the error code 800706ba when you try to sign in to Windows Live Messenger Wave 4 Beta? The fix is easy — you have to start a system service.
If you receive the error code 80071392 when you try to sign in to Windows Live Messenger, try these steps.
You have been trying Messenger 2010 recently after downloading and installing the leaked Milestone 2 beta 15.2.2583.119? You might get problems when you want to go back to Messenger 2009.
Some of you have problems while trying to sign in to Messenger, receiving error code 81000306. Let’s take a look at the solution.
For the past several hours or so, the Messenger servers have been showing the majority of contacts offline. You can however still talk to contacts using offline message. There were other similar issues earlier on in the day and the problem just seems to have progressively gotten worse.
Numerous users of Windows Live Messenger are currently experiencing the error code 80048820 when they try to sign in to Messenger. If you are getting this error as well, the reason might be that you have invalid characters in the first name of your user profile.
There is a new solution for the Windows Live Messenger error code 8004820. If you get this error, maybe the only problem is that your system clock has the wrong date set.