If 'Action' 'Configure' is performed for a plug-in, a process for that plug-in will be started, and will never expire (4036276)

There are only a couple plugins (SQL & Exchange) , that use third party libraries to be installed by Core installer.  As a result for these couple of plugins, since the process is running and the dlls are loaded, then those third party libraries will fail to be overwritten by the Core. Overall result, is that the plugin upgrade will fail.

This basically means that whenever you run Configure Action for SQL Server and Exchange plugins, the plugin binary will be locked forever. Upgrade will fail, and changes in the environment will affect this as well.

Examples of Cause:

* Plug-in is installed

* You run Configure Action; at that time an nv____.exe for the plug-in is created, for browse purposes, this exe will load the DLLs required at that moment, for example NNN.dll among others

* This nv_____.exe will be lock forever (Bug NVBU-15358)

* Changes affecting NNN.dll or its running environment might affect the plug-in next usage, and

* Upgrade attempts will fail, because nv_____.exe is being used (message: A key could not be installed ...)

Case Example - Windows 2012R2, SQL 2012 and SQL plugin v11.0.0.26, all was working fine.  Disabled SSL, TLS 1.0 & 3DES (and lower) Ciphers.  Once that was done NetVault SQL plugin can no longer authenticate for backups.  Attempts to reinstall/upgrade SQL plugin fail with Error. 

Possible Workaround:  Manually using Task Manager to 'kill process' any process for the NVBU plug-in affected, and/or re-enable the environmental changes made. (may not work for everyone)

Upgrade to NVBU v11.4, once it becomes available, as the issue is fixed in this version and will fix the plug-in process, it will expire in a timely manner.