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, stop scheduled jobs from running once for every open window, keep a batch Delete step inside the folder it names, and let RcloneView start on macOS 27. 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.
Global --checksum and --exclude now apply to jobs.
These two flags in Global Rclone Flags were overridden whenever a job ran. A job whose Enable checksum to compare files box was unchecked turned a global --checksum off, and every job sent its own exclude list — even an empty one — which replaced the global --exclude list. Dry runs already used the global flags, so the preview and the run could disagree. Jobs and batch steps now keep the global values: an unchecked box means “use the global setting”, and a job’s own exclude rules are added to the global ones.
This changes what existing jobs do if you keep --checksum or --exclude in Global Rclone Flags. Files matching a global exclude are no longer transferred, and a sync no longer deletes them at the destination. Files are compared by checksum, which can take longer where the checksum has to be computed. Please run affected jobs once with Dry run.
Do not go back to 1.6.6 or earlier after this update.
This update changes the database format so that it can record what happened to each file. If an earlier version opens the database afterwards, it deletes it and starts with an empty one: your jobs, batches, job history, saved mounts, and filter presets are lost. Remotes and settings are not affected. If you may need to go back, keep a copy of rclone_view.db from the Database folder shown in Settings before updating.
Data Loss and Security
A Batch Delete Step Deleted Outside Its Folder:
A Delete step in a batch ignored the folder path set in the step and deleted files from the whole remote instead of only from that folder. It now deletes only inside the step’s path; a step with no path still works on the whole remote, as before. Delete File and Purge steps were not affected. If you have run a batch with a Delete step, check the remote’s trash or version history for files missing from outside that folder.
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; a job overrode a global --checksum or --exclude from Settings; 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
This release also fixes a long list of problems across jobs, mounts, the explorer, remote creation, the Wizard, and packaging. The full list, grouped by area, is in the first reply below.
Thank you for using RcloneView.
We appreciate your continued feedback and support as we expand cloud integration and remote management capabilities.
— The RcloneView Team