Hi HomerJ,

I have had heard of this and there is a KM article addressing it (KM03793246) and the recommendation is the following:

Locate the "ALM-Client.exe.config" file located in the path where the ALM client files are located, usually in the user's profile: C:Users<wiindows_user>AppDataLocalHPALM-Client<alm_version>

For example: C:Usersalex_almAppDataLocalHPALM-Client15.51.0.0_952

Open the file for editing

Locate the element "<runtime>" in the file

Within the "<runtime>" section add the line: <loadFromRemoteSources enabled="true"/>

It should look like this...

<runtime>
<startup useLegacyV2RuntimeActivationPolicy="true">               This is the highlighted line in the KM document
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<probing privatePath="3rdParty"/>
<dependentAssembly>

Save changes and run the ALM Client Launcher Again

Hope this helps resolve your issue,

Dan