There are many users who still use Windows Live Mail 2012 as their Mail client. Windows Live Mail 2012 was the last Mail client, its part of the Windows Essentials 2012 suite released by Microsoft. After this version, Microsoft has stopped releasing the updates and wants users to shift to the newer Mail app that comes with Windows 8.1 and Windows 10.
The KB3093594 re-released:
In the second week of this month, Microsoft had alerted Windows Live Mail 2012 users that some chnages are coming to users of Microsoft accounts like Outlook, Live, Hotmail, MSN accounts that may prevent mails being delivered to Windows Live Mail 2012. And it said, in order to continue using this Mail client, you need to install this update.(Update for Windows Live Essentials Mail 2012 (KB3093594) )
But after installing this KB30393594, some Windows Live Mail 2012 users started reporting about facing stability issues. The Windows Live Mail would crash on launching it. Reacting to this, Microsoft said “We have identified the root cause and are currently working on a fix that addresses the issue for impacted users on applicable platforms.”
And then Microsoft re-released Update for Windows Live Essentials Mail 2012 (KB3093594). So users who had previously installed this update and were facing cash on launch of Windows Live Mail 2012 should download and re-install KB3093594 and the issue wil be resolved. Download it from here. So the issues listed below will be fixed by installing this re-released update.
Known issue and solution about this update
- Issue 1: After you install this update (that was released before December 17, 2015), you may find that the program crashes soon after start.
Solution: If you installed this update before December 17, 2015, you may have experienced a crash in the Windows Live Mail app soon after start. To fix this issue, download and reinstall the same update that's described in this article.
- Issue 2: After you install this update that's released on December 17, 2015, you may experience mail sync issues.
This issue occurs because of a server-side problem. Microsoft is researching this issue and will post more information in this article when the information becomes available.