Error Message

None.

This is by design per a process called code signing certificates. A certificate is generated for a certain validity, typically 1 to 2 years. The code (executable or other file) is signed using that certificate within the certificate's validity period, which then registers it with the certificate's issuing authority. After the certificate expires, the code is still valid as it was signed when the certificate was valid.

Here is an excerpt from https://knowledge.digicert.com/general-information/code-signing-certificate-faqs:

"Is timestamped code valid after a Code Signing Certificate expires?
DigiCert timestamp services allow you to timestamp your signed code. Timestamping ensures that code will not expire when the certificate expires because the system validates the timestamp. If you use the timestamping service when signing code, a hash of your code is sent to the timestamp server to record a timestamp for your code. A user's software can distinguish between code signed with an expired certificate that should not be trusted and code that was signed with a Certificate that was valid at the time the code was signed but which has subsequently expired."

To confirm this:

1. Navigate to the Client installation folder. The Client installation folder location depends on how the Client was installed:
- Per-User: C:\Users\\AppData\Local\Enterprise Vault Discovery Accelerator\Client\ 
- Per-Machine: The folder as specified during the Client's installation.

2. Right-click AcceleratorClient.exe | Properties | Digital Signatures  | Select the signature | Details.

3. Note the Signing Time listed in the General tab.

4. Click on View Certificate and compare the Signing Time with the Valid From and To dates.

5. If the Signing Time falls between the Valid From and To dates, the executable is valid, even if the certificate has expired.