Error adding a signature file or document with Secure Exchanges

If an error occurs when you try to attach a file or document for signature in an email protected by Secure Exchanges, it usually means that the file is already being used by another application or is temporarily blocked by your antivirus software. In most cases, this problem is caused by a conflict with the antivirus software, which prevents Secure Exchanges from accessing the files needed to protect or sign documents.

Setting up exceptions in the antivirus software will permanently resolve this problem.

Steps to Follow

1. Add Secure Exchanges to your antivirus's exceptions

For most antivirus software, you will need to:

1. Open your antivirus software.
   
2. Access settings or configuration options.
   
3. Search for the exceptions or exclusions section.
   
4. Add Secure Exchanges to the list of exceptions or exclusions.
   

Here is the list of exceptions to add:

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.commons.dll

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\phonenumbers.dll

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.barcodes.dll

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.layout.dll

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.forms.dll

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.io.dll

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.pdfa.dll

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.sign.dll

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.svg.dll

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.styledxmlparser.dll

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.kernel.dll

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\OSecureExchange.dll

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\JWT.dll

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\CsvHelper.dll

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\BouncyCastle.Crypto.dll

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\SecureExchangesSDK.dll

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\Newtonsoft.Json.dll

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\fr-CA\OSecureExchange.resources.dll

If it's not Windows Defender, you need to add Secure Exchanges to the exclusions of your third-party antivirus.

2. Restart Your System

Once Secure Exchanges has been added to the exceptions, restart your computer to ensure that the changes take effect.

3. Try attaching the signature file or document again

1. Open Outlook and try again to attach the signature file or document to your email.
2. Protect your email with Secure Exchanges as you normally do.
   

• Related Articles

• How do I configure Secure Exchanges in Outlook?

  Secure Exchanges offers several configurable settings directly within Outlook to tailor the security level, sending behavior, and signature management to your needs. This article explains each settings tab , specifying its purpose and how to use it. ...

• Create a list-based signature (bulk signature) with Secure Exchanges in Outlook Classic

  Secure Exchanges allows you to send the same document to be signed by several people in a single operation thanks to list signing (also called bulk signing or group signing). This feature uses a CSV file containing the signatories' information. Each ...

• How do I get a document signed in Microsoft Outlook using Secure Exchanges?

  This guide shows you how to send a PDF document for signature directly from Outlook, from A to Z: writing the email, adding the document, configuring the options and placing the signature areas. Prerequisites Before you begin, make sure you have: The ...

• November 26, 2025: Update to the PDFSignForm tool in Outlook Classic

  This procedure explains how to update the Outlook Secure Exchanges Outlook Area Sign Form tool. The update is necessary to ensure compatibility with the latest changes introduced by Microsoft. Important warning The steps below must be followed in the ...

• Microsoft error during installation or update of Secure Exchanges

  Microsoft Office may display an error message when installing or updating the Secure Exchange Connector in Outlook. In most cases, this problem is caused by a corrupted local cache used by Microsoft for installed applications. This error originates ...