External Release Notes: Desktop App for Windows v 3.28.1 (September 19, 2025)
New Features and Enhancements
Added Option to Disable Hardware Accelerated Rendering
In some virtual machine environments, the Desktop App UI could fail to render correctly due to conflicts with certain Intel Iris graphics drivers.
A new command-line parameter has been added:
--rendering=software
launches the app with hardware acceleration disabled.
--rendering=hardware
This setting is retained until explicitly changed.
Issues Addressed
Improved Handling of Read-Only Folder Attributes
Desktop App no longer marks folders with a read-only attribute. According to Windows documentation, this attribute is not used by File Explorer for access control and has no effect on file or folder permissions.
This change simplifies the Desktop App’s implementation and prevents unnecessary delays when opening folders in Windows Explorer, without altering user access or security settings in any way.
Fixed Drive Conflict Handling in Desktop Configuration Deployment
Previously, Desktop Configurations could fail if a configured drive conflicted with the default drive created at startup. After the fix, the configuration data is retained, so deployment continues even if a conflicting drive is removed.
Removed Incorrect Storage Location Not Added Pop-Up
The Desktop App previously showed a pop-up when starting a Microsoft co-edit session if the storage location was not detected. This message could appear even when the storage was already added. The pop-up has been removed and if storage is missing, Office now directs users to the storage configuration window automatically.
Preventing Files from Opening in Co-Edit Mode
In some cases, files could not be opened in Co-edit mode and appeared as locked by another user. This was caused by integration settings that were not re-enabled after a network disruption. This update ensures the settings are restored correctly so the issue no longer occurs, including for users who may have been affected in earlier versions.
Skipped Files Kept Reappearing
Previously, a skipped file could get stuck in a state where it repeatedly reappeared, even after being deleted from both the local drive and the cloud. This issue has been resolved. Skipped files affected by metadata issues can now be manually moved to the desktop from the Skips tab in the Desktop App, allowing them to be cleared permanently.
Allow Users to Manage Drives Setting
Resolved a problem where the Allow users to manage drives option in Desktop Configurations was not always applied correctly.
Egnyte Actions Menu for Configuration Defined Drives
For drives defined in Desktop Configurations, the Egnyte Actions menu was sometimes not available immediately after the configuration was applied, and a restart was required to make it visible. This has been fixed, and the menu is now available right away without restarting.
Known Issues or Limitations
No new limitations have been discovered.
Please refer to this article for the list of known limitations.