Important Notes

• Going forward, when updating from an older version to any future Private Cloud release, installing Private Cloud 3.6.20 will be a mandatory intermediate step to apply necessary changes to the database structure. For example: 3.5.0 -> always 3.6.20 -> 3.6.30 will be the proper update path, while 3.5.0 -> 3.6.30 won't be possible. The updater and installer will show the appropriate versions and messages when relevant.
• In one of future Private Cloud releases, backend will stop supporting Client versions 3.5.2 and earlier. Please ensure that all your users have updated to Client 3.6.0 or newer to avoid any compatibility issues. For the best experience, we recommend always using the latest Client version on all devices.

Enhancements

Private Cloud

• New Private Cloud installations will now include PostgreSQL 12 instead of PostgreSQL 9. New installations will also have PostgreSQL as default database type for new roots instead of SQLite. To make such changes on an existing Private Cloud environment, please refer to these KB articles: Upgrading PostgreSQL on Private Cloud from 9.x to 12.x and How to convert root database from SQLite to PostgreSQL [Manual for Private Cloud administrators]
• Added support for Windows Server 2025

All Clients and Server

• Updated libraries and drivers for better performance and reliability
• Stability improvements for Clients with a high number of root subscriptions
• Improved overall sync-up reliability

Server

• Added backend support necessary for upcoming cross-platform features and improvements
• Introduced database structure changes for future performance improvements
• Introduced Server-side improvements for Client to be able to graciously handle files and folders in the same location and with the same name but in different encodings
• Improved WebDAV authentication methods. Newer versions of Windows and Office will no longer have trouble working with files in mounted x360Sync WebDAV locations
• Improved the restore process: if the database is temporarily locked by other queries and Server encounters "database busy" error, it will retry several more times. This should reduce the likelihood of restore operations failing
• Increased default timeouts for database locks for all file and folder operations (including deletions and restores) to improve their reliability
• Introduced improvements to batch conversion procedure for roots
• Improved WebDAV logging for better troubleshooting
• Introduced additional logging for file and folder restore operations for better troubleshooting

Thick Clients (Windows and Mac)

• Team shares are now sorted alphabetically in selective sync GUI
• When selective sync is enabled, the folder created elsewhere or restored on Web will no longer sync down to Client unless this folder or its parent folder is explicitly selected in GUI
• Added details to error logs for better troubleshooting
• Added warning details to sync status report for better troubleshooting

Thick Client Mac

• Added support for macOS 15 Sequoia
• Reduced CPU usage by optimizing the performance of agent_service and agent_gui processes
• Introduced rollback functionality: if an update fails, the installer will automatically revert to the previous version

Thin Client

• Added support for Windows Server 2022 and Windows Server 2025
• If user tries to unregister Client while it is still syncing, they will now be explicitly informed about the risks of data loss
• If user tries to uninstall Client while it is still syncing, they will now be explicitly informed about the risks of data loss and advised to make a copy of their data first
• Added context menu options to lock and unlock items within file server enablement (FSE) mappings
• Increased the default value of connection_acquire_timeout from 60 seconds (1 minute) to 300 seconds (5 minutes), enhancing Client reliability when handling especially large roots
• In rare cases where a user attempts to delete a file from the Client that is missing on the Server (potentially due to an old synchronization issue), the file will now be backed up to the Desktop, and a notification will be shown to the user
• When Client is unable to sync changes to the Server after several attempts, it will now display a warning in UI for all affected folders and files. No user action is needed. The next sync-up attempt will occur automatically during the next scan (usually every hour) or after pause/unpause. If this warning persists, please contact support
• Added translations of warning messages into Brazilian Portuguese, Dutch, French, and German for scenarios when a user attempts to unregister or uninstall the Client while changes are still being synced

Web

• Security improvements
• Improvements to the restore status UI: If restore is taking some time, a hint will appear suggesting the user to look at Activity Log (with a relevant link) to see files being restored in real-time
• Added debug information for cases of restore errors: Instead of "Unknown error", Web will display a more detailed message. The user will be able to expand error details and share them with support for troubleshooting
• Maintenance update for Web Preview functionality
• Minor under-the-hood improvements

Fixes

All Clients and Server

• Fixed an issue where restricting access of an account to a team share (reducing permissions to a level not supported by Client) would make Client send excessive requests to the backend
• Made the file synchronization logic more reliable

Server

• Fixed issues that could cause snapshot creation to fail
• Fixed an issue where snapshot creation could generate irrelevant stale events in the database, causing potential sync issues for Clients
• Fixed an issue where snapshot creation could restore the files deleted in the original root
• Fixed a bug in snapshotting mechanism where deleted files were marked as deleted at snapshot creation time rather than at their actual deletion time
• Fixed a bug where extensive wipe jobs could cause short-term service outage
• Fixed a bug where root conversion in system console could incorrectly report the conversion job status and result
• Fixed a bug where admin dashboard could display negative values for organization stats such as space used, number of files, revisions, etc. This change might take up to three months to appear due to the timing of monthly usage data collection

All Clients

• Fixed an issue where Client could get stuck until service restart if it encountered "Database busy" or "Server busy" error
• Fixed an issue where special characters in file names could cause recurring file events, such as creation/deletion
• Fixed an issue where files inside a folder with a name using format "(collision xxx)" would duplicate on Server upon rename
• Fixed an issue where icon overlay remained next to the folder that was mapped for file server enablement (FSE) but then became a regular local folder
• Fixed inconsistencies in the "Delete all duplicates" functionality introduced earlier

Thick Clients (Windows and Mac)

• Fixed an issue with selective sync where a deselected subfolder moved into a selected parent folder from Web would not sync to Client properly
• Fixed an issue where Client would crash when trying to move a folder no longer available on the Server
• Fixed an issue where connection sometimes could not restore after computer wakes up from sleep
• Fixed an issue where files made read only locally could not be renamed, modified or removed by Client when respective changes were done elsewhere
• Fixed an issue where lock icons and context menus were not showing in FSE mapped folders
• Fixed an issue where a team share icon remained next to the folder that became a regular personal folder after unsubscribing from a team share and keeping files
• Fixed an issue where an empty folder would not sync down when chosen in selective sync GUI

Thick Client Mac

• Fixed an issue where macOS update could result in Client being reported as damaged and unable to open
• Fixed an issue when sync could get stuck on newly registered devices because of colliding file names with unsupported characters or because of a very large number of events in the root to process
• Increased the default timeout for locking a root database to 60 seconds. Now, Client should not have problems locking a large database, where previously this process could fail with "lock timeout" error in the log
• Fixed an issue where some file formats (such as .xlsx) took up to one hour to be synced up after being edited
• Fixed a rare issue where Client would lose and restore connection every few minutes after plugging in an iOS device
• Fixed an issue where "Lock Info" option in Finder context menu would throw an error and not display the proper lock status
• Fixed an issue where .docx files would not auto-lock when opened in Word
• Fixed an issue where Client would not start automatically on login after updating to a version with a differently branded name

Thin Client

• Fixed an issue where Client could stop syncing properly and throw errors "Bad event log" or "Revision is not current"
• Fixed an issue where Client would display a wrong number of files as being synced after adding a large file into a root (share)
• Fixed an issue where Client would continue displaying sync in progress after all files have been successfully synced up
• Fixed a bug where, in some cases, Thin Client could accidentally remove PDF files after they were edited using Adobe Acrobat
• Fixed an issue where Client would not properly apply locks within file server enablement (FSE) mappings done from elsewhere
• Fixed a bug where the Client couldn't sync up a file if its name contained translations of special characters, such as: "file_with_asterisk~12.txt"
• Fixed a rare bug where Client could stop syncing properly after an attempt to delete a file that is missing on the Server (potentially due to an old synchronization issue)
• Fixed a rare bug where Client could crash when the overlay attempted to request file status from a root that had just been removed

Web

• Fixed an issue where completed restore tasks could disappear from the list when refreshing the page or going to another page

SUPPORT | 720-204-4500 | 800-352-0248

• Contact Axcient Support at https://partner.axcient.com/login or call 800-352-0248
• Have you tried our Support chat for quick questions?
• Free certification courses are available in the Axcient x360Portal under Training
• Sign up for free, live,  one-on-one training to learn about Axcient products
• Subscribe to Axcient Status page for updates and scheduled maintenance