Mar 2026 - Private Cloud 3.6.31 - x360Sync Release Notes

Written By Nikki Klukowski (Administrator)

Updated at May 4th, 2026

Component 

Private Cloud

Version

3.6.31

Release Date

March 19, 2026

Contents 

Thick Client Windows: 3.6.30.546

Thin Client Windows: 3.6.41.523

Thick Client Mac: 3.7.0.690

Server: 3.6.50

Web: 3.0.4 

Outlook add-in: 3.6.1.193

 

 

 

 

 

 

 

 

 


How to Install

To update an existing x360Sync Private Cloud Server installation, simply launch the embedded Updater tool.

To download the new installer manually, please refer to this article: Download the latest Private Cloud Server - x360Sync.

 

Important Notes

  • Windows Server 2012 and Windows Server 2012 R2 are no longer supported starting with Private Cloud 3.6.30. This release includes and requires Python 3.12, which doesn’t support these outdated operating systems. Please update to a newer OS version to keep receiving the latest Private Cloud updates. If you'd like to migrate instead, please refer to Migrate the system to a new server - x360Sync.
  • Thick Client Mac: macOS 10.14 and macOS 10.15 are no longer supported starting with Thick Client Mac 3.7.0. Please make sure your users update to macOS 11 or newer (macOS 15 or newer is recommended) to continue receiving the latest application updates.
  • When updating from Private Cloud 3.6.10 or earlier, it is required to install Private Cloud 3.6.20 or 3.6.21 first to modify the necessary database fields. After this, Private Cloud 3.6.30 will become available. If you run the Updater tool in the installation folder, it will automatically display the latest available release.
  • Web Preview client for images and PDF files has been updated in Private Cloud 3.6.30. Our hosted backend services for Web Preview and Web Editor also require updating, and they are temporarily running in compatibility mode. Make sure to update your Private Cloud environment by June 30, 2026. Starting from early July 2026, partners running Private Cloud 3.6.21 or earlier may experience issues with Web Viewer PDF previews and Collaborative Web Editor saves.

 

New FeaturesEdit section

Thick Client Mac: Native ARM SupportEdit section

  • Added native support for Apple silicon chips, improving the performance and energy efficiency on the latest Apple hardware and removing the need to use Rosetta translation layer.

 

Enhancements

Private Cloud Edit section

  • Installer is now blocking installation attempts on no longer compatible Windows Server 2012 and Windows Server 2012 R2. This will prevent administrators from updating and accidentally rendering their environments unusable. Please update to a newer OS version to keep receiving the latest Private Cloud updates. If you'd like to migrate instead, please refer to Migrate the system to a new server - x360Sync.

Thick Client MacEdit section

  • Verified support for macOS 26 Tahoe.
  • Significantly improved the initial scan time when adding a new team share, backup or FSE mapping.
  • 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.
  • Introduced local rsub database integrity checks and auto-repair functionality. Local rsub corruption could cause various synchronization issues, and now the Client will rebuild the database when this problem is detected.
  • Updated libraries for better performance and reliability.

 

FixesEdit section

Thick Client MacEdit section

  • Fixed a bug where local root subscription database inconsistency could cause Client to make excessive RPC calls, resulting in increased load on the backend.
  • Fixed a bug where the wrong Client version was displayed in status report, service output logs and GUI logs. This will help support with troubleshooting.
  • Fixed a bug where file server enablement (FSE) could not work on macOS Sonoma or newer because of the duplicated path "/Volumes/Volumes" in mount points.
  • Fixed a rare bug where the application could crash at launch.
  • Fixed a bug where re-registering the Client and merging SyncedFolder with the folder with same name but different case would cause a delay of syncing files to the server.