In locked-down enterprise environments, io.Connect Desktop may fail to install or start if security software interferes with files the application needs at runtime.
This article covers three related scenarios:
- Startup fails blocked by user policy
- Antivirus blocks io.Connect Desktop files during installation
These issues can happen in environments with strict endpoint protection, AppLocker/WDAC-style controls, aggressive antivirus heuristics, or software-distribution pipelines that scan or modify installed files.
Symptoms
You may be seeing one of the following:
- io.Connect Desktop closes immediately during startup
- widgets or interoperable applications do not load because io.Connect Desktop never initializes
- antivirus reports some bundled files as malicious during installation
Scenario 1: Startup fails because security software blocks native modules loaded during startup
Typical symptoms
On affected systems, logs may show errors similar to:
This program is blocked by group policyERR_DLOPEN_FAILED- references to
.nodefiles being loaded from the user profile Temp location
In some environments, Electron can extract native modules from app.asar and load them during startup. If Windows group policy, AppLocker, WDAC, endpoint protection, or antivirus blocks those files from being created or executed, io.Connect Desktop can fail before initialization completes.
In one case we’ve seen Windows blocking a native module loaded from the user’s %TEMP% path and the process terminated during bootstrap
How to fix it
Review (or ask IT/security to review) controls that apply to:
- rules affecting Temp folders
- endpoint protection rules for extracted native modules
- AppLocker / WDAC / group policy restrictions on executing binaries from temporary locations
- antivirus or EDR quarantine activity
And:
- allow io.Connect Desktop to create and load its required runtime files from the user Temp/cache location
- whitelist the relevant Temp/cache path used during startup
- ensure endpoint protection is not deleting, quarantining, or blocking
.nodefiles
What to check
Use this checklist:
- confirm the user can access
%TEMP% - confirm
%TEMP%is not subject to unusual storage restrictions - check whether antivirus or endpoint protection quarantined any runtime files
- check whether the environment blocks execution from Temp
- compare with an unaffected user on the same rollout if available
Version note
After io.Connect Desktop 9.10.1 files involved in startup are located in the application cache, which avoids the earlier startup path that could be blocked in some enterprise environments by group policy, AppLocker/WDAC, or endpoint protection. If you are seeing this behavior on an older 9.10 build, upgrade to 9.10.1 or later.
Scenario 2: Antivirus flags io.Connect Desktop files as malicious during installation
Typical symptoms
During installation, antivirus may flag files such as:
- bundled JavaScript dependencies
- helper scripts such as
.cmdfiles - third-party libraries included in the application bundle
What is happening
This is typically a false positive caused by antivirus heuristics, not malware.
How to fix it
- verify the digital signature in Windows before approving the application. This helps confirm the files are genuine and have not been tampered with.
- whitelist the io.Connect Desktop installation folder
- re-run the installation if files were already quarantined
- verify the installer and executable signatures before allowing them
What information to collect for support
Before escalating, collect as much of the following as possible:
- full startup logs
- the exact error message shown to the user
- any antivirus or EDR detection name
- the exact file path that was blocked or quarantined
- confirmation whether the issue affects one user or many
- the io.Connect Desktop version
- whether reinstalling resolves the issue
- whether the environment blocks execution from
%TEMP%