Statement regarding KB3172519 and the april patch tuesday for Outlook 2013

[fbartels]

Last thursday we learned about an issue introduced with the latest Microsoft Patchday for Microsoft Office 2013, or more specifically KB3172519 (https://support.microsoft.com/en-us/...-april-11-2017). The patch provided through KB3172519 is an unusual one and unfortunately our current approach to restore functionality by adapting the Zarafa compat package, does not seem to provide a way to influence this new behaviour of Outlook. We are still investigating.


The current workaround is to remove this specific update from the workstation to restore the reply-all functionality.


For msi installations:
remove KB3172519


For C2R installations:
revert back to version 15.0.4911.1002 as described here: https://support.microsoft.com/en-us/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-click-to-run

cd “%programfiles%\Microsoft Office 15\ClientX64” (for 64 bits)
cd “%programfiles%\Microsoft Office 15\ClientX64” (for 32 bits)
officec2rclient.exe /update user updatetoversion=15.0.4911.1002

[hanspeter]

Please refer also to https://support.microsoft.com/de-de/...is-not-enabled to disable Click-to-Run Updates for the Moment

[fbartels]

Since our last update we looked a bit into the internal mechanics of the actual “why” an “object not found” is thrown, when trying to reply to an email. As it turns out, the already mentioned change to add the users email address when replying from outlook.com addresses also came with a change to the "Resolve names" functionality, that broke this for all account types that are not Exchange, Outlook.com or a local pst/ost (as it is with IMAP or ActiveSync connections). Sadly there seems to be no way to solve this without breaking other functionality, like lookup of user information from the mail header.


The “good” news on this topic is, that Zarafa does not seem to be the only Outlook addin that is suffering from this. According to a post on the Microsoft Technet a few other solutions seem to be affected by this change in Outlook as well.

[bcnx]

Hi,

this update is not in my list of installed updates. I do however see in the System Restore a security update has been installed on 20/04. Does anybody else see this update in the installed updates lst?

[bcnx]

Hi,

this update is not in my list of installed updates. I do however see in the System Restore a security update has been installed on 20/04. Does anybody else see this update in the installed updates list?

OK, I missed the C2R bit: the update will not be visible in the Updates list while using C2R installations. Mind the little error regarding the paths though: it is the same for 32 bit and 64 bit,

BC

[afischer]

Since our last update we looked a bit into the internal mechanics of the actual “why” an “object not found” is thrown, when trying to reply to an email. As it turns out, the already mentioned change to add the users email address when replying from outlook.com addresses also came with a change to the "Resolve names" functionality, that broke this for all account types that are not Exchange, Outlook.com or a local pst/ost (as it is with IMAP or ActiveSync connections). Sadly there seems to be no way to solve this without breaking other functionality, like lookup of user information from the mail header.

Hello,

are you still working on the issue or is the only "solution" the uninstallation of a security update?

Best regards
Achim

[fbartels]

Hello Achim,

solving it is sadly not possible. We added a statement about this to our blog and have sent out a newsletter to partners and customers today. You can find the blog at https://kopano.com/kb3172519-mission-reply-impossible/

[RemoStrotkamp]

KB3191889 from the May Patch Round reintroduced the Reply-All Bug for us with Outlook 2013

Deinstalling works as a workaround.

[RemoStrotkamp]

KB4011078 reintroduced it.

https://support.microsoft.com/de-ch/...3-july-27-2017

deinstall works