Windows Certificate Issue - HOOPS Binaries
This is a live page. Please check content regularly.
Table of Content : |
|---|
Issue Description
We identified a critical issue affecting Windows platforms only.
Due to the removal of timestamping in our signing process last year, all HOOPS SDK binaries signed with the current certificate will lose OS trust after the certificate expiration on Aug 28, 2025.
Downloading a newly signed version from the https://developer.techsoft3d.com/start and updating your installation is mandatory to ensure continued compatibility and avoid OS-level restrictions.
The actual impact depends on how the software using our technology was built and on the configuration of the client machines.
Failure to update may result in security warnings for dynamic libraries and/or execution restrictions when running an *.exe loading these binaries.
DLL Warning
Microsoft Defender Warning
Impacted HOOPS Versions
This issue affects only the versions listed below. Please ignore the information sent on our communication by email.
Toolkit | Affected Version | Patched Version | Forecast or Delivered Availability |
|---|---|---|---|
HOOPS Exchange | 2025.6.0 | 2025.6.1 | 2025-08-28 1700 CET |
2025.5.0 | 2025.5.1 | 2025-08-28 1800 CET | |
2025.4.0 | 2025.4.2 | 2025-08-28 1800 CET | |
2025.3.0 | 2025.3.4 | 2025-08-28 1800 CET | |
HOOPS Communicator | 2025.6.0 | 2025.6.1 | 2025-08-28 1600 CET |
2025.5.0 | 2025.5.1 | 2025-08-29 1600 CET | |
2025.4.0 | 2025.4.1 | 2025-08-28 1600 CET | |
2025.3.0 | 2025.3.1 | 2025-08-28 1600 CET | |
2025.2.0 | 2025.2.1 | 2025-09-04 1800 CET | |
2025.1.0 | 2025.1.1 | 2025-09-04 1800 CET | |
2024.8.0 | 2024.8.1 | 2025-09-05 1800 CET | |
HOOPS Visualize HPS | 2025.6.0 | 2025.6.1 | 2025-08-28 1600 CET |
2025.5.0 | 2025.5.1 | 2025-08-29 1600 CET | |
2025.4.0 | 2025.4.1 | 2025-08-29 1600 CET | |
2025.3.0 | 2025.3.1 | 2025-08-29 1600 CET | |
2025.2.0 | 2025.2.1 | 2025-09-01 1600 CET | |
2025.1.0 | 2025.1.1 | 2025-09-01 1600 CET | |
2024.8.0 | 2024.8.1 | 2025-09-04 1800 CET | |
HOOPS Visualize 3DF | 30.20 | 30.21 | 2025-08-28 1600 CET |
30.10 | 30.12 | 2025-08-29 1600 CET | |
30.00 | 30.01 | 2025-09-03 1800 CET | |
29.40 | 29.41 | 2025-09-03 1800 CET | |
27.58-LTS | 27.59-LTS | 2025-08-29 1600 CET | |
HOOPS Luminate | 2025.5.0 | 2025.5.1 | 2025-08-28 1600 CET |
2025.3.0 | 2025.3.1 | 2025-08-29 1600 CET | |
2025.1.0 | 2025.1.1 | 2025-08-28 1600 CET | |
Demo Applications | Affected Version | Patched Version | Forecast or Delivered Availability |
HOOPS Demo Viewer | 2025.6.0 | 2025.6.1 | 2025-08-28 1600 CET |
HOOPS Parasolid Viewer | 2025.6.0 | 2025.6.1 | 2025-08-28 1600 CET |
HOOPS Exchange Demo | 2025.6.0 | 2025.6.1 | 2025-08-28 1800 CET |
Workaround
Windows allows the execution of an executable with an expired (invalid) or missing signature by using the “Run anyway” option.
To access “Run anyway”, select “More info” on the warning screen :
FAQ
Are the new DLLs binary compatible with the existing DLLs? Can customers simply overwrite the old DLLs with the new ones?
Yes, the new DLLs are binary compatible with the previous versions. The only change is an updated digital signature.
For example, version 2025.6.1 is binary compatible with and identical to 2025.6.0 except for the updated digital signature.
Customers should, however, confirm whether the expiring signature affects their application, as testing and field reports have shown mixed results regarding Windows OS warnings.Do customers need to recreate their installers with the new HOOPS DLLs?
This depends on how the installer validates DLL signatures. In most cases, customers should verify whether the expiring certificate impacts their installer. If it does, the installer may need to be recreated with the updated DLLs.Is this issue limited only to the HOOPS versions listed in the table?
Yes, the issue affects only the listed versions.
Final Words
We apologize for this inconvenience and ask for your cooperation as we work diligently to resolve it.
Thank you for your prompt attention. If you have any questions or need support, please contact us.