Known issue with Windows Server 2019 (AWS EC2)

This article explains a startup issue affecting io.Connect Desktop on certain Windows Server 2019 environments, especially AWS EC2 instances running io.Connect Desktop 9.13.x and earlier. In affected environments, the application may crash silently during launch because the installed Microsoft Visual C++ runtime is older than the version required by native components.

This issue is typically seen as a silent crash at startup with no visible error message. It is commonly associated with locked-down or infrequently updated machine images.

The issue is addressed in io.Connect Desktop 9.14 and later.

Prerequisites

Access and tools

  • Administrator rights on the affected machine
  • Access to the Microsoft Visual C++ Redistributable x64 installer

Environment

  • Products/components involved: io.Connect Desktop, Native Bridge, Microsoft VC++ Runtime
  • Affected versions: io.Connect Desktop 9.13.x and earlier
  • Fixed in: io.Connect Desktop 9.14+
  • Operating system: Windows Server 2019 on AWS EC2

Instructions

  1. Identify the symptom

    If io.Connect Desktop fails to start on a Windows Server 2019 instance and no error is shown, the machine may be affected by this issue.

    Expected result: You confirm that the failure happens immediately during launch and appears as a silent crash.

  2. Confirm the root cause

    Check the version of the following file:

    C:\Windows\System32\msvcp140.dll

    If the installed file version is below 14.40.33810, the machine is affected.

    Expected result: You identify whether the installed Microsoft VC++ runtime is older than the required version.

  3. Apply the immediate workaround

    Install the latest Microsoft Visual C++ Redistributable x64 from the official Microsoft download link:

    Microsoft Visual C++ Redistributable x64

    After installation completes, launch io.Connect Desktop again.

    Expected result: The application starts normally and the silent startup crash no longer occurs.

  4. Apply the permanent fix

    Upgrade io.Connect Desktop to version 9.14 or later.

    From version 9.14 onward, native components were changed so they no longer depend on the specific system runtime version that triggered this startup failure.

    Expected result: Future deployments are no longer exposed to this specific runtime-related startup crash.

The internal crash signature observed during investigation was INVALID_POINTER_READ_c0000005_MSVCP140.dll in mtx_do_lock.

Verification

  • Launch io.Connect Desktop after installing the VC++ Redistributable or upgrading the product.
  • Confirm that the application opens successfully.
  • Re-check C:\Windows\System32\msvcp140.dll if needed to verify the runtime version is now current.

Preventive Guidance

  • Prefer io.Connect Desktop 9.14+ for Windows Server 2019 deployments.
  • Review golden images used in AWS or enterprise environments and ensure the Microsoft VC++ Redistributable is updated as part of the base image maintenance process.
  • Include runtime validation in provisioning or health-check procedures for locked-down servers.