Cyberduck Mountain Duck CLI

#5306 closed defect (fixed)

Transfers only work to/from C: Drive

Reported by: Owned by:
Priority: highest Milestone: 4.0b4
Component: core Version: 4.0b3
Severity: critical Keywords:
Cc: Architecture:
Platform: Windows XP


Cyberduck seems to be rewriting local paths to always be rooted from the C: drive, even if the real source is another drive or UNC path. Local and Network paths are affected. This definitely affects FTP and SFTP, I'm guessing it affects all protocols.


  • ALL uploads, initiated via Keyboard (Alt+Up), Context Menu, File Menu, or Drag & Drop fail on all non-C: drive local paths. All paths have their local drive (D:, E:) or UNC server (
    Server) rewritten to C:. Of course, since the file isn't actually there, the transfer fails.
  • Drag & Drop Downloads to paths not on C: drive have also have their leading identifier (e.g. D: or
    Server) rewritten to C:. Transfers succeed, but the local path is rerooted to the C: drive. If a file was to be downloaded to D:\Path\To\, then the file is downloaded to C:\Path\To\ The \Path\To directories are created on C: if they do not exist. This happens for all non-C: local drives, mapped network drives, and UNC paths.
  • The "Download To..." command works correctly.
  • If the default download folder specified in Preferences -> Transfers -> General -> Downloads -> Download Folder is not on the C: drive, then the "Download" command fails in a similar manner as Uploads and D&D Downloads.

Change History (3)

comment:1 Changed on Oct 12, 2010 at 4:03:03 PM by

  • Summary changed from Uploads and Drag & Drop only work to/from C: Drive to Transfers only work to/from C: Drive

comment:2 Changed on Oct 12, 2010 at 8:18:56 PM by dkocher

  • Milestone set to 4.0b4

comment:3 Changed on Oct 13, 2010 at 11:34:29 AM by yla

  • Resolution set to fixed
  • Status changed from new to closed

In r7305. Thanks for reporting this issue!

Note: See TracTickets for help on using tickets.