Outlook 2016 Encryption not encrypting

Topic

New Reply

I have a few systems with Windows 10 and Office 2016 that we’re just put into service recently. We use PKI certificates for signing and encryption keys, but recently I’ve noticed that messages that are created in outlook2 2016 that show they’ve been encrypted (no errors using  the recipients certificate, locked icon on sent message) show up as clear text to the recipient, or as blank (to other outlook 2016 users) with a smime.p7m attachment. Totally not encrypted (I can read it on my phone which does not have the certificate installed). The smime attachment is also a clear text copy of the message.

Any ideas?

Mark

Reply | Quote

Replies

How long has this been happening? What has changed recently?
Office/Outlook non-security patches were issued on June 6 and Patch Tuesday was last week. The Outlook security patch released on June 13th has been causing other problems with attachments.

If you can relate the problem to this time frame, I would suggest uninstalling the Outlook patch and using the utility wushowhide to prevent its reinstallation until you see if it solves the problem. I don’t know what else has changed for you, but I know updates were released.

This topic, although not related to your problems, has the patch number for last week’s issue.
https://www.askwoody.com/2017/microsoft-confirms-problems-with-june-2017-security-patches-for-outlook-provides-workarounds/

Let us know if this helps (or not).

Reply | Quote

Happening at least since last week (when we first noticed it). I’ve looked into installed updates on two of the affected systems and nowhere in the Installed update history are there ANY office updates. Researching more, looks like Office 2016 (not the 365 version) with their click to run model, installs updates using another update model that doesn’t show up anywhere. I can turn off future updates, but beyond redirecting to the Office 365 website change log, there is no where I can find so far to roll back any changes to the Office products.

It did work initially, when the product was first installed, I think my next step is to do a complete uninstall/reinstall of that suite and block updates before connecting it back to the outside world.

1 user thanked author for this post.

PKCano

Reply | Quote