The Messenger Support Blog has today been updated adding further error code troubleshooting articles as many people have been getting hit with the 8xxxxxxx error codes when logging in with the newer versions since Windows Live Messenger 8.0.
Heres some links to step by step instructions which help fix errors you maybe recieving;
Hopefully these will solve your problems you may be experiencing with Messenger. Remember to check out the other articles at Messenger Support Blog relating to other error codes and problems relating to Messenger.
If you’ve been getting errors when trying to sign in for the last few hours, it may be because of some service downtime. The service status page is reporting temporarily experiencing difficulty.
Sign In
The .NET Messenger Service is temporarily experiencing difficulty. You may be unable to sign in. Please try again later.
Last Update: 4/12/2007 3:00:00 PM Pacific Time (GMT -8:00)
As it says, just try again later. It doesn’t appear to be very widespread, I’m having no problems signing in and have the usual number of contacts online. But, traffic to this Web site has increased a little, so there’s definitely something going on.
Last September the same problem could be solved by changing the server which Messenger connects to, I’ve just tested it and it still works.
Update: Looks like I posted this shortly after the problem had already started to come right, I even missed the acknowledgment from Nicole at the Windows Live Messenger blog.
There seems to be an awful lot of people having trouble with running Windows Live Messenger on Windows Vista. One problem I am hearing a lot about is Data Execution Prevention crashing Messenger, preventing it from fully starting up. The issue seems to come down to Acer’s eDataSecurity Management software.
If you have recently purchased an Acer notebook or desktop PC with Windows Vista installed, you can now download a patch from Acer to correct the problem.
Leave a comment on whether or not the patch fixes the problem for you - I’m interested to see if there is anyone else having this problem but from different causes.
A new virus labelled a variant of the Win32/Spy.VB.LO trojan by NOD32 has been spreading via Windows Live Messenger over the past couple of weeks, one of the messages it typically sends contains the recipients e-mail address, looking something like this:
» rofl @ you, http://improfile.net/members.php?msn=example@example.com
The Web site has been shutdown to stop it from spreading. The DNS is set to loopback (127.0.0.1) and “Closed for Fraud” is in the whois information.
Kelvin has created a tool called impFix to remove the virus, so give it a try if you believe to be infected with this pest.
There have been many users having problems signing in for the last few days. Reports claim that Windows Live Messenger doesn’t complete the sign in process, instead just sitting there with the messenger sign in buddies continuing to spin until you cancel. One of the most likely causes is this month’s round of security updates for Windows.
Among all the posts for help in the newsgroups, Jimmymac posted (6th post down) explaining he fixed it by deleting messenger’s registry settings. Jonathan Kay created a .reg file that will automatically delete the settings for you, remove_msgrsettings.reg.
Before running the .reg file, completely exit Windows Live Messenger by right clicking the buddy icon near the clock and clicking Exit. Once you have run the file and clicked Yes, try signing in again.
One of the side effects of this solution is you will lose some customised settings, but hopefully you’ll find it’s worth it!
Leave a comment if this does or doesn’t work for you.
