Overview
This article provides a step-by-step guide for resolving JavaScript errors when installing or launching the Timus Connect application on Windows. These errors are commonly caused by missing permissions or interference from endpoint security tools like BitDefender, Windows Defender, SentinelOne, and ThreatLocker. You’ll also learn how to properly configure exclusions and allowlisting to ensure smooth installation and operation.
Uncaught Exception: Error: EPERM: operation not permitted, mkdir ‘C:\ProgramData\Timus Connect’
This error indicates that the installer was unable to create a required folder due to permission issues or security software interference.
A similar error may also occur when attempting to create:
C:\Program Files\Timus Connect
✅ Pre-Installation Checklist
Before proceeding, ensure the following:
- Administrator Rights
The installer (Timus-Connect.exe) must be run with elevated privileges. - Disable Conflicting Tools
Close any VPN or network security tools (e.g., Todyl, other VPN clients) that may interfere with the network stack. - Stable Internet Access
Ensure the machine can access Timus services—see allowlisting requirements below.
🛠 Step-by-Step Resolution
1. Run the Installer as Administrator
- Right-click on
Timus-Connect.exe→ Select Run as administrator - If deploying via RMM, ensure it's executed in the Local System or Admin context
- ⚠️ Do not run the installer from a network share—copy it to a local folder first
2. Manually Create Required Folders (Optional Workaround)
To prevent EPERM errors:
- Open File Explorer or Command Prompt as Administrator
- Create required folders:
mkdir "C:\ProgramData\Timus Connect" mkdir "C:\Program Files\Timus Connect"
- Set folder permissions:
- Right-click folder → Properties → Security → Edit
- Add the Users group with at least Modify rights
- Ensure Administrators and SYSTEM have Full Control
⚠️ Only grant the minimum permissions required. Avoid giving "Everyone" access.
3. Configure Security Software
🔒 Bitdefender (Endpoint or GravityZone)
- Policy → Antimalware → Exclusions
Add:C:\ProgramData\Timus ConnectC:\Program Files\Timus ConnectTimus-Connect.exe
- Firewall: Allow outbound HTTPS over port 443 (TCP/UDP)
🛡 SentinelOne
- Local Agent:
- Add exclusions for
Timus-Connect.exe,C:\ProgramData\Timus Connect, andC:\Program Files\Timus Connect - Add app to Controlled Folder Access
- Add exclusions for
- Managed Environment:
- Ask your security admin to allowlist the hash of
Timus-Connect.exe
- Ask your security admin to allowlist the hash of
- Optionally, temporarily disable protection during installation
🔰 Windows Defender
- Add the following under:
Windows Security → Virus & Threat Protection → Exclusions- Folder:
C:\ProgramData\Timus Connect - Folder:
C:\Program Files\Timus Connect - File:
Timus-Connect.exe
- Folder:
- If Controlled Folder Access is enabled:
- Allow
Timus-Connect.exevia:Manage ransomware protection → Allow an app through Controlled folder access
- Allow
⚙️ ThreatLocker
- Allow
Timus-Connect.exein Application Control policies - Whitelist paths:
C:\ProgramData\Timus ConnectC:\Program Files\Timus Connect
- If issues persist, temporarily switch to Audit Mode during install
⚠️ Re-enable protection immediately after installation
4. Allowlist Required Domains & Ports
🔗 Domains
If wildcard rules are supported, allow:
*.timusnetworks.com*.timuscloud.com
Otherwise, allow:
auth.timuscloud.comuser.timuscloud.comdevice.timuscloud.comconfig.timuscloud.commy.timusnetworks.com
🌐 Ports
Ensure the following are allowed:
| Port | Protocol | Purpose |
|---|---|---|
| 443 | TCP & UDP | HTTPS communication |
| 53 | UDP & TCP | Local DNS (127.0.2.1:53) |
| 1195 | UDP | OpenVPN |
| 1196 | UDP | WireGuard |
| 7505 | TCP (localhost) | OpenVPN management (127.0.0.1) |
| 49202 | TCP (localhost) | Local Connect Service |
| 49204 | TCP (localhost) | Connect Helper Service |
If behind a proxy, configure it to allow Timus-Connect.exe access to these domains over port 443.
5. Re-run the Installer
- Reboot the machine (recommended)
- Try to install Timus Connect Application again.
Updated
Comments
0 comments
Please sign in to leave a comment.