Category Archives: MSN Messenger
This page remains here for archival reasons. As of March 12th 2015, the last of the servers accepting sign-ins from Messenger:Mac have gone offline. To use the Messenger service on the Mac, you will need to use Skype, the web-based Outlook.com client, or Windows Live Messenger 2012 in a Windows virtual machine.
Starting November 13th, 2014, Messenger:mac clients are no longer able to sign in to the Messenger service and you will receive the following error:
Sign in to Microsoft Messenger failed because the service is not responding. The service is not available or you may not be connected to the Internet.
Using Messenger Reviver 2:mac
To revive Messenger:mac, download the Messenger Reviver 2 dmg and open it from the Downloads folder. Then right-click on the Messenger Reviver 2 mac icon and choose Open.
If you receive the “unidentified developer” warning message choose Open when asked. Next, you may get a message reminding you that you’re about to install software, click Continue. You can then click Continue to the Introduction screen, then the Install button, type in your password, and finally click the Install Software button. After Reviver has completed, Messenger:mac should re-open and you should be able to sign in.
Important note: Unlike the Windows version, Messenger Reviver 2:mac at this time is not able to automatically download and install Messenger:mac. If you do not already have it installed, you can install it from c|net Download.com.
Known issues and workarounds
When you sign into Messenger:mac after using Reviver:mac, you most likely will see various contact list addition requests from your contact list. This is a side effect of tricking the server, and can either be ignored or dismissed. Unfortunately, they will return again when you sign in again. This issue is being seen in various third party clients as well.
In addition to this, even though contacts appear on your contact list, you might receive a message “Do you want to accept a message from an unknown sender”. Click the Accept button and you can proceed with the conversation.
Lastly, on some accounts you might not appear online to your contacts. Regrettably, this is a result of the same issues above. You can workaround this problem by signing in on another client first (including logging into your Microsoft account at Outlook.com) and then signing into Messenger:mac. The other client will put you online and Messenger:mac will take over your Messenger session.
A compatible version of OS X running Messenger:mac 8.0.1
In the past few weeks you most likely read the headlines in the popular press, “MSN Messenger to end after 15 years”, “MSN Messenger Turned Off Forever!”, “Microsoft Is Officially Killing MSN Messenger Once and For All”, and similar captions of the same premise. Reading through these articles, you’ll find that Microsoft has sent out messages to the current Chinese users of Messenger, informing them that after October 31st they will need to use Skype to sign in, plus a bonus $2 Skype coupon for their trouble. The writers then jump to the conclusion that there will be no Messenger after that time, as it seems none of them have noticed that you can still use Messenger and that they’ve just been using Messenger in Skype.
With no other evidence to the contrary, Microsoft is most likely doing the same in China as it did for the rest of the world, force-upgrading its users to use Skype as their Messenger client instead of Windows Live Messenger.
Here are some facts about the situation:
- Messenger contacts (as of yet) did not transfer to Skype contacts. When you link your Skype username to a Microsoft account, Skype (or also Outlook.com) will sign you into both Skype and Messenger services. Despite the accounts being linked up, you can still sign into your Skype username separately or sign into your Messenger account separately using another Messenger client.
- Recently Microsoft started blocking users from signing into older versions of Skype. This seems to be primarily to push people into using the newer versions of Skype which support MSNP24 (Microsoft Notification Protocol version 24). To compare, Windows Live Messenger 2011/2012 uses MSNP21, so they are in fact transitioing from Skype’s native protocol to the Messenger protocol for all Skype communication. You can view the MSNP server and protocol information in Skype by opening up any Skype window and typing /dumpmsnp.
- The Messaging app included in Windows 8.0 (removed in 8.1) signs into the .NET Messenger service. As Windows 8.0 will remain supported until January 12, 2016, this client within 8.0 should continue to work within this supported time frame. This version of Messenger uses MSNP22.
- Although unsupported officially, third-party clients, Windows Messenger 4.7 above and “revived” clients still continue to work nearly a year and a half after the official shutdown date. These clients do not connect to Chinese servers or pretend to be in China.
- The dates of these forced-upgrades have been incorrect so far. Initially Messenger was to “shut down” on March 15th, 2013, and then was moved to April 8th. However, the forced compulsory Skype didn’t truly begin on the servers until April 23rd. Then more recently was the issue of “MSP” (not MSNP) first declared to be discontinued first in March of this year, then May, and then the reference was removed from the Microsoft website all together.
I have no idea when non-Skype Messenger clients will no longer be able to sign in.
Regardless of the facts above, Microsoft could still prevent non-Skype Messenger clients (and their subsequent versions of the protocol) from signing in at any time. I would personally implore them not to do so, as they only face to alienate more users to other services, particularly with their dwindling usage and increased competition. Additionally, once their move to the MSNP24 protocol on Skype is fully complete, they could open and encourage third-parties to write for that new protocol.
After reading through the most recent Messenger headlines, I think it’s worth a reminder that MSN Messenger was replaced by Windows Live Messenger in 2006. Everyone knows that Messenger is colloquially known as “MSN”, which can correctly refer to the protocol (MSNP) being used, but in reality the actual versions of software called MSN Messenger were discontinued and replaced in the years following the name change, particularly as older versions of the protocol were retired and security issues were found.
|Download Messenger Reviver 2|
March 12, 2015
Now Windows Live Messenger 2012 only
With the removal of the last servers supporting the older version of the Messenger protocol, versions of Messenger prior to Windows Live Messenger 2012 will no longer work.
If you’re using Windows XP, Mac OS X, Linux, or any other non-Microsoft Messenger client, you will need to either use Skype or the web-based Messenger client in Outlook.com.
Windows Live Messenger 2012 current issues:
- When you sign in you will briefly see a message indicating that your e-mail address is not verified. This started on on March 5th. It can be ignored.
- Hyperlinks will need to be copy/pasted to a browser as they presently don’t show up as a hyperlink.
Messenger Reviver 2 automatically installs, repairs and/or modifies Windows Live Messenger 2012, 2011, 2009, and 2008 as well as Windows Messenger to continue signing in despite being blocked by Microsoft.
Reviver 2 supports modifying all language versions and can automatically install either 2009 or 2011/2012 versions in 47 different languages.
You will receive one of the following messages if you’re being forced to upgrade to Skype:
A newer version is available. You must install the newer version in order to continue. Would you like to do this now?
A newer version has been downloaded and is available. You must install this newer version in order to continue. Would you like to do this now?
To bypass the forced upgrade, download my Messenger Reviver 2 utility and run the application. As this requires changes to Messenger you may receive a message asking you to allow Reviver to make changes to your computer.
Reviver will automatically attempt to detect if Messenger is still installed, which versions are eligible for modification and if you need to run a repair or new installation to bring Messenger back (if Skype has removed it).
Also available: Messenger Reviver 2 zipped if you are experiencing problems with running Reviver.
Windows Vista, Windows 7, Windows 8, Windows 8.1, Windows 10
To revive Messenger, click Start and the process will automatically modify Messenger and restart it.
If Windows Live Essentials is not installed, you will presented with options to either install Messenger 2009 or 2012 in the language of your choosing. Reviver will attempt to guess which language you prefer based on your prior Windows and Essentials language settings.
Additionally if Essentials is still installed, but Skype has removed it, you will be offered to repair your Essentials installation.
If you are attempting to revive Windows Messenger on Windows XP and do not have Windows Live Messenger already installed, use the Patch Messenger option in this menu to revive it without further Live Essentials installation.
As Messenger Reviver 2 will probably be my last exclusive Messenger project, I have added a few small Easter eggs into the application for fun.
Animated MSN butterfly
When you open Reviver, you’ll find an animated MSN butterfly in the main window. This is the original butterfly that flew around from MSN Messenger 5.0. Based on highly advanced software engineering, the butterfly will fly around, flaps its wings or just sit quietly. If you click the butterfly when it’s not busy, it will react accordingly.
If you click the About button, you’ll find the original Messenger signing in spinning animation in the top-left hand corner.
The MSN sound
Back in 1996, MSN had a sound they used for their advertising which accompanied the various letters of M-S-N. I was fairly fond of it, and I’ve included it in Reviver. Single-click the above mentioned spinner to initiate the sound and watch the letters light up.
Concise version history (full history)
|May 19 2017||2.4.9||
|May 17 2017||184.108.40.206||
|May 10 2016||220.127.116.11||
|Feb 12 2016||18.104.22.168||
|Jan 27 2016||22.214.171.124||
|Oct 3 2015||126.96.36.199||
|Aug 10 2015||188.8.131.52||
|Jul 29 2015||184.108.40.206||
|Mar 21 2015||220.127.116.11||
|Mar 17 2015||18.104.22.168||
|Mar 12 2015||22.214.171.124||
|Dec 20 2014||126.96.36.199||
|Dec 5 2014||188.8.131.52||
|Nov 13 2014||184.108.40.206||
|Apr 16 2014||220.127.116.11||
|Feb 19 2014||18.104.22.168||
|May 13 2013||22.214.171.124||
|May 07 2013||126.96.36.199||
|May 04 2013||188.8.131.52||
|Apr 25 2013||184.108.40.206||
|Apr 25 2013||220.127.116.11||
|Apr 24 2013||18.104.22.168||
|Apr 23 2013||22.214.171.124||
One of the most compelling things about some companies’ products is the small details the customer initially doesn’t know about but discovers after using the product. In Microsoft’s case, such details are usually usability features like a keyboard shortcuts or “intelligent” features to prevent extraneous typing. Very rarely are the small details visual in nature.
After sending a screenshot of my conversation window to a contact of mine as a joke, he identified something odd. The Sharing Folders icon in the toolbar showed the Windows Vista folder icon whereas on his Windows XP install, it was showing the XP folder icon. It’s a nice detail but I only hope that in the future other more important details might be done. I for one would like to see some Aero glass in Messenger, especially in toasts.
Here’s a screenshot of the differences of the two icons:
My Activity App is now up! You can check out my first Activity API application for Messenger, which I’ve dubbed Web Sharing here:
For those who haven’t read about how long it took to get this up, be sure to read my previous entry. Needless to say, it ended up taking a month, half a dozen e-mails and a blog entry to get the application up. So far there’s been no official response from Microsoft and I’ve been excluded from the latest mini-contest that I would’ve presumed I would’ve been included. So, I’m still not very pleased with the whole thing from the ridiculous amount of work and time required not building an app (it actually wasn’t that difficult) but just trying to get it up. Not only that, but even some final statement of apology would be nice.
Anyway, my inspiration for Web Sharing came from a long lost feature of MSN Explorer. For those who knew it existed or have forgotten, the feature was called "Browse the Web Together". You could initiate it from MSN Messenger 5 and assuming both people had MSN Explorer 8 and a paid MSN Subscription, an applet would appear full-screen with chat on the left and a web browsing pane on the right that both users would "share". With the introduction of MSN Messenger 6 and MSN [Explorer] 9, this functionality was removed and hasn’t been seen since.
There are some distinct differences between the two however. Firstly, Browse the Web Together let you see the other user’s cursor as it moved over the page. This was actually rather ridiculous as you couldn’t see them scroll down a page nor fill in forms. I thought about attempting to reproduce this silly feature as homage to the original but decided against it. Secondly, Browse the Web Together would follow links (with the exception of form POSTs) but Web Sharing simply opens a new browser window. If you want the user to follow the link, you have to copy/paste it back to the conversation window. Thirdly, unlike Browse the Web Together, Web Sharing monitors URLs in the current conversation (http:, https: and www.) so that you can continue copy/pasting links as you normally do.
Also, I’d like to give my friend Huuf some credit for the whole thing as he pointed out the IFRAME SECURITY attribute and gave me some pointers on how to improve the Regular Expression for detecting the URLs in the conversation.
If you have any comments or feedback on Web Sharing, feel free to let me know.