This afternoon Microsoft account based services like Messenger, Skype, Xbox, Outlook.com and others are experiencing intermittent issues.
In Messenger you’ll get error code 81000395 when you try to sign in. Additionally when you do sign in, contact lists may be incomplete.
Just keep trying and it should eventually allow you to sign in.
In the heyday of Messenger’s popularity, I had very little reason to use any of the other instant messaging services on a regular basis, because (almost) everyone used Messenger!
However, today’s XKCD comic expresses my current situation perfectly:
To further explain, here’s a screenshot of the messaging section of my taskbar.
There’s at least nine applications for instant messaging, not counting that some connect to more than one chat service. Within each application, I tend to have a completely different group of contacts, and some are used more so for audio, group, or exclusively text communication.
Although over time I’ve become more accustomed to knowing which contact is trying to talk to me on which application, and the required CPU and memory usage for each application hasn’t been too noticeable in general usage, searching for information can be quite difficult as the message history for each contact usually can only be searched within the application or service itself (or virtually not at all, Google Hangouts).
Recently Microsoft has shown that they are working on a feature (called My People) for Windows 10 that would pin contacts to the taskbar instead of individual applications. The feature has been delayed and may not work with existing desktop applications (which should be the subject of another article), so this may or may not help the situation.
Messenger on its own originally supported both the .NET Messenger Service/Windows Live and AOL Instant Messenger, and you can still see the basis of this if you hover over a contact in Messenger 2012 (look for the Networks: heading).
Additionally, Messenger originally supported a full API back in the 90s to allow others applications to fully communicate through Messenger without evening opening the program. This was quickly abused and scaled back slightly but the API is still usable and was made use of in tools like Messenger Plus!, Outlook, Outlook Express and others. Almost no instant messaging applications support this level of control now.
I’m curious how many messaging applications others use, so I’ve made a poll on the forum where you can indicate which applications you actively use on your PC.
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.
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).
When the Skype app opens, choose the hamburger menu button in the top corner and then choose your name at the bottom.
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.
Now you’ll only be signed into 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.
As I don’t believe the software or servers for DeltaSync are a component of the new foundation of Outlook.com (Outlook Web Access), it’s not clear how long DeltaSync will end up staying around.
Over the past week the persistent groups feature in Messenger has completely disappeared. If you had existing groups loaded in Windows Live Messenger or Butterfly Messenger, they will now appear as offline. Additionally, if you delete your locally stored cache of contacts or sign in somewhere you haven’t signed in before, you will see that any existing groups simply no longer exist.
Back on the server side of Messenger, if you attempt to access the groups or create another one, the service will reply with the error message “Circle no longer supported”. (Circles is the original name of the groups feature.)
Why this finally disappeared now is unclear, as the underlying groups feature in OneDrive had its demise back on October 16th and you haven’t been able to reliably create new groups in a while.
Additionally, this seems to be the end of group messaging on Messenger, as the alternative of adding people into conversations hasn’t been working since June of last year.
I’m thinking of making of a relay bot to get group messaging working again in some way, would anyone be interested in that?
If the title sounds familiar, it’s because this whole situation started back in December. Subsequently the disastrous KB3093594 patch was released to replace DeltaSync with Exchange ActiveSync, and then withdrawn. The patch was clearly rushed and untested, as it crashed on Windows 10 and usually fell short of fully synchronizing messages.
Just like back in December, a number of users have notified me that they’ve received an e-mail from Microsoft entitled “Action required for users of Windows Live Mail 2012”. This was sent last month and I’ve still yet to get my own copy of the message. I’m guessing you need to be a daily user of Live Mail to have received it.
The following are the important portions:
It appears that you are currently using Windows Live Mail 2012 to connect to your Outlook.com account. Windows Live Mail 2012 does not support the synchronization technologies used by the new Outlook.com. When account upgrades begin at the end of June, you will no longer be able to receive email sent to your Outlook.com account in Windows Live Mail 2012. Rest assured, you can always access your email by logging into Outlook.com from any web browser, and you will continue to have access to all your data that is currently in Windows Live Mail 2012.
Please take action before June 30th, 2016, which is when we’ll begin upgrading accounts that currently use Windows Live Mail 2012. If you have more questions, please find answers to common FAQs in this help article, or you can contact Microsoft support.
Both in the email and the above referenced help article, they do not cover using IMAP or POP3 as an alternative so you can continue to use Live Mail. Instead they’re more interested in pushing you to the Windows 10 Mail application or signing you up for Office 365. Re-adding your account using IMAP would be my recommendation if you make use of Live Mail and Outlook.com/Hotmail.
What does this mean for Messenger?
Even if you don’t have Messenger installed, Windows Live Mail 2011 and 2012 partially sign you into Messenger using MSNP21. This Messenger connection is used for e-mail notifications (when it worked) and although it’s technically a separate service, downloading your contacts. While the announcement from Microsoft specifically mentions receiving e-mail, which is done over the separate DeltaSync protocol, there is a possibility that this has been one of the key reasons that MSNP21 is still operating and therefore the protocol could be shut down on June 30th. Without further details there is no way to know until then.
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!
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.
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.
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.
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.
Thanks everyone for your support.
During the process of making Windows Live Messenger 2012 function on Vista earlier this year, I was also able to get Windows Live Mail 2012 working.
As Microsoft will not be patching Windows Live Mail 2011 to replace the DeltaSync protocol, you may find this helpful to install 2012 on Vista to avoid disruption if you’re using Live Mail.
Before you get started, you need to make sure you have all the requirements installed:
- Windows Vista Service Pack 2
- Windows Update KB971644 Platform Update (found in the optional updates section of Windows Update)
- .NET Framework 4.0
- Windows Live Mail 2011
If you do not already have Live Mail 2011 installed, I can supply installers of any supported language on request. If there is sufficient demand, I may add Live Mail into Reviver for clean installs.
If you had to install any of the above required components, please restart Windows before starting the process.
If you use Windows Live Movie Maker 2011, it will not be able to export movies after the upgrade.
Finally, download and run Messenger Reviver 2 which will upgrade Messenger, Mail, Writer, Photo Gallery and Movie Maker to 2012 versions.
|Download Messenger Reviver 2|
When prompted, click the link to install Windows Live Messenger 2012.
This installation tends to take a while, due to the age of the computers running Vista and the overall slowness of the Windows Essentials installer.
Once installation is complete, Live Messenger will come up, just close it.
Next, you will want to install the Windows Live Mail 2012 KB3093594 patch that swaps DeltaSync support for Exchange ActiveSync. Download and run the .msp file, then choose Repair when prompted.
After this is complete, click the Finish button and you can now start Windows Live Mail 2012!
Installing Essentials 2012 will force Windows to check updates, in which case svchost.exe may continue to consume CPU after installation and none of the Windows Live products will come up. You can either wait it out or restart Windows.