- Home
- /
- Troubleshooting
- /
- Startup
TMS is built from the ground-up on modules, called Extensions. Both TMS and Extensions are based on Threats Manager Platform (TMP), which is the engine behind it. This requires them to be somewhat aligned. On that account, each Extension declares which version of TMP requires. If there is a mismatch, TMS sends you an alert to notify you about the problem and the Extension which has the misalignment: in our example, XYX. This does affect TMS operation only in part: while the problematic Extension is not loaded, all other Extensions are not impacted. As a result, some metadata related to the said Extension may be lost when you save the Threat Model.
How to address the problem
The recommended behavior is to close TMS without saving the Threat Model, and then to install a version of the affected Extension compatible with the version of TMP used by TMS. In doubt, it is best to ensure both TMS and the installed Extensions are the latest versions published.
Threats Manager Studio (TMS) shows an orange message saying something like 'Extension library XYZ has not been loaded because it has not been signed'.How to address the problem
The recommended behavior is to close TMS without saving the Threat Model, and then to install a version of the affected Extension compatible with the version of TMP used by TMS. In doubt, it is best to ensure both TMS and the installed Extensions are the latest versions published.
TMS is built from the ground-up on modules, called Extensions. You may configure TMS so that it loads only libraries signed with a specific certificate. This is the message you get when an unsigned library has been found, while you require signed libraries.
How to address the problem
The recommended approach is to search for a signed Extension library. All Extension libraries distributed within this site are signed.
If it is not possible, you may decide to configure TMS to allow loading unsigned libraries. Please refer to Extensions Configuration for details on how to do that. Consider that loading unsigned libraries is highly discouraged because it represents a security risk.
Threats Manager Studio (TMS) shows an orange message saying something like 'Extension library XYZ has not been loaded because its signature is not trusted'.How to address the problem
The recommended approach is to search for a signed Extension library. All Extension libraries distributed within this site are signed.
If it is not possible, you may decide to configure TMS to allow loading unsigned libraries. Please refer to Extensions Configuration for details on how to do that. Consider that loading unsigned libraries is highly discouraged because it represents a security risk.
TMS is built from the ground-up on modules, called Extensions. You may configure TMS so that it loads only libraries signed with a specific certificate. This is the message you get when a library is signed with a certificate that is not recognized as valid.
How to address the problem
All Extension libraries distributed within this site are signed with the same certificate used for TMS. This represents the standard certificate.
To allow loading an Extension library that has been signed with a different certificate, you may add its certificate to the list of the certificates trusted by TMS to load Extensions. Please refer to Extensions Configuration for details on how to do that. Consider that trusting certificates for Extension libraries obtained from unchecked sources is highly discouraged because it represents a security risk.
After updating Threats Manager Studio (TMS) to the latest version, it shows an orange message saying something like 'Extension library XYZ has not been loaded because its signature is not trusted.How to address the problem
All Extension libraries distributed within this site are signed with the same certificate used for TMS. This represents the standard certificate.
To allow loading an Extension library that has been signed with a different certificate, you may add its certificate to the list of the certificates trusted by TMS to load Extensions. Please refer to Extensions Configuration for details on how to do that. Consider that trusting certificates for Extension libraries obtained from unchecked sources is highly discouraged because it represents a security risk.
This may be the result of the renewal of the certificates used to sign the Extension libraries, which was required because the old one has expired.
How to address the problem
Open the Options, and in the Extensions panel you should first remove the existing certificate issued to Simone Curzi from the list, and then click Add Default to replace it with the current one. Now you can restart Threats Manager Studio, and the warning should not occur anymore.
Threats Manager Studio (TMS) shows an orange message saying something like 'Extension library XYZ has not been loaded because it is not compatible with the current Platform'.How to address the problem
Open the Options, and in the Extensions panel you should first remove the existing certificate issued to Simone Curzi from the list, and then click Add Default to replace it with the current one. Now you can restart Threats Manager Studio, and the warning should not occur anymore.
TMS is built from the ground-up on modules, called Extensions. This error is generated when an error is raised while the Extension library has been processed by TMS.
How to address the problem
This represents an anomaly. The Extension library may be malformed or may have bugs that prevent loading it. Try finding a newer version.
Threats Manager Studio (TMS) shows an orange message saying something like 'Extension library XYZ has not been loaded because it is not designed for this client'.How to address the problem
This represents an anomaly. The Extension library may be malformed or may have bugs that prevent loading it. Try finding a newer version.
TMS is built from the ground-up on modules, called Extensions. Some Extensions are marked in a way that makes them not usable by the free version of TMS. If you get this error, then the affected Extension may not be for you and you should uninstall it. Other versions of the same Extension may present the same problem.
How to address the problem
Remove the affected Extension by uninstalling it.
Threats Manager Studio (TMS) does not start and you get a message from Windows Security Virus and threat protection, stating that it has blocked unauthorized changes requested by ThreatsManager.exe.How to address the problem
Remove the affected Extension by uninstalling it.
This is a result of the Anti-Ransomware Protection.
How to address the problem
Add ThreatsManager.exe as an exception, using function Allow an app through Controlled folder access which is available from the Ransomware Protection page of the Windows Security tool in Windows 10. The executable to be allowed should be proposed by the tool automatically, but otherwise consider that it typically is C:\Program Files (x86)\Simone Curzi\Threats Manager Studio\ThreatsManager.exe.
Threats Manager Studio (TMS) shows an orange message saying something like 'It is not possible to write the User Dictionary. If you have configured Ransomware Protection, please mark the Threats Manager Studio as trusted'.How to address the problem
Add ThreatsManager.exe as an exception, using function Allow an app through Controlled folder access which is available from the Ransomware Protection page of the Windows Security tool in Windows 10. The executable to be allowed should be proposed by the tool automatically, but otherwise consider that it typically is C:\Program Files (x86)\Simone Curzi\Threats Manager Studio\ThreatsManager.exe.
This is a result of the Anti-Ransomware Protection.
How to address the problem
Add ThreatsManager.exe as an exception, using function Allow an app through Controlled folder access which is available from the Ransomware Protection page of the Windows Security tool in Windows 10. The executable to be allowed should be proposed by the tool automatically, but otherwise consider that it typically is C:\Program Files (x86)\Simone Curzi\Threats Manager Studio\ThreatsManager.exe.
How to address the problem
Add ThreatsManager.exe as an exception, using function Allow an app through Controlled folder access which is available from the Ransomware Protection page of the Windows Security tool in Windows 10. The executable to be allowed should be proposed by the tool automatically, but otherwise consider that it typically is C:\Program Files (x86)\Simone Curzi\Threats Manager Studio\ThreatsManager.exe.