Release notes
Newest first. The agent version is the one shown in the console's Agents list; agents update themselves within minutes of a release, and the console is redeployed with it.
1.0.261 — 25 September 2026 #
- The tray's activity panel now scales with your display. On a screen set above 100%, the transfer rows were drawn at their 100% size while the text was drawn larger, so file names were clipped and rows overlapped each other. The panel, its rows and the enrolment and version-history windows now size themselves from the text they actually contain, so they follow both display scaling and a larger text setting.
1.0.260 — 24 September 2026 #
- "Job completed with warnings" is now its own notification, with its own switch, off by default. Anything that was not a clean success used to be announced with the subject "FAILED", including runs that finished and copied their data. Warnings repeat — one file an antivirus will not release produces the same one every night — so they are silent unless you ask for them, under Settings → Notifications → Alert Triggers.
- A quiet night is no longer reported as a failed backup. A file the agent can never read — one blocked by antivirus, for instance — failed every run. On nights when other files changed that was a warning, but on nights when nothing changed the run was marked Failed, even though every file had been checked and confirmed already backed up. Runs are now only Failed when nothing at all succeeded.
1.0.258 — 21 September 2026 #
- Hyper-V incremental: the third night of a chain fell back to a full because the previous night's local differencing disk had been removed; the host now keeps a header-only stub of every layer (a few MB each), so chains run to the weekly full as designed. The VM's runtime-state file is no longer uploaded — a restore boots the application-consistent disk cold and has no use for it.
1.0.257 — 20 September 2026 #
- Hyper-V incremental: the VM's definition (.vmcx and companions) is now taken through Hyper-V's own export rather than copied from the live files the host holds open, so incremental runs no longer close as Warning on every host.
1.0.256 — 18 September 2026 #
- Hyper-V changed-block incremental backup, redesigned. A VM's backup is now a real .vhdx base plus one small differencing disk per night, with a fresh full weekly, all stored as ordinary files in the customer's storage — no flattened images. First production night on a 320 GB mail server: 64 minutes for the base, then 8 minutes and 20 GB the next night. Restore is a standard merge (Merge-VHD).
- Console: a Help button on the title bar and a "Help & documentation" entry in the account menu open this site.
- macOS: the supported floor is macOS 26.
1.0.255 — 16 September 2026 #
- Re-enrolment. An agent whose enrolment the server definitively rejects (a token from another server, a deleted agent) now discards it, unmounts and forgets its drives, and asks for a new token — instead of retrying forever while the tray said "Registered".
- Uninstall forgets the machine: token, local database and drive cache are removed on a real uninstall (upgrades keep them), so a reinstall enrols cleanly.
- Every binary is code-signed, not only the installers; no more Defender or SmartScreen prompts during install.
1.0.254 — 15 September 2026 #
- Hyper-V: a checkpoint left behind by an interrupted run is recorded and merged at the start of the next run, in any mode. Service-stop grace raised to three minutes so an ordinary stop can finish a merge.
1.0.253 — 14 September 2026 #
- Uploads: streamed uploads to S3-style and Azure storage are bounded by the declared length (a raw device read past its end had failed a 130 GB disk after fully streaming it).
- Hyper-V: the changed-block path never streams a flattened image; with no reference point the disk goes to the writer full path. Change tracking is enabled explicitly; a rejected reference point is forgotten.
- Crash reporting: an unhandled exception and a service stop now ship their last log lines to the console before the process ends.
1.0.252 — 10 September 2026 #
- Run logs say what happened to every file: backed up, skipped unchanged, skipped in use, skipped encrypted, failed — for file, Microsoft 365 and VSS jobs alike.
- EFS-encrypted files are a warning, not a failure, and are named.
- Concurrency: an agent reports every run it owns on check-in, so a long run is never marked abandoned and double-started.
- Cloud runs report which file failed and why.
1.0.248 — 9 September 2026 #
- Console: resellers see and edit their own customers; connector tiles greyed on trial with the reason; deployment tokens single-use by default; several visibility fixes found while writing this documentation.
- Archiving Policy folder marking in the storage browser, with inheritance shown.
- Website: a real book-a-demo form.
1.0.247 — 8 September 2026 #
- Multi-source jobs: each source path is namespaced at the destination by its full path, so two folders holding a file of the same name no longer overwrite each other. Affected jobs were re-baselined.
1.0.236 — early September 2026 #
- Connectors: "Back up all — including ones created later" for mailboxes, OneDrives and sites; new users are swept in on every run.
1.0.233 — late August 2026 #
- Version history uses native bucket versioning where the bucket has it, server-side copies where the provider can, and download/re-upload elsewhere — one behaviour across jobs and drives.
1.0.221 — August 2026 #
- Cloud drives: conditional writes across machines — the second save of a file edited on two machines keeps its work as a conflicted copy instead of overwriting.