Reported by jasper, 2 years ago.

COBIA stub code will refuse to load COBIA runtime installed by a current user from an elevated process. This is a security measure to counter a possible DLL hijack by a current user replacing COBIA.dll or one of its dependencies.

Some installers elevate in a mixed-mode scenario even when installing for the current user. Particularly the default multi-user scenario of NSIS is subject to this.

This scenario in which COBIA is being installed for the current user, and the PMC registration is executed elevated, the PMC registration fails, as COBIA cannot be loaded.

Workaround is to provide a /ascurrentuser option to cobiaRegister that, in case it is started with elevated rights, will restart itself with the same command line options, impersonating the unelevated current user.

This option is to be specified by installers that run a current user installation mode with admin rights (elevated)

Reported by michelpons, 18 months ago.

COBIA code generation tools for Windows x86 platform are mentioned as optional in the dialog of the COBIA SDK MSI, when running a custom installation. Since their installation is optional, it is a bit weird to state that "This feature frees up 955KB on your hard drive". Like for the other optional features (e.g., COBIA Class Reference, COBIA IDL), why not simply states "This feature requires 955KB on your hard drive"?

Reported by michelpons, 18 months ago.

Within the Custom SDK installation setup, when choosing to not install the COBIA Class Reference, the GUI states "This feature requires 1 KB on your hard drive.". One expects a statement such as "This feature requires 0 KB on your hard drive." Or does it mean that, even if this feature installation is disabled, something related to it is still installed?