Transfer Failed

[micheledavis]

Describe the bug
Transfer failed message on larger files

To Reproduce
Drop file into e content folder
File transfer starts
File transfer stalls
message appears

Expected behavior
The file transfers

Desktop (please complete the following information):

• OS: Windows 11 Pro

I have Cyberduck version 9.4.1
My coworker has version 8.6.3 and it is working for him. How do I go back to a previous version of Cyberduck?

[IMONsergey]

A rollback can be a useful A/B test, but first capture the actual transfer failure from 9.4.1. “Transfer failed” alone does not distinguish a Cyberduck regression from a server timeout, proxy, multipart-upload limit, or changed connection profile. Open the failed transfer, copy the transcript/log with credentials and signed URLs redacted, and record the protocol, server product, approximate failing size, and whether download or upload is affected.

For a temporary Windows rollback:

1. export or back up your Cyberduck bookmarks;
2. uninstall 9.4.1 without removing user settings;
3. download the required signed installer from Cyberduck's official changelog/download history, not a third-party archive;
4. install it and turn off automatic updates only for the duration of the test;
5. retry the same file with the same bookmark.

Do not copy your coworker's installed program directory; use the official installer so bundled components and registry entries match.

If 8.6.3 works and 9.4.1 fails, test one intermediate release if practical and report the narrowest known good/bad range together with the redacted transcript. Also compare the bookmark settings rather than only the app versions—especially transfer concurrency, connection timeout, segmented/multipart upload settings, proxy, and TLS/SSH configuration.

Because 8.6.3 is old, do not leave it as the permanent fix: older clients miss security and protocol fixes. Keep the rollback isolated to confirming the regression, then return to a supported release or use the latest build containing the fix.