XCOM for Windows secure transfers crash after VMware cluster migration

Products

• XCOM Data Transport
• XCOM Data Transport - Windows

Issue/Introduction

XCOM for Windows r11.6 20041 SP03 64bit (only 1 PTF level after SP03 GA).
VMware cluster migrated to new location (XCOM not reinstalled) and received secure transfers have stopped working.
Tested an unsecure loopback transfer and it is successful.
Tested a secure loopback transfer and it fails when xcomtcp.exe crashes in libeay32.dll.
Backed up directory "%XCOM_HOME%\ssl" to test with XCOM self-signed certificates. Tried to run makeca.bat which calls openssl.exe and that also crashes.

Environment

Windows Server 2016.

Resolution

Installed the latest patch LU13921 (build 24061) which includes an OpenSSL update from an earlier patch. For that update the files ssleay32.dll and libeay32.dll are removed and the use of Broadcom OpenSSL package CAPKI is restored.
The crash problems were resolved and secure transfers started working again.

Additional Information

POSSIBLE ROOT CAUSE FROM XCOM ENGINEERING
Potentially the crash problems could have been due to missing dependencies or Visual C runtime libraries having problems with the OS version Windows Server 2016.
In the original SP03 GA and early PTFs the SSL transfer uses 2 libraries ssleay32.dll, libeay32.dll. The sample make scripts for self-signed certificate creation also use executable openssl.exe.
In addition, there is a dependency on the msvcr120.dll & msvcp120.dll C runtime libraries.
Perhaps some of the required  libraries were missing or latest Windows updates for 2016 may have caused problems, because Microsoft moved away from the private copies of runtime and encouraged applications to use common runtime from the system32 directory. The latter approach is used by XCOM starting in the 12.0 release, where the compiler was updated to Visual Studio 2019 and C runtime distribution was stopped. 

XCOM for Windows 11.6 Solutions (patches) page