Our users are using ALM Client Launcher and when they started to use new version ALM24.1 they received this kind of SpiderHost security warning where they should have selected the first option 'Always install....'. In case they didn't choose it, they received error messages related to setup_a.cap file. 

To solve the download issue with end users (after they had selected wrong option to SpiderHost warning), there was first needed to modify internet options, i.e. remove Open Text corporation from untrusted publisher and then start download again with correct selection to SpiderHost warning.

Hope this would give you some help to solve your problem too.

Hannele, 

this is a different issue, but the issue you described can be resolved by using the latest ALM Client Launcher. This is because old version ALM Client Launcher does not know the new certificate on the product. 

Massimo, since your alm client is installed through the msi. You need to create a new client msi on top of the 24.1 version and install it again on the client machine. However, I would recommend you to try alm client launcher, would you mind to remind me what blocks you from using the client launcher? I will be glad to help. 

Hi Hannele and Mike,

thank you very much for your advice. I appreciate so much. 
The problem we suppose could be related to some policy that are applied to some users. The error appears in both cases: using ALM Explorer or ALM Client Launcher. 

We're going to investigate further and I'll update you as we'll find the cause.

Thank you,

Massimo.

Hi Mike! Just to confirm, do you mean that only Launcher ver 4.4. can handle the new certificate correctly? And e.g. ver 4.2 does not?

Try windows update, and make sure GlobalSign GCC R45 EV CodeSigning CA 2020 exists in Trusted Root