New
#131
Finally, an acknowledgment from Microsoft concerning this update KB3093594.
Known issues 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: Microsoft has identified the cause and has released a fix that addresses the issue for affected users on applicable platforms. To fix this issue, install this update that's released on December 17, 2015.- 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.
The update now shows a release date of 12/17/2015 and it appears to address the Calendar Sync issue predominately found to occur in Windows 10. I have tried it in Windows 10 and WLM 2012 no longer crashes when the Calendar is Syncing.
I realize that this update is not directly specified for Windows 10, but this new behavior is nonetheless encouraging.
Links that may be helpful:
https://www.microsoft.com/en-us/down....aspx?id=49486
https://support.microsoft.com/en-us/kb/3093594
Just to confirm, I have applied the revised update KB3093594 on quite a few machines-a mixture of Windows 7, 8.1. and 10.
Everything seems to work as expected now (although I did have to wait a bit for everything to sync the first time). I have not experienced any of the issues you described that you are still having. All of mine are the English version so I don't know if that makes a difference or not. Hope you get things worked out. Merry Christmas.
Looks like this update was pulled and will be updated at a future time.
https://support.microsoft.com/en-us/kb/3093594
Article ID: 3093594 - Last Review: 02/02/2016 03:02:00 - Revision: 8.0
I have WLM 2012 and on my Outlook account it is still using the old sync method that this update was changing to ActiveSync.Issues 3:Some customers have reported other issues with the release on December 17, 2015. This update is no longer being offered while Microsoft investigates these issues farther. Server interactions will remain supported during this investigation.
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.
I was late for this update as I was out of town when it came out so never got it.
Jim