Thank you very much, this is useful to know, also for others.
It may have to do with us calling the UA certificate generator as a separate executable/process.

If so, other notes/remedies to this might be:
1) When targeting .NET Core/.NET 5+, the certificate generation is done differently, inside the .NET code, so the external program is not invoked.
2) It is possible to pre-generate the certificate manually (outside of your QuickOPC application), and let the application just find it and use it. There is information in User's Guide that helps with this.
3) It is likely that QuickOPC 2022.2 or some other coming version will switch to the approach use by .NET Core/.NET 5+ currently also in .NET Framework targeting.

Best regards

In the meantime we could locate the problem: SOPHOS prevents QuickOPC's try to create the OPC UA certificate! As a workaround we deactivated SOPHOS temporarily and started our application once so that the certificate could be created. After that SOPHOS was activated again. Now our application runs without problems.

Yes, quite possibly.

And the same answer.

Best regards

I created a Config file based on the third code snippet ('complete file'), but without any effect.

I found the following post:

www.opclabs.com/forum/general-issues-building/3304-antivirus...en-starting-apps-with-quickopc

Maybe that's the same problem we have!?

Hello.

You can try the suggestions described here: kb.opclabs.com/How_to_disable_prerequisites_boxing . This disables a 3rd-party library that is doing some system hooks that might look suspicious to security programs.

Best regards

After changing to SOPHOS cloud-based virus scanner our QuickOPC-UA based program is terminated due to 'DynamicShellcode' by SOPHOS when trying to connect to the OPC UA server (see attached screenshot). The program worked without problems before and is still working if the QuickOPC code is deactivated.