b4: Fixed an issue introduced in b3 that led to an error "Reading the contents of this file", affecting only sparse files that contained no data.

b3: Fixed an issue that was causing some tasks to fail with a CloneKitService exception on macOS Tahoe.

b3: Fixed an issue where CCC was failing to create a new folder because the parent folder was locked on the destination.

b2: This build addresses an issue introduced in b1 in which CCC would fail to mount a not-encrypted source or destination, claiming that CCC lacked the password to mount the volume.

The "Find and replace corrupted files on the destination" setting is now officially named "Backup Health Check".

Removed the "Standard Copy" button; the name of this button was a misnomer. This button was only present when Quick Update was enabled on a task, and in those cases, running the task with the Quick Update setting is the "standard" way of running that task. The Standard Copy button was added as a way to suppress the Quick Update feature in an ad hoc manner. This button was not frequently used, and its presence with that particular name was leading to some unnecessary confusion and concern. In lieu of a separate button, you can now hold down the Option key while clicking the Start button if you would like to have CCC rescan the entire source and destination (i.e. suppress Quick Update). Additionally, you can hold down the Command key to perform an ad hoc Backup Health Check. The resulting behavior of the modifier key presses is reinforced by icons on the Start button that correspond to the Quick Update and Backup Health Check features, as well as customized tooltips that will appear when you hover your mouse over those buttons.

Resolved an issue where CCC would fail to import tasks or restore the CCC application support folder if CCC's helper tool was not yet registered with macOS. CCC will now prompt to register the helper tool prior to importing tasks.

Added a menu item to the Volumes sidebar contextual menu that offers to delete an APFS volume (e.g. if you accidentally added an extraneous volume via the Backup Volume Setup Assistant). Select the volume in the sidebar first, then right-click on the volume to get an option to delete it.

Fixed a crasher that could occur if many, many tasks were started simultaneously (e.g. in response to a volume mount event).

Fixed a logic issue that was causing some "Folder was deleted" audit transactions to get a "circle with plus" icon rather than the "circle with minus" icon. Addressed another issue that was leading to extraneous folder entries in an audit when those folders had not actually been modified.

Orphaned compression attributes are dropped when transferring a file or dataless folder that does not have the associated "this file is compressed" flag (this part is not new). Addressed a logic issue that was causing files (or more commonly, no-longer-dataless folders) with these vestigial attributes to appear in the task audit every time the task is run, despite that the files were not actually getting modified.

Addressed an issue in which CCC was prematurely aborting a task due to an apparent stall while collecting the attributes of files in a folder that had an exceptionally high file count (e.g. >100K).

Fixed an issue that affected how sparse files are copied between volumes that have different optimal buffer sizes.

Improved the experience of switching between Simple Mode and Standard Mode, especially when CCC's helper tool has not yet been registered with macOS.

CCC will avoid auditing a Quick Update task if the destination NAS filesystem URL has only a DNS-suffix difference (e.g. smb://user@host vs. smb://user@host._smb._tcp.local are now treated as the same).

CCC now verifies that the device ID of the "_CCC SafetyNet" folder matches the device ID of the destination volume. If that folder has been replaced with a symlink that points to some other volume (for example), CCC will abort the task. This change resolves the errors that would occur if the SafetyNet folder was on some other volume (e.g. because files cannot be moved across device boundaries, they would have to be copied, then deleted). CCC only moves content into the SafetyNet folder — copying and then deleting the content defeats the purpose of the SafetyNet feature.