Desktop App for Windows 4.2.0 – Migration to 64-Bit Client

Overview

Version 4.2.0 marks the full transition of the Egnyte Desktop App for Windows to a 64-bit architecture. All Desktop App components are now delivered as 64-bit binaries, and the installation directory has moved from C:\Program Files (x86)\Egnyte Connect\ to C:\Program Files\Egnyte Connect\.

Most environments will upgrade without requiring configuration changes. Administrators using custom deployment scripts, path-based security policies, or antivirus exclusions referencing the previous installation path should review those configurations before deploying.

Release Plan

• Version 4.2.0 is available immediately as a manual download from the Helpdesk Installers page and in Apps and Integrations.
• Automatic Upgrades from version 3.31.1 will not be enabled immediately, giving administrators time to review and update their environments. Advance notice will be provided before automatic upgrades are enabled.
• Version 3.31.1 remains available under the current static download link during this transition period.

Reason for this Change

The move to 64-bit is driven by the ongoing industry-wide end-of-life trajectory for 32-bit operating systems and applications. Continuing to ship a 32-bit Desktop App would limit compatibility with modern Windows environments and constrain future platform enhancements. This transition ensures the Desktop App remains sustainable and capable of supporting new capabilities going forward.

Quick Overview of Necessary Action Items

Use Case	Action Required
Standard installation or upgrade, no custom scripts or tools	Update antivirus exclusions only
Custom deployment scripts or automation	Update antivirus exclusions + Update path references in scripts
Mass deployment with reboot suppression	Update antivirus exclusions + Update antivirus exclusions + add ED_UPDATE_ON_BOOT=1 flag
Upgrading from a previous 4.x build	Review antivirus exclusions to cover both directories

Direct Upgrade or Installation

For users and administrators performing a standard (non-scripted) installation.

Steps

1. Download the Egnyte Desktop App 4.2.0 MSI from the Desktop App Installer page or the Apps and Integrations on Web UI.
2. Run the installer. It will handle the upgrade from any existing installation automatically.
3. If prompted, restart the system to complete the installation.

Antivirus and Endpoint Security Exclusions

Because the installation directory has changed, antivirus or endpoint protection policies must be updated to exclude both paths during the transition period:

• C:\Program Files (x86)\Egnyte Connect\
• C:\Program Files\Egnyte Connect\

Excluding both ensures that devices still running earlier versions are not impacted while the rollout progresses.

For detailed guidance, refer to the Antivirus Policy documentation.

Repercussions of Skipping the Antivirus Update

If antivirus exclusions are not updated before or during the upgrade, endpoint security software may flag or block Desktop App binaries at the new installation path. This can result in the Desktop App failing to launch, unexpected disconnections, or degraded sync performance.

Mass Deployment

For administrators deploying via MDM, scripts, or automation tools.

Steps

1. Download the Egnyte Desktop App 4.2.0 MSI from the Desktop App Installer page or the Apps and Integrations on Web UI.
2. Review any deployment scripts, automation tools, or monitoring integrations that reference the previous installation path (Program Files (x86)) and update them to point to the new path (Program Files).
3. Deploy using standard tooling of choice. If the environment suppresses automatic reboots, include the ED_UPDATE_ON_BOOT=1 flag (see below).

Standard Silent Install (Reboot Allowed):

EgnyteDesktopApp_4.2.0.msi /quiet

Silent Install with Reboot Suppressed (MDM/Scripted Environments):

EgnyteDesktopApp_4.2.0.msi /quiet /norestart ED_UPDATE_ON_BOOT=1

OR

EgnyteDesktopApp_4.2.0.msi /quiet REBOOT=ReallySuppress ED_UPDATE_ON_BOOT=1

When ED_UPDATE_ON_BOOT=1 is used, the installer stages the upgrade and completes it automatically on the next device restart. The MDM solution will receive exit code 3010, indicating success with a reboot pending.

Antivirus and Endpoint Security Exclusions

Push updated antivirus or endpoint security policies before or alongside the Desktop App deployment. Exclude both paths across the fleet during the transition:

• C:\Program Files (x86)\Egnyte Connect\
• C:\Program Files\Egnyte Connect\

Repercussions of Skipping the Antivirus Update or Using the Reboot Suppression Flag

Missing Antivirus Exclusions: Endpoint security software may block binaries at the new installation path, causing the Desktop App to fail on affected devices after upgrade.

Using Reboot Suppression Without ED_UPDATE_ON_BOOT=1: The upgrade will not complete successfully. The installer requires one of these two outcomes — either an immediate restart, or the ED_UPDATE_ON_BOOT=1 flag to stage the upgrade for the next reboot.  Omitting both will leave the installation in an incomplete state.

Open Beta Users (Upgrading from Previous 4.x Versions)

Users upgrading from 4.x beta versions released prior to 4.2.0 may notice that the CBFS driver remains installed under Program Files (x86) after the upgrade. This is expected — the CBFS driver version used in those beta builds remains compatible with the current release, so it is not automatically moved.

This does not affect Desktop App functionality, as long as antivirus exclusions cover both installation directories (see above).

The driver will be relocated to the new installation directory in a future update.

If a clean state with all the components under the new path is preferred, perform a clean installation:

1. Uninstall the existing Desktop App.
2. Restart the system.
3. Install version 4.2.0.