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.

Windows_Live_Mail_2015-12-11_19-55-26

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.

Installation
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.
Windows_Live_Mail_Setup_Wizard_2015-12-11_19-49-40

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

Usage
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 Outlook.com/Hotmail/POP3/IMAP 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.

 

Posted on December 11, 2015, in Live Mail, Outlook.com. Bookmark the permalink. 37 Comments.

  1. To start with, Thank you. A while back I had uninstalled the “not to be mentioned update” in order to recover from more of unexplained stops during syncing the 30 some email accounts that I have accumulated through 3 decades of using outlook express onward. I have been thrown for a loop when Windows Live mail stopped syncing correctly, jumping on outlook.com, or launching Outlook 2010 dreading to have to click on every separate inbox, just to be sure I haven’t missed crucial emails. Tonight I was going to give it one more fight to either get my beloved Windows live “Quick views” working again or dismantle the whole thing in ways I am not going to list here. YOUR SOLUTION saved the night, both the command line and the manual server settings together did the trick, all inboxes sync without a glitch. I verified that the repair worked for my version went back to 16.4.3528.0331 THANK YOU for sharing

  2. The crash is caused by calendar sync. If you log out from Live services the issue won’t appear. But the functionality will be gratly reduced since contacts and calendar sync won’t be available.

    • bonjour, pour cela il suffi de désactivé le calendrier, et sa refonctionneras, car j’ai u ce problème a un moment donner, et c’est ce que j’ai fait. et depuis je n’est plus ce genre de probléme.

  3. https://support.office.com/en-us/article/Windows-Live-Mail-2012-will-not-connect-to-Outlook-com-45453b92-373b-4bbb-88ca-f8ec74f8e8fd?ui=en-US&rs=en-US&ad=US

    Unfortunately, it seems the update has been cancelled, which means that WLM will NOT support the new Outlook.com

    • bonjour,remco,je ne c’est pas si windows live mail 2012 suporte outlook.com,mes moi en outlook.fr je n’est pas de probléme particulier,donc moi ce que je vous conseille c’est de mêtre votre outlook.com en outlook.fr,parce que moi comme je vous les dit je suis en outlook .fr et je n’est aucun probléme a ce sujet.

    • Yeah, so, now that Microsoft is moving forward with this migration in the next ten days, I’m looking into my alternatives. I’ve read elsewhere that while DeltaSync will no longer be supported, IMAP still will be. Thus, you could create a brand new instance of your e-mail account within WLM2012, and just configure it to use IMAP and it would still work, or you could use a third party e-mail client like Thunderbird to connect using IMAP. The official Microsoft supported protocol will, going forward, be MAPI (technically, MAPI/RPC) which is the proprietary protocol that Microsoft Outlook uses to communicate with Microsoft Exchange. Third party clients don’t support this, but IMAP will still be available. Can anyone else confirm any or all of this?

      • bonsoir,je pensse que sa doit être vrais parce que j’ai ressu le même message.mes je pensse qu’il font sa pour faire peur au gens, pour que sa les oblige a passer dans leure version a eux,mes si on résiste comme on l’a fait pour windows live messenger je pensse que sa ne ce fera pas mes pour cela il faut résister.

  1. Pingback: Outlook.com dropping DeltaSync support (and possibly MSNP) June 30 | Jonathan Kay, MessengerGeek

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: