Skip to main content

RcloneView 1.6 – Release Notes

Release Date: October 2026
Platforms: Windows, macOS, Linux

RcloneView 1.6 is a correctness release. Two ways of losing files and one open network port were closed, the flags you type into a job are now actually sent to rclone, a failed sync can no longer report itself as finished, and RcloneView no longer shuts down rclone processes that do not belong to it. Later 1.6 updates also stop a remote with a wrong password from signing in again and again until the server blocks this computer, and stop scheduled jobs from running once for every open window. Alongside those, this release fixes a long list of problems across mounts, the explorer, remote creation, the Wizard, and packaging on all three platforms.

Please Read Before Upgrading​

  • Filter flags in a job's Custom flags now take effect. Filter flags such as --include, --exclude, and --filter typed into a job's Custom flags box were being dropped before the job ran — they only applied during a dry run and during bisync diagnostics, so the preview and the real run could disagree. They are now passed through on every path.
    This changes what existing jobs do. If you have a job with filters in Custom flags, it now transfers only the matching files instead of everything. For a sync job with deletion enabled this also changes what gets deleted at the destination. Please review any job that keeps filters in Custom flags, and run it once with Dry run before letting it run on a schedule.

  • A remote whose password is a long token needs that password entered once more. When saving a remote, RcloneView left rclone to work out for itself whether the password it had been handed still needed encoding. For a password that looks like base64 that guess is always wrong, so the value was written to the configuration unencoded and then scrambled on every connection attempt. A remote saved that way has never been able to authenticate. RcloneView now encodes passwords itself, so anything you add or edit from this version on is stored correctly.
    Remotes already saved that way are not repaired by the update. This only affects a password of 22 characters or more made up purely of letters, digits, - and _ — in practice an API token or a generated app password, not one you chose yourself. If you have a remote that has been failing to connect with an authentication error, open it in Remote Manager → Edit, enter the password again, and save. It will connect from then on.
    Do not re-enter the password of a Crypt remote that opens correctly today. A Crypt remote saved this way never failed: its files were encrypted with the scrambled value, and only that value reads them back. Entering the real password now would switch the remote to a different key, and the files already in it would no longer open. Leave such a remote as it is — editing its other settings is safe. If you have already re-entered the password and the files stopped opening, put the old value back in rclone.conf: it was the password itself, written without encoding. To move such a remote onto its real password, copy the files out through the existing remote first, then create the remote again.

  • With App Lock on, nothing starts until the app is unlocked. The lock screen now comes up before any window content, and rclone, scheduled jobs, auto mounts, and the web server wait for the password instead of starting behind the lock screen. If RcloneView starts at login with App Lock enabled, scheduled jobs and auto mounts do not run until someone unlocks it. If this computer relies on jobs or mounts running unattended after a restart, turn App Lock off or unlock the app after each login.

  • A remote whose sign-in is rejected is no longer contacted automatically. For remotes that sign in with a password — SFTP, FTP, WebDAV, and SMB — RcloneView now checks the sign-in once, and if the server rejects it, stops connecting to that remote: no auto mount, no scheduled job, no reopening its tabs. This is remembered across restarts. A scheduled job that uses such a remote is recorded as failed and sends the usual failure notification. Connecting resumes once you press Retry in the explorer or save the corrected password in Edit Remote.
    If a server rejects sign-in only for a while — for example while its password is being changed — scheduled jobs on that remote stay paused afterwards until someone presses Retry. Cloud storage that you sign in to through a browser or with a key is not affected.

  • Scheduled jobs now run from the main window only. Schedules follow the main window's rclone connection. If you switched only a secondary window to a different connection, the scheduled jobs of that connection no longer run while that window is open; select the connection in the main window instead. If the main window closes unexpectedly, scheduled jobs stop until RcloneView is started again, even if other windows are still open.

Data Loss and Security​

  • Retry After a Partly Failed Delete Could Purge the Parent Folder: Deleting several files at once, having some of them fail, and then pressing Retry could remove the entire parent folder instead of retrying the files that failed. Retry now acts only on the items that failed.

  • File Names With [ ] * ? { Could Delete the Wrong Files: Deleting multiple files handed their paths to rclone's filter engine without escaping them, so a name containing a pattern character was treated as a wildcard. A single delete could match — and remove — files in other folders. Paths are now escaped before they are used as filters.

  • Creating a Remote Under an Existing Name Replaced That Remote: rclone treats "create" as "create or update", so creating a remote with a name that was already in use — even with a different storage type — silently overwrote the existing remote's settings and credentials. The New Remote dialog, the Wizard, and the Wizard's Crypt step now warn as soon as you type a name that is taken and do not continue.

  • Window-to-Window Port Was Open to the Network: The port RcloneView uses to talk between its own windows (13542) was listening on every network interface rather than only on this machine, and the main window accepted an empty authentication key. It now binds to the local machine only and requires a real key.

Highlights​

  • RcloneView No Longer Stops Your Other Rclone Processes: Quitting the app, restarting rclone, or running Update Rclone terminated rclone by name, which also killed every other rclone on the machine — a rclone mount you started in a terminal, a cron job, or another tool using rclone. RcloneView now only stops the process it started itself.

  • A Wrong Password No Longer Gets This Computer Blocked: One SFTP remote with a wrong password could sign in dozens of times until the NAS blocked this computer's IP address. rclone retries a rejected sign-in up to ten times per request, opening a single tab sent several requests at once, and the app retried a failed listing three more times — around 80 sign-ins for one tab. The app also connected on its own at startup, when restoring tabs, for auto mounts, and for scheduled jobs. For remotes that sign in with a password (SFTP, FTP, WebDAV, SMB), RcloneView now checks the sign-in once and stops if it is rejected. The explorer shows Sign-in failed with Edit Remote and Retry buttons — for a Crypt or alias remote it points to the remote underneath — and the Remote Manager shows a Sign-in failed badge instead of free space. A remote added with a wrong password in New Remote is not saved. When a server stops answering after repeated failures, the explorer now says within seconds that the IP may have been blocked, instead of spinning for about 50 seconds.

  • Scheduled Jobs Ran Once for Every Open Window: Each RcloneView window ran its own scheduler, so with a second window open every scheduled job and batch started once per window at the same moment. Two copies writing to the same local folder deleted each other's partial files, and the run could end with nothing copied. Changing or deleting a schedule in a secondary window also left the main window firing the old schedule. Schedules now run only from the main window, and changes made in other windows are passed to it. Pressing Run at the moment a schedule fired, or pressing it twice in quick succession, could likewise start the same job twice; it now starts once.

  • The Rclone From Before an Upgrade Kept Running: An rclone left running by the previous version was reused after upgrading RcloneView, so the newly bundled rclone was not used until that process was stopped by hand. RcloneView now restarts rclone when the running version differs. It also no longer mistakes another program that happens to use rclone's port for rclone — which left the app showing only No connection — and starts rclone on the next free port instead. On quitting or restarting rclone, the app now waits for rclone to shut down by itself; it used to force-kill it every time, before mounts were unmounted and the VFS cache was cleaned up.

  • Custom Flags and Global Flags Are Actually Applied: The flags you configure were being silently discarded in several different ways, which is why a flag that worked on the command line appeared to do nothing in the app. Fixed in this release: global rclone flags from Settings were not applied to Sync/Copy jobs; backend and process-wide flags put into a job's Custom flags were ignored; batch step fields (Bandwidth limit, Include, Min/Max age, Min/Max size) were sent in a form rclone discards; a boolean flag written with a number (--checksum=1, valid on the command line) made the whole request fail so the job never started; repeated --backup-dir and --compare-dest flags were rejected; --header, --header-upload, --header-download and --compare-dest were converted to the wrong type; the flag parser could not handle quotes or spaces inside a value; a dry run did not include Custom flags at all, so the preview did not match the real run; and one bad character in the global flags box silently dropped every flag instead of just the offending one.

  • A Failed Sync No Longer Reports "No Changes": A sync that failed before transferring anything — wrong credentials, an unreachable remote, a missing path — was shown as a completed run with no changes, in the job list, the history, and notifications. The errors rclone reports for the job are now read, so a failure is shown as a failure.

  • A Failed Listing Is No Longer Treated as an Empty Folder: When a folder could not be listed, several parts of the app assumed it was simply empty. That is how a mount could be placed on top of existing content, how mount Verify always passed, and how the folder tree, Compare, and the path picker could show nothing at all for a folder full of files. A listing that fails is now reported as a failure — the list view shows it too, instead of looking like an empty folder.

  • Abandoned Sign-Ins Blocked All New Remotes: Closing a provider's sign-in page without finishing left rclone's authorization helper holding port 53682, and every later attempt to create a remote that signs in through a browser failed. Restarting the app did not release it — force-quitting rclone was the only way out. The helper is now shut down when a sign-in is abandoned.

New Features and Improvements​

  • Per-Job Upload Concurrency: Backend upload concurrency (upload_concurrency) can now be set on an individual job instead of only globally, so a job against a fast remote does not have to share one setting with everything else.

  • New Remotes Open Straight Into a Pane: After you create a remote, it now opens in an explorer pane right away instead of leaving you to find it and open it yourself.

  • Free Space Shown in the Explorer: For remotes that can report it, the remaining space on the remote is now shown in the file explorer.

  • Faster Copying From the Compare View: Copying from the Compare view started one rclone job per item and ran four at a time no matter what --transfers was set to. Items are now grouped into one sync/copy per remote and parent folder, and your --transfers setting is honored.

  • The "Configuration File Changed" Popup No Longer Interrupts: The notice that the rclone configuration file changed on disk no longer takes over the screen in the middle of what you are doing.

  • License Registration Behind Strict Proxies: Some university and corporate proxies block the request method used to register a license. Registration and unregistration now fall back to a second method when the first is refused.

  • Global Flag Fallback Is Narrower: When a global flag could not be applied, the app used to drop the whole set — taking working flags such as --bwlimit with it. Only the flag that caused the problem is dropped now.

  • Google Photos Guidance: Google Photos only lists photos that were uploaded by this app, which is a restriction imposed by Google — this is now explained in the app instead of looking like an empty account. When a connection cannot be made, the app also walks you through creating your own OAuth client ID.

  • Clearer Custom Flag Warnings: The warning text shown for timeout, contimeout, and user-agent in Custom flags has been corrected.

  • Choosing a Mount Point: The Wizard now checks a mount point as soon as you type or browse to it, shows the reason when it cannot be used, and keeps Next disabled — instead of failing at the last step and leaving a failed entry behind in Mount Manager. It only suggests locations that can actually be created, starting with ~/Mounts/<remote>; when connected to rclone on another machine, it suggests a folder under that machine's home. Browse adds a folder named after the remote inside the folder you pick, and Use a new folder inside it fixes a folder that cannot be used as is — on Windows the mount folder must not exist yet, on macOS and Linux it must be empty. Mount Manager checks the same rules before saving, including on Windows a parent folder your account cannot create folders in, and shows why a mount failed instead of only Failed to mount.

  • Interactive Demos From the Wizard: Each task on the Wizard's Welcome screen has a Demo link that opens an interactive walkthrough of that task in your browser, and All demos lists every one of them.

  • iCloud Photos: The total number of photos is now shown during the first sync, so a long first run no longer looks stalled, and double-clicking a thumbnail can open it in the preview.

Bug Fixes​

Jobs, Batches, and Transfers​

  • Renaming a Folder on S3 Left the Old Folder Behind: Rename and Move steps in a batch moved the contents but left the original folder marker in place, so the old folder kept showing up in the explorer. On object storage a folder is a marker object, and the batch step never created one at the destination or removed the one at the source. Rename in the Job Manager had the same gap and additionally ran the cleanup of the old folder at the same time as the move, so the two raced; an empty folder ended up with no new folder created at all. Both now create the destination marker and remove the source marker, in order.

  • Retrying a Rename on S3 and Swift: Retrying a folder rename left an empty marker for the original folder.

  • Retry Could Run a Different Job: After rclone was restarted, a restored row and a current job could share the same job id, so pressing Retry re-ran the wrong job.

  • Retry Always Failed on Multi-Item Batch Transfers: The retry button on a batch transfer covering several items never succeeded.

  • Multi-Thread Streams Ignored on S3: The Multi thread streams value had no effect on S3 destinations, where the backend's own upload concurrency won instead.

  • Duplicate Job Names From the Wizard: The Wizard built a job's name from the path alone, so two jobs could end up with the same name — and that in turn blocked saving when you edited either of them.

  • Dry Run Previewed With Different Options Than the Run: A dry run of a job, a batch, or the Wizard ignored Global Rclone Flags and always checked with --transfers=4 --checkers=8, so a lower checker count set to spare a busy server did not apply to the preview. A batch copy step's preview left out the step's options, Custom flags other than filters (such as --fast-list and --compare-dest) were missing from every preview, and --checksum was passed differently from the real run.

  • Crypt Uploads Stayed "Running" Above 100%: rclone counts a Crypt upload in encrypted bytes, which are slightly more than the file's size. File rows of a finished Crypt upload stayed at Running in the transfer list and in history, and showed figures such as 183% while running.

  • A Sync Notification Opened Another Run's Details: rclone numbers its jobs from 1 again every time it starts, so clicking a completion notification could show the source, destination, and errors of a different run that reused the same number.

  • Deleted Scheduled Batches Kept Running: A scheduled batch deleted in Job Manager kept running on schedule until the app was restarted. Also fixed: one job with damaged settings stopped Connection Manager from switching connections; schedule changes made while schedules were being reloaded were dropped; and pressing Delete twice quickly could close Job Manager.

Mounts​

  • Mounting From a Remote Rclone Connection: When connected to rclone on another machine, the app still checked for and created the mount point on the local machine, so mounting from a Mac or Linux PC always failed.

  • Slow Drives Reported as "Parent Folder Does Not Exist" (Windows): Creating the parent folder was tied to the same timeout used to probe the drive, so a slow drive was misdiagnosed as missing.

  • Saved Mounts Disappeared When the Rclone Port Changed: Mounts you had saved vanished from the list after the embedded rclone started on a different port.

  • "Too Many Open Files" After a While: Responses from rclone were not fully read on some paths, which leaked a file descriptor every time until mounting stopped working altogether.

  • SFTP Mounted the Home Directory Instead of the Server Root: Path normalization stripped the leading slash from the mount target, so a mount of the server root landed on the account's home directory.

  • Local Drive Names in the Mount List: Fixed how local drive names are displayed.

  • Mounted Remotes Listed as "Configured": On Windows, and when connected to rclone on another machine, a mounted alias remote, a named local remote, or an alias pointing to a drive letter was listed as configured with a Mount button, so it could not be unmounted from its row.

  • Successful Unmounts Recorded as Errors: Unmounting twice, unmounting something already unmounted elsewhere, or an unmount that took more than 30 seconds — a macOS NFS mount waits for Finder to let go of the volume — left the row stuck at error. RcloneView now checks whether the mount is actually gone.

  • Mount Manager Dropped the Drive Letter (Windows): In Mount to local path mode, a folder chosen with Browse was saved without its drive letter, so Save and mount failed and the failed entry stayed in the list.

  • An Error Box Before the Folder Picker (Windows): Pressing Browse Local Folder while the mount point was still Auto: showed "You can't open this location using this program" before the folder picker.

  • Drive Letter Mounts Missing From the Local Disk Tab (Windows): A drive letter mounted through the Wizard appeared in File Explorer but not in RcloneView's local disk tab, because the tab was refreshed before the drive letter showed up. The tab now waits for it.

Explorer, Compare, and Filters​

  • Backslashes in Object Names (Windows): A cloud object whose name contains a backslash was split as if it were a folder separator on Windows hosts.

  • Backslashes in File Names (macOS and Linux): Path normalization made files with a backslash in the name fall out of step with exclusion rules.

  • Escaped Pattern Characters in Filters: The app's own filter preview could not match escaped pattern characters, so what you saw on screen and what rclone actually did were different.

  • Hidden Dropbox Files Were Still Copied: The exclusion for Dropbox's hidden files did not apply when copying a directory.

  • Local Drives Missing From the Browser (Windows): Local drives did not appear in the browser.

  • Errors After Using Compare: Fixed the frequent errors when running an operation after a comparison.

  • Open Always Used the Left Pane: Open in the Remote Manager put the remote in the left pane regardless of which pane you were working in, replacing the view you were comparing against. It now opens in the active pane.

  • Explorer Tabs Closed When Rclone Restarted: When the embedded rclone came back on a different port — after Restart rclone or connecting from Connection Manager — or Update Rclone changed its version, every remote tab in both panes was closed, and the tabs did not come back after restarting the app.

Startup, App Lock, Quitting, and Licensing​

  • The Dock Icon Bypassed the App Lock (macOS): Clicking the Dock icon while the app was locked opened the window without asking for the password.

  • The Tray Menu Bypassed the App Lock: While the app was locked and hidden in the tray, the tray's Mount items — mounting or unmounting a saved mount, and Unmount all — ran without the password, and a mount set to open in the file manager opened its folder as well. When the window was minimized rather than hidden, Open → remote added the tab before asking for the password. All of these now ask first.

  • Two Password Prompts From the Tray (Windows): Choosing a tray submenu item such as Open → remote or Mount → New mount with the locked window minimized opened two password prompts; after unlocking, the second one stayed on top of the app, and pressing Exit there quit RcloneView.

  • Keyring Password Prompt at Startup (Linux): Where the login keyring stays locked — automatic login, remote desktop, fingerprint login — RcloneView asked for a password at every start, before its window appeared. It was the GNOME keyring asking to be unlocked, not a request for administrator rights, and cancelling it froze the app. RcloneView no longer touches the keyring on Linux.

  • The Wizard Opened On Top of the Lock Screen: The Wizard could appear over the Enter App Lock Password screen.

  • Reset App From a Secondary Window: Running Reset App from a secondary window's lock screen left the main window running on settings and a database that had already been erased.

  • "Stop rclone on App Exit" Was Ignored: Quitting with ⌘Q or by closing the window on macOS, and Exit or Reset App from the lock screen, ignored the Stop rclone on App Exit setting.

  • Restarting Rclone Could Hang Forever: Restarting rclone after a configuration change could sit on an endless spinner, because the request to stop the old process had no time limit.

  • Trial Expiry Was Only Checked at Startup: Whether the trial had expired was decided once when the process started and never re-evaluated.

  • Auto Mount After Upgrading to a Paid License: Auto mount did not run after switching to a paid license, because the check ran before license verification finished.

  • License Registration Error Messages: When registration fails, the cause is now shown in your language. A server that does not answer is reported as unreachable, with a reminder to check the internet connection, firewall, and proxy, instead of as an unexpected error. Proxy advice no longer appears for failures such as an invalid key, and the copied diagnostic names the request method that was actually blocked.

Creating Remotes and Signing In​

  • Missing Provider Options: Options belonging to a specific provider were filtered by the wrong name, so Storj access credentials, the Koofr endpoint, and several Oracle fields never appeared.

  • Required Options Hidden Under Advanced: Compress could not be saved because its required level option was hidden under advanced options, and Oracle Object Storage was blocked the same way by compartment.

  • Oracle Authentication Methods: Choosing no_auth or user_principal_auth from the list configured the provider incorrectly.

  • Saving an Edited Remote Could Hang: Saving a change to an existing remote could stop responding inside rclone.

  • OneDrive Personal: Setting up a personal remote could stall at Verify Connection with the underlying error hidden, and a failed drive lookup could save an empty remote.

  • iCloud Accounts Waiting on Terms: An account that had not accepted Apple's updated terms failed with only no auth method found, with no way to tell what was wrong. The real reason is now shown.

  • Google Photos Client ID: The requirement to use your own client ID was not applied on the path the app actually takes.

Wizard​

  • Editing a Job Created by the Wizard: Source and Destination looked empty when editing, and saving wrote those empty values over the real ones.

  • Mount Location With a Remote Rclone (Windows): The Wizard suggested a home path on the local machine as the mount location while connected to rclone on another machine.

  • Local Folder as a Backup Source (Windows): Choosing a local folder as the source raised an error.

  • Mounting Through the Wizard (Windows): Mounting from the Wizard failed far more often than it should have.

  • Retrying With the Same Remote Name: After a failed sign-in, going Back and trying again with the same remote name was refused.

  • Renaming the Remote With Back: Going Back after creating a remote and continuing under a new name left the old remote listed next to the new one until the Wizard closed. If the task had already run, the rename deleted the remote that the saved mount, scheduled job, or Crypt remote pointed to. The earlier remote is now removed right away, and only when nothing saved by the Wizard uses it.

  • iCloud Photos in the Wizard: Adding an iCloud Photos remote after using Browse raised an error. iCloud Photos is now offered only in the Browse task; the Backup, Sync, Mount, Compare, and Crypt tasks no longer list it. Jobs that already use iCloud Photos as their source keep running, and you can still create one in Job Manager.

Language and Interface​

  • Untranslated Screens: The language dropdown itself, the two Telegram remote-control field labels, the Web Server settings section, and the iCloud Photos "sync automatically when the tab is activated" setting were shown in English in every language. The Japanese confirmation for deleting a job was missing the job's name.

  • Switch Rows in Settings: Switch rows inside a bordered settings section showed no ink effect and raised a debug assertion.

  • Help Popup in the Terminal: Typing a directory name in the terminal was treated as a command and brought up the help popup.

  • Version Information (Windows): Fixed the version information shown for RcloneView.

  • Changing the Database Folder Broke Saving: After the Database folder was changed in Settings, every save and lookup of jobs, mounts, and history failed until the app was restarted.

Packaging and Updates​

  • Bundled Rclone on Linux: The Linux packages were built with whatever rclone happened to be on the build machine and could ship a development build of rclone 1.60.1. The Linux builds now bundle the same pinned rclone as the other platforms.

  • Updates Not Reaching Existing deb/rpm Installations: A saved rclone path took precedence over the bundled binary, so the bundled rclone never took effect after an update.

  • "Update Rclone" Reported Success While Always Failing (Linux): Updating the bundled rclone in place could not succeed under a normal user account, but the app reported success anyway because it judged the result by the terminal's exit code — and the attempt interrupted transfers that were in progress.

  • "Update Rclone" Refused an Rclone You Own (Linux): With Local Rclone location pointing to an rclone owned by your account, Update Rclone showed the same "cannot write" notice as for the bundled one and never tried, so rclone could not be updated from the app on Linux at all. An rclone you own is now updated; the bundled one is still left to the package.

  • The aarch64 RPM Could Not Be Installed: The aarch64 rpm listed a Rockchip-only library (librockchip_mpp) as a requirement, so dnf install could refuse it on Fedora and other distributions that do not provide it.

  • Silent Build Failures: A build whose installer step failed could still be published as if it had succeeded, on both Windows and macOS. Those scripts now fail loudly.