Category Archives: Messenger

Messenger and the Windows Essentials installers removed from Microsoft servers

At what is no surprise to anyone, the Windows Essentials have disappeared from the Microsoft servers.

I did prepare for this situation for Reviver use and the Essentials installer files have been saved.  However, this does mean that installing Messenger for the time being will now be a larger download at 100MB.

Additionally, not all the languages will be available for the next few hours, if there is one you are in need of right now, please let me know in the comments and I’ll move it up in queue.

Signing out of the Skype app on Windows 10 Anniversary Update

If you use Windows 10, no doubt you have updated to the Anniversary Update (Version 1607, build 14393) which has a built-in Skype app called Skype Preview.

After using Reviver to revive Messenger on the new version of Windows, you may notice that Messenger will tell you you’re signed into multiple locations with the same device name.

Messenger status menu with two locations

This will happen if you use your Microsoft account to sign into Windows and the Skype app will automatically make use of your Microsoft account to sign you into the .NET Messenger network.

The biggest problem with this is that you’ll remain signed into Messenger, even if you’re signed out of Messenger or your computer is off as the Skype app operates on the Microsoft servers.  Additionally, even if you use Messenger to force the Skype app to sign out, the app will eventually sign you back in again on its own.

Thankfully you can choose to sign out of the Skype app and use the real Messenger client exclusively.  To do so, just head over to the Start menu and click on the Skype Preview tile (or find it on the applications list under S).

Windows 10 Start Menu with Skype Preview tile highlighted

When the Skype app opens, choose the hamburger menu button in the top corner and then choose your name at the bottom.

Skype app menu with options listed

You’ll then find a Sign out link under your name and info, clicking on the link should sign you out and then close the Skype app automatically.

Sign out link in Skype App

Now you’ll only be signed into one location.

Messenger status menu with one location

Signing out of the Skype app has been maintained through the insider builds, so you should hopefully only need to do this once.  You can always start the Skype app and sign in again if you would like to try the app at a later time.

 

Happy third anniversary Messenger Reviver 2!

Happy Anniversary

It was on this day, three years ago, that Messenger sign-ins started being blocked by the official Messenger client and three years ago that Messenger Reviver 2 was released.

Although we’ve lost some features over time, access to versions prior to 2009 and unfortunately most of the third-party clients haven’t kept up with the required changes, you can still use Windows Live Messenger today.

Thank you for your support!

Recent Messenger outages

UPDATE (2016-02-12): After more investigation, it seems the DNS reported in some regions (especially in Europe) will connect you to servers that are no longer operating.  Reviver has been updated to fix this issue.  If you are having this problem, please revive Messenger again using Messenger Reviver 2.4.7.

msnmsgr_2016-02-11_22-24-59

In the last 24-36 hours, a handful of users have been reporting infrequent outages resulting in error code 80072efd (can’t connect to the server).  Waiting a few minutes and just trying again usually will remedy the problem.

Four days ago it was reported on the forum that all the bn1 category servers had disappeared, but the actual connectivity problems with Messenger were not reported until several days later.

So far I have not seen the issue on any of my accounts and therefore have not yet been able to properly investigate the situation. However, at the moment my best guess is that the servers are being reorganized in some way and when you get the error message, you’ve been redirected to a server that is no longer operating. At the end of 2014, the same problem occurred when some of the servers started to phase out direct MSNP and HTTP access.  However, I think this might a bit of a different situation.

Although it may or may not be related, during the same time period I have also seen some disconnections with Skype causing it to sign out completely, which usually mean the server has signed me out automatically.  These sign outs might indicate that Skype’s infrastructure is also being changed too.

Unfortunately the inner-workings of the Messenger servers have never been completely fully known, so we’ll have to continue monitoring to see what happens.

Messenger Reviver 2 temporary download

Update:
Both Google and Microsoft unblocked the original Reviver links from their respective browser detection engines within 12 and 3 hours respectfully.

Although frustrating for the need to continually stay on top of these false positives, I do applaud them both for being quick and relatively painless to resolve the situation.

I have returned all the links, with the exception of this page, to the originals.


 

Here is a temporary link to download Messenger Reviver 2

Download Messenger Reviver 2

It seems someone doesn’t like the idea of Messenger Reviver and has reported all my links as malware.

2015-12-16_16-07-24

I suspect this may be related to McAfee being slow about removing a recent false positive.  Having these false positives removed takes up time in my life every week, but the antivirus vendors have always removed Reviver without question, although naturally they take their time about doing it.

I find the best way to check software (including Messenger Reviver) is to use virustotal.com.  The current analysis reveals that almost every vendor agrees it’s clean.

In the past, I have had infrequent threatening comments directed at me, specifically from those who trust their antivirus software without question and claim that I am harming their computer.  I have had my registrar falsely accuse of me of distributing malware, giving me a 24 hour warning to “remove it” or risk losing my entire account.  In all instances in these situations, after reviewing the real facts, these people stand down.

Ignoring anything else, just thinking logically, why would I, someone who has been assisting people with Messenger problems for for nearly 15 years, run a blog for 10 years, with comments, forum, live chat on a variety Messenger related topics, only to trick a few people into installing malware now.  Why would I ruin my reputation like that?  It just doesn’t make any sense.

Messenger Reviver does not do anything other than what it says it does.  It does not report any statistical data or personal data about yourself or your computer, it does not install anything other than Messenger, it does not contain ads, or contain any income-generating mechanism.  Messenger Reviver loses me time and money and it is simply a work of love.

Which is exactly why the icon for Reviver is Messenger with a heart.
reviver2.png

Thanks everyone for your support.

First look at Microsoft’s new “Messenger” client

UPDATE – Oct 12, 2015: A newer version (1.10.7000.0) is now included in Windows Insider Build 10565 which you can try out yourself by joining the Windows Insider program and being in the Fast ring.  Among possible other fixes, it includes a full emoticon set and the Ctrl key doesn’t seem to be sticking.

A version of Windows 10 leaked out late last week and contained within it was the long-awaited Windows Messaging Universal app.

Supposedly written from scratch, it’s the successor to the Messaging app contained in Windows 8.0 and the Skype WinRT app previously available (since withdrawn).  The executable is still named SkypeApp.exe however.

For these keeping track, this app is labelled as version Windows Messaging 1.9.26001.0:
Windows Messaging 1.9.26001 version windowThe user interface is barren when you begin.  Messaging window blankBut soon fills up when you start conversations:Messaging with conversationsWhen sending messages, Messaging claims they’re being delivered on Skype, which is technically not accurate as I was signed in with a non-linked Skype account and speaking only to .NET Messenger contacts.  I suspect Microsoft is trying its best to blur the difference.

Messaging runs in the background separate from the user interface itself and appears as a second location in Messenger while you’re logged into Windows.  After starting it for the first time, it took a while to start working initially and during usage, regularly disconnected.  There was no indicator in the actual Messaging app when these disconnections occurred and although messages appeared in the window as being sent, they weren’t delivered until later.  UPDATE: I observed later in the Event Log that the background SkypeHost.exe process was constantly crashing.  This is most likely the cause of the disconnections observed in the client.

Emoticons are extremely limited in this version, as well as being static and non-animated.  Space bar and backspace buttons are added presumably for use on touchscreens.  You can bring up Windows’ touch keyboard and use its standard emoji though. You certainly won’t be finding any custom emoticons here.
Messaging emoticonsThe paperclip in the conversation window does not function yet, but I assume will be used for sending files when activated.

There’s an integrated search function but it seems quite limited in its results as shown as individual lines of text.  Typing your search term too quickly seems to not put the search through, although adding a space to the end seems to help:

I also encountered multiple instances where it seems the Ctrl key on the keyboard got “stuck”.  Here’s an example where I’m trying to type Jon and as Ctrl-N starts a new conversation, when I get to the letter n, it starts a new window:

This problem was reproducible on multiple machines, so I don’t believe this to be a hardware problem. At least I was able to successfully put in my name by copy/pasting it to the box.

Toast notifications for Messaging have a textbox to reply back to sending contact and although you can type in them, I’ve found they work inconsistently.
Toast

A significant problem with the notifications is that once they’re gone, there’s no little indication that you received a message. The Messaging taskbar icon does not blink and the only way you’ll know you received a message is by opening up the Action Center or the Messaging app.

I’ll note that the notifications broke on all my machines after some light usage and never seemed to worked again, even after multiple reboots.

Sending messages is a bit painful right now, as upon presssing Enter to send a message, it adds a new line to the textbox instead of just sending the message. You have to press Ctrl-Enter to actually send the message. Hopefully this will changed or be an option in later builds.

Messaging has a select option and is the first of the built-in Windows 10 apps to support select all (a feature still painfully missing in Windows 10’s Mail app).  You can select conversations to mute or delete, as well as Delete, Copy and Forward individual messages.
Messaging forwarding

When you forward the message, Messaging makes a new empty conversation with that same text and if you switch to another conversation, it will make a draft just like an e-mail client.
Draft Messaging_2015-10-08_05-29-21

I’ve connected Cortana and Mail to my Office 365 account and Messaging seems to know about that too:
Messaging Office 365 2015-10-08_05-31-15Searching the Office 365 Directory didn’t seem to work yet however.  If you push the + button in the corner, another window shows all your contacts and offers to search the Skype Directory.  This doesn’t work either as it attempts to load a “skypepage” that doesn’t exist.
Search Skype DirectoryMessaging uses a separate Skype Video app to do voice and video conversations. I wasn’t able to get it to successfully call another computer but it does appear at least try to make a connection:
Skype_Video_2015-10-08_05-42-25Unfortunately you won’t find winks, custom emoticons, display names, animated display pictures, nudging, coloured text, customization, games, voice clips, or any other of the standard Messenger features in this application.  I couldn’t find an Options screen, so there isn’t much in the way of things to tweak.

Even compared to Windows Messenger that came with Windows XP, nevermind modern instant messaging clients like Facebook Messenger, WhatsApp, Viber, Telegram or Kik, Messaging still has a long way to go.

Butterfly Messenger

It’s no small thing to say that the reaction to Windows Live Messenger 2009 and related clients that use the older Messenger protocol has been pretty intense.  Regardless if you’re using Windows XP, you have a favourite feature that’s missing in the 2012 version, or you simply do not want to use Skype, it seems everyone is looking for another option to choose from.

Butterfly Messenger

Butterfly Messenger is an improved working version of the client used to demonstrate MSNPSharp.   It supports the same protocol version as Windows Live Messenger 2012 (MSNP21), and has the a basic Messenger feature set.

The current release is an alpha version of Butterfly Messenger intended to be used to collect feedback on bugs, features and other changes.  However, it is relatively stable and usable.

Butterfly Messenger

System Requirements

Butterfly Messenger currently requires Windows XP or above with at least the .NET Framework 2.0 or above installed.

Although MSNPSharp was deliberately written to support Mono (on other platforms), the client presently does not run on Mono (but probably works on WINE), hopefully this will be addressed later for Linux and/or OS X compatibility.

Download and installation

You can now download the third alpha release of Butterfly Messenger.  Due to the early nature of the project, it does not presently have an installer and you will need to extract the files to a folder of your choice and run it from there.  Butterfly Messenger makes use of the Segoe UI font (like Messenger).  If you do not have the Segoe UI font installed right now, you can install it from the Messenger 2009 files.

Feedback and bugs

Please feel free to leave quick comments here on this post, but if you wish to go in depth, you can make use of the Butterfly Messenger category on the forum.

Known issues

  • Depending on the situation, brand new conversation windows may blink even if they’re in focus.  If you start typing a reply, they should stop blinking.
  • Flickering in the contact list.
  • Custom emoticons will appear, but the current conversation window does not support animated GIFs.  Animated GIF display pictures work though.
  • You cannot rename contacts.

Open Source

Butterfly Messenger is open source software and based on the MSNPSharp project code.  A repository will be set up shortly once more details about the project have been finalized.

Oct 10 2015 0.1.2.0
  • Further nameserver exception fix
Sep 23 2015 0.1.1.0
  • Fixes Nameserver exception trying to connect to 25.127.129.101 by changing server hostname to the same one used for Reviver
Mar 25 2015 0.1.0.0
  • First alpha release of Butterfly Messenger

Older versions of the protocol no longer being accepted by any Messenger server

I’m sorry to report that this Thursday’s update ends the last bit of trickery for any clients prior to Windows Live Messenger 2012 (MSN Protocol Version 21).

You can see this for yourself using dx’s server list on www.ismsndeadyet.com.

On Thursday, February 26th, most of the servers removed MSNP18 support, but left a few bn1 servers allowing the old version and all db3 servers.
On Thursday, March 5th, the last of the bn1 servers removed MSNP18 support, leaving only db3 servers.
On Thursday, March 12th, the last of the db3 servers removed MSNP18 support.

If you’re using Windows 7, Windows 8 or Windows 10, and wish to continue using Messenger on its own, you will need to upgrade to Windows Live Messenger 2012.  You can do so by downloading and running Reviver again, clicking the Advanced button, selecting “Do a new Messenger install” and choosing Windows Live Messenger 2012.

If you’re using Windows Vista, despite being unsupported officially, with a workaround you can install Windows Live Messenger 2012 too.  I’ll be detailing this process shortly.

If you’re using Windows XP, Mac OS X, Linux, or any other non-Microsoft Messenger client (as of this writing, none I’m aware of support MSN Protocol 21), you will need to either use Skype or the web-based client in Outlook.com.  My efforts on bridging an interface between the newer and older protocol wasn’t terribly successful so far.  You can always use Messenger 2009 or other clients if they’re made to work again.

This is the end of an era.  Messenger Reviver 2 supported these older clients (including the popular 2009 version) from April 23 2013 to March 12 2015, they will be missed.

Messenger down again for pre-2012 users (error code 80072efd)

If you’ve been relying on the workaround from last week for versions of Messenger prior to 2012, beginning just a few minutes ago, a number of the Messenger servers disappeared and sign-ins on these prior versions are once again failing with error code 80072efd (which means, can’t connect).

Another workaround I was trying this week has not been successful, so you’ll have to upgrade to 2012, use the web-based Messenger version on Outlook.com or upgrade to Skype.
To upgrade to 2012 on Windows 7, launch Messenger Reviver 2, choose the Advanced button, then select Do a new Messenger install, and then choose Windows Live Messenger 2012.

If you’re using Windows Vista, version 2011 will not presently allow you to sign in, but this should be fixable eventually as it uses the same version of the protocol as 2012.
If you’re using Windows XP, you will need to use Outlook.com or upgrade to Skype for now.

A small number of users using pre-2012 versions are redirected into the “db3” servers, which revived clients will now automatically try.  With this in mind, if you are one of the lucky ones with an account that operates in this way, you may till be able to sign in or have contacts that do using these old versions.

Note: conversations on 2012 are sporadic right now, I’m going to assume once the current server changes are completed, it will go back to normal.

Major Messenger outage as MSNP and HTTP logins are rejected

Starting a few minutes ago, new sign-in attempts to Messenger are being rejected and depending on your account, you’ll now receive either error code 81000305 or 80004005.  Normally during the sign in process, the client and the server will negotiate the version of the protocol being used to access the service, but unfortunately the server is now rejecting the major versions of the Messenger protocol up to 18 (used by Messenger 2009).

With that said, Windows Live Messenger 2012 is still working over HTTPS.  If you need Messenger access right now, please either install Messenger 2012 or use the Messenger client in Outlook.com.

UPDATE (Feb 26/2015 18:24 EST): A workaround is now in place as one of the servers hasn’t been updated yet, but it most likely will not last long.  As this workaround is being done on the server side (DNS), depending on your ISP, it may take several hours.  Some accounts will still not be able to connect.