Skip to main content
Jun 27, 2025 7:14 AM UTC
Acknowledged

Make it possible to digitally sign a Pro/TOOLKIT DLL after it has been unlocked successfully

Related products:Creo Parametric

1. Describe the Problem

After a Pro/TOOLKIT DLL has been compiled and unlocked successfully using protk_unlock.bat and will be digitally signed afterwards (these steps are described exactly like this in the Pro/TOOLKIT user guide), the DLL looses the "unlock" state and the popup "... has not yet been unlocked before distributing to your site..." comes up.

(This issue is already described in article "CS200080" with "No plans to Fix" in further Creo releases).

Recommendation: Remove the described possibility from the user guide if it's not possible to digitally sign the DLL or implement a fix for a further release.


2. Are you using a workaround?
The current workaround is to NOT digitally sign the Pro/TOOLKIT DLL.

3. What is the use case for your organization?
If it would be possible to digitally sign our application extension, we could ensure to the user that he's running a reliable extension. Furthermore we could ensure that it hasn't been manipulated by third parties using security check programs.

4. What impact does this problem currently have on your organization?
It currently not possible to ensure for the users to work with a trustable executable.

1 reply

Community Manager
Jun 27, 2025 9:01 AM UTC
Status changed to: Acknowledged

Thank you @dschork for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.