Welcome to
Help Desk

Product Updates
Training
Support
Ideas Contact Support

Desktop App for Windows v 3.24.0 - Improved Co-editing Experience

External Release Notes: Desktop App for Windows v 3.24.0 (March 28, 2025)

New Features And Improvements

Improved Co-Editing Experience For Files With Upload In Progress

Enhanced the co-editing experience for cases where a file hasn’t finished uploading to the cloud. Previously, users would see a generic error message asking them to try again later. Now, when opening such a file for co-editing, users will see a new pop-up with a progress bar showing the file upload status.

DA 3.24 RN 1.png

This improvement doesn’t apply to folders synced for offline access.

Context Menu Option Renamed To ‘View Online’

Renamed the context menu option View in Cloud to View Online for better clarity and consistency with user expectations.

DA 3.24 RN 2.png

 

Issues Addressed

Desktop Configuration Profile - Custom Access URL Deployment Issue

Applying a Desktop Configuration Profile containing a Custom Access URL caused the deployment to fail. The configuration is now properly respected during mass deployment.

Lock State Alternating After File Save in BricsCAD

Saving .dwg files in BricsCAD caused file locks to alternate on each save. The locking mechanism now correctly maintains the intended lock state during and after the save process.

Log Collection Crashes

Log collection tool consumed excessive memory, sometimes causing the app to crash. This also prevented log files from being zipped and sent to support. The process is now more stable and reliable.

File With Unsupported Characters Stuck in Upload Loop

Files with unsupported characters like a tilde ~ at the end of the name were getting stuck in an endless upload loop. These files will now be properly skipped.

 

Known Issues Or Limitations

Co-Editing Not Triggered When Using ‘Save As’ In Office

When using Save As in Office to save a file to Egnyte Drive via Browse or This PC, the file will be saved, but co-editing will not initiate. This occurs due to a limitation in Microsoft Office’s integration behavior.

Please refer to this article for more details on this and other known limitations.

 

Was this article helpful?
0 out of 0 found this helpful

For technical assistance, please contact us.