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.


DeltaSync still working in Windows Live Mail


At what comes at really no surprise, Windows Live Mail’s Hotmail/ DeltaSync protocol that was supposedly being discontinued yesterday, is still working normally today.

As I don’t believe the software or servers for DeltaSync are a component of the new foundation of (Outlook Web Access), it’s not clear how long DeltaSync will end up staying around.

Groups feature disappears

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? dropping DeltaSync support (and possibly MSNP) June 30

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 account. Windows Live Mail 2012 does not support the synchronization technologies used by the new When account upgrades begin at the end of June, you will no longer be able to receive email sent to your account in Windows Live Mail 2012. Rest assured, you can always access your email by logging into 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

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.



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.


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

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  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.

Installing Windows Live Mail 2012 on Windows Vista

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.

reviver click 2015-12-12_02-01-51

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.

repair 2015-12-12_02-30-10

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.


The craziness of Windows Live Mail patch KB3093594

As mentioned previously, Microsoft has elected to discontinue the DeltaSync protocol of Windows Live Mail 2012 for Exchange ActiveSync.  This is to be done using a Microsoft Installer patch filed under KB3093594, Update for Windows Live Essentials Mail 2012.

However this patch doesn’t appear to have been fully tested nor is it made simple to install.

Windows 10 support
Most importantly, after installing this patch, Live Mail will no longer work on Windows 10.  Live Mail will open up, but within seconds it crashes with the standard, Windows Live Mail has stopped working.


This crash was repeatable on multiple machines of different bitness and Windows builds.  The actual exception is an access violation in wcsync.dll (which is one of the patched libraries).

If you want to go ahead and try to install the patch or if you already did, you can revert/uninstall the patch by pressing oldwindowsflag-R (Windows Key and R) on the keyboard, then copy/paste the following:

msiexec /package {B775C26B-EAA8-4A11-ACBF-76E52DF6B805} /uninstall {342DCD5D-5946-453B-97AC-D53B7662EDF5}

Then press enter or click OK.  When prompted, choose Repair.

Furthermore, even the installation of the patch (KB3093594) is simply awful.  After running the .msp (Microsoft Installer Patch file), you’re offered to either Repair or Remove Live Mail.  Choosing Repair is the only way to get it to install.

After installation, the version number of Windows Live Mail will change from 16.4.3528.0331 to 16.4.3563.0918.

Installing this patch does not add any new functionality to Windows Live Mail 2012.  The only difference is that the DeltaSync protocol been swapped out with the Exchange ActiveSync protocol.  Live Mail still only allows use of email accounts, and you cannot use your own Office 365 or Exchange server account.  Additionally, push email support has not been restored, as Live Mail still uses Messenger to notify Live Mail for new messages.  Unfortunately, this particular feature in Messenger has been broken since April 2014.

As much as we can appreciate Microsoft continuing support for Live Mail, certainly it would have been better if they fully tested this on the latest Windows version, as well as made it easier to install or just utilized Windows Update to deploy the patch automatically.


Microsoft to discontinue DeltaSync (for Windows Live Mail)

A good friend of mine got the following email today:

Important information about your email service

Dear user,
In a few weeks, we will be making some changes to our email services that might impact your, @hotmail, @live, or @msn email account. Those changes will prevent your email from being delivered to the Windows Live Mail 2012 application you use.
In order to continue using Windows Live Mail 2012 to send and receive email for your account, you need to install the latest update published here.
If you use Windows Live Mail 2012 on Windows 8, Windows 8.1 or Windows 10, we recommend that you switch to the built in Mail app in Windows to stay connected and get the latest feature updates on Windows 8, Windows 8.1, and Windows 10.
Windows Live Essentials 2009 and 2011 are not supported anymore, and you will need to update to Windows 8/8.1 or Windows 10 and use the Mail app, or use To learn more about the Mail app, please click here.
We also recommend all Windows Live Mail users on Windows 7, Windows 8, and Windows 8.1 to upgrade to Windows 10 and use the built in Mail application to stay connected and get the latest feature updates.
We suggest saving this email so you can refer to it later.
Thanks for your understanding and continued use.

The Outlook team

Although not officially mentioned in the message, Windows Live Mail 2012 uses the DeltaSync protocol to send and receive email for accounts, so it can be assumed that they are discontinuing this protocol.  Prior to DeltaSync’s creation, Outlook Express used WebDAV, which itself was shut down in 2009.

With the patch linked in the email, KB3093594, Microsoft seems to have elected to continue to support Live Mail 2012 by replacing the DeltaSync protocol with Exchange ActiveSync.

As much as I can tell, after installing this patch, Live Mail will no longer work on Windows 10.  Live Mail opens up, but within seconds it crashes:

Windows_Live_Mail_2015-12-11_19-55-26Additionally, the Exchange ActiveSync support is extremely rudimentary and fixes none of the existing issues with mail notifications.

I’ve continued and elaborated my discoveries, as well as how to revert the patch on my next post.