Microsoft recently released an update that has begun to affect users of some of our add-ins. Specifically, the error looks like this:
It reads “Microsoft Office has identified a potential security concern. This document contains fields that can share data with external files and websites. It is important that this file is from a trustworthy source. Choosing Yes will enable updating all fields in this file, until you close it.”
The update is documented by Microsoft in KB4461625, and while it references Outlook 2010, it also affects Outlook 2013, Outlook 2016, Outlook 2019 and Office 365. Further, as noted it can happen in Word, Excel, or Powerpoint.
The underlying problem is that several of our add-ins use the temporary files folder as a space to write files that, well, are temporary. However, because Microsoft has reached a conclusion that the temporary files folder is now insecure, the error pops up as Microsoft designed.
When we first noticed the problem, we created our own KB article on How to add a trusted folder location to Word, however we were able to create a more permanent solution quickly since this problem began affecting so many customers.
So, we now have new versions of the add-ins that mitigate this problem by using a new temporary file folder location. The new versions are contained in version 6.2 and were released on Wednesday May 8th 2019. The add-ins that are affected are:
Regarding that last one – Safeguard Send – it “only” causes the Word security prompt to occur if there is a rule that searches the email and/or attachments for particular keywords.
So to fix this error:
- Exit Outlook
- Uninstall the add-in(s) via Control Panel…Programs and Features…Uninstall a Program
- Download then run the Uninstall Add-Ins tool
- Download a new version of your add-in
- Install it
- Restart Outlook
- Try your test again
If you don’t know how to get a download of your add-in, all the add-in downloads are listed here in alphabetical order, so simply scroll down in the list to find yours.
In any event, the problem should now be eradicated. If not, please get in touch with tech support.