Fixing Windows Live Messenger 8100030F Error
When trying to run the newest version of Windows Live Messenger (at the time of writing this post, that's version 2009, build 14) I was getting this error:

We can't sign you in to Windows Live Messenger
Signing in to Windows Live Messenger failed because the authentication service is not compatible with this version of the program.
Error code: 8100030f
All it takes to solve it is browsing to C:\windows\system32\drivers\etc\, opening the file called hosts, and adding the following line after the last entry:
65.54.239.80 messenger.hotmail.com
I'm using Windows Vista but this fix has been reported to work on XP as well.


Or use Pidgin (or even Digsby)
I go to C:\windows\system32\drivers\etc\ but then it asks me to choose a program to open up the Hosts file in...what do I do there?
It's just a text file, so you can choose any program that opens text files, like Notepad or Wordpad.
Genius! That worked like a charm - thank you so much!
did that ... now getting error 80072ee7
fired up the "Windows Live Messenger Connection Troubleshooter" which got upset that the HOSTS file had MSN entries ... allowed the 'troubled'shooter to "fix" the problems (=remove MSN entries) after which it (the troubleshooter) was happy with my config
and now getting original error (8100030f)
Worked just fine on the first try! thanks for the tip
Yes it work. Thanks.
Users should not have to manually add a DNS entry into the hosts file. Workarounds like this creates IP spoofing risks if the IP addresses are not validated!
Microsoft should fix this!
I totally agree that we shouldn't have to do this.
But since we have to do it if we want Live Messenger to work, we can always check if the IP is really from Microsoft, which gives some kind of security:
http://ws.arin.net/whois/?queryinput=65.54.239.80
5.5.09 Worked great! Easy work around for someone that is not very literate about Windows.
Tried it with XP SP2 in the office using Messenger build 14.0.864.206
Works perfectly! Thanks!
Odd thing is that it did work from home as long as I didn't run the VPN...
Thanks!!!