SuperDuper! 4.0.3

4.0.3macOS
Added 1
  • VoiceOver groundwork including improved descriptions for drive lists, pickers, and job tiles
Changed 4
  • Turbo will happen more frequently and faster due to tweaked system inquiries and accounting
  • Running many replications at once no longer stalls the UI
  • Smart Delete improvements for quicker and more accurate space freeing
  • Extremely large folder handling is improved
Fixed 7
  • Copying from a non-startup bootable copy can now use Turbo
  • Spotlight restoration is more reliable post-replication by restoring both the overall state of indexing and individually ignored files and folders
  • Dragging a job to reorder it now works
  • Keyboard navigation with arrow keys, Space, Return, and Esc now works in pickers opened by clicking
  • A backup no longer fails mid-copy if another app unmounts the snapshot during backup, and now reports which app caused the failure
  • A bootable copy no longer fails at the final step when the system unmounts volumes during renaming
  • A backup no longer sits indefinitely waiting for a Turbo-related query response and falls back to regular Smart Update if macOS does not respond in reasonable time

From SuperDuper!

SuperDuper! 4.0.3 (August 17, 2026)

Welcome to the hat-trick release of v4.0—v4.0.3…the goal of which is to continue to address any roll-out problems as quickly as possible.

And so, to the fixes!

Fixes

Copying from an non-startup bootable copy can now Turbo, whereas before it could not.

Spotlight restoration is more reliable post-replication. This is mostly due to trying to restore both the overall state of indexing and individually ignored files and folders. It’s better.

Dragging a job to reorder it didn’t work. Regression—fixed.

Clicking to open a pop-up, and then using the keyboard, didn’t work. Click open the copy-method (or any other) picker and the arrow keys and Esc did nothing (they worked with you opened with the keyboard). Arrows, Space, Return and Esc now work no matter how you opened it.

Chapter 1,000,000 in the Swift UI Hates the Keyboard saga, with more to come. Might even be a trilogy!

A backup could fail mid-copy if another app yoinked our snapshot. If something (I’m looking at you, Time Machine) unmounted the copy’s internal snapshot while a backup was running (a snapshot Time Machine did not own, natch), which would show up later as an error. SuperDuper now notices the moment it happens, stops cleanly, and the failure report names what actually went wrong...and who did it.

And we know who did it.

A bootable copy could fail at the very last step. While I was renaming the volumes back to what they should be, the system would sometimes unmount them to do its own stuff. Rude!

A backup could start, and then just…sit there. I’ve only seen this with one user, who ran a huge from-scratch-not-a-replication copy, and then a follow-up Smart Update. Basically, this exposed a weird macOS bug: when I was waiting for an answer to a Turbo-related query, that answer never came.

Well, I don’t wait indefinitely any more. If macOS doesn’t answer in a reasonable amount of time, SuperDuper gives up and just does a regular Smart Update. Take that, permanent wait-state.

Improvements

Turbo will happen more, and faster. I’ve tweaked the way the system inquiries and accounting are done, for the better.

Running a lot of replications at once could stall the UI. Yeah, none of you did this, but I did.

Smart Delete improvements. Should work more quickly and accurately to free space, if available.

Extremely large folder handling is improved. Pathological case, meet Dr. Improvement.

Groundwork for VoiceOver. Drive lists, pickers, and job tiles now describe themselves properly instead of reading as scattered fragments, and decorative artwork keeps quiet. This is in-progress—there’s more to do before it’s something we’d call supported—but it should already be noticeably better, and we’d welcome reports from VoiceOver users.

Requirements

The same as before: macOS 14 or later, on Apple silicon or Intel.

View original

Upgraded? How did it go?

Discussion