External Release Notes: Egnyte Desktop App for Windows v 4.7.1 (October 6, 2026)
New Features and Improvements
Remote Wipe Reliability and Reporting Improvements
Remote wipe now reliably removes access to Egnyte content on the target device. This release addresses a small number of rare edge cases in post-wipe behavior:
- An infrequent path where the drive was left in a disconnected state rather than removed
- Local configuration entries occasionally left behind
- Completion status not consistently reported for both Classic and ABC drives
All three are now handled as part of the same operation; finished actions are cleared from the device, and restart behavior immediately after a wipe is more robust.
Device Entitlement - Wildcard UPN Suffixes are no Longer Accepted
Wildcard entries in the device entitlement UPN suffix list are no longer supported. A wildcard can match subdomains outside the organization's control, which could allow access from unintended devices. Previously, the Desktop App displayed an error for a device matched only through a wildcard but still mounted the drive. From this release, the drive is not added.
The suffix list limit has also been raised - up to 50 suffixes can now be entered explicitly, so the full list can be in place before upgrading.
Clearer Component Naming for MDM-Managed Deployments
The MSIX shell extension package, used to integrate with Windows Context menu, now registers as Egnyte Desktop App Modern Shell rather than sharing the main application's display name, so MDM tooling (SCCM, Intune etc.) no longer shows two identically named entries to target and report on.
Updated Embedded Browser Component
The embedded browser component used for sign-in and in-app web content now ships with the latest upstream security fixes. No behavior changes, no action required.
Issues Addressed
Drive Status as "Connected" Instead of "Hybrid Connected" at Startup
Drive configured to use a Smart Cache appliance could display as "Connected" (to the cloud) rather than "Hybrid Connected" after the Desktop App started. Users had to open the drive's menu and run Advanced → Refresh All manually before the drive switched to Hybrid Connected.
The Desktop App now re-evaluates Smart Cache appliance availability when a drive connects, so drives that should be Hybrid Connected reach that state on their own without manual intervention.
InDesign Edits on Adaptive Block Caching Drives not Reaching the Cloud After First Save
A newly created Adobe InDesign file (.indd) on an ABC-mounted drive uploaded correctly on its first save, but all subsequent saves were silently dropped. The local file appeared correct with no error shown, yet in some cases only the initial near-empty version reached the cloud.
Edits to .indd files are now uploaded on each save, keeping the cloud version in sync with the file on disk. Other applications that use the same save pattern are covered by this fix.
Drive Disconnect During Host Switch in VDI Environment
In VDI environments, some drives could occasionally disconnect and prompt for sign-in again after a user switched hosts. Drives now stay connected through a host switch.
Known Issues and Limitations
No new limitations have been discovered.
Please refer to this article for the list of known limitations.
Additional Information and Resources
How to Upgrade
Visit the Desktop App installers article to download and install the latest version of the Desktop App or update the existing app to the newest version on all the devices. It may take a few days for the latest version to propagate to all user devices. However, users can manually upgrade their app immediately after the release.