VaultSync 1.8.8 — Stability

VaultSync 1.8.8 is a stability-focused release centered on interruption safety, filesystem boundaries, large-repository performance, updater qualification, Linux/Wayland support, and reliability across backup, restore, metadata, and cleanup workflows.

Rather than introducing another large feature set, this release concentrates on making existing VaultSync operations safer when files disappear, destinations become unavailable, cancellation arrives at difficult points, or an operation is interrupted before completion.

Highlights

Deterministic interruption and recovery handling

VaultSync now has repeatable interruption and recovery qualification for both plain and encrypted archives.

A broad set of backup and recovery paths have also been hardened around cancellation and partial failure.

Improvements include:

• preserving completed backups when cancellation arrives after commit;
• rejecting scans cancelled while processing the final entry;
• failing backups when required snapshotted source files become unavailable;
• rejecting vanished backup data before publishing metadata;
• propagating verification cancellation instead of reporting a mismatch;
• rolling back interrupted restores;
• rolling back interrupted metadata imports and exports;
• preserving rollback evidence when restore destinations disappear;
• preserving retention metadata while backup destinations are unavailable;
• preserving deferred metadata when destinations disappear during replay;
• isolating cancellation ownership between overlapping backup runs.

Safer filesystem and temporary-data boundaries

1.8.8 tightens the boundaries around filesystem traversal, cleanup, decrypted workspaces, and encrypted restore staging.

Changes include:

• snapshot scans no longer follow linked source paths;
• retention cleanup is confined across filesystem links;
• disposable cleanup cannot traverse linked children;
• decrypted-open workspaces are isolated between application processes;
• decrypted-workspace cleanup is confined to exact operating-system temporary children;
• encrypted restore staging avoids predictable location collisions;
• temporary telemetry exports are limited to 30 days and 100 MB.

Abandoned temporary writes for release caches, installation identity, credential indexes, and support bundles are now cleaned up safely.

Large-history and high-file-count performance

VaultSync now includes repeatable performance budgets for large histories and high file counts.

Snapshot creation has also been reworked around:

• isolated snapshot stages;
• deferred hashing;
• checkpoint telemetry;
• native-copy orchestration.

Archive and support-package generation now reduce memory use through buffer reuse and streaming hashes.

Cancellation performance checks have also been made deterministic on smaller CI runners.

Native Wayland support

Linux builds now support native Wayland, with automatic X11 fallback where required.

Linux windows are explicitly opaque to avoid compositor and transparency issues under native Wayland.

Linux updater qualification

Safe patch updates have been qualified across multiple installed Linux versions.

When the currently installed version is not an approved patch base, VaultSync falls back to the full installer.

Additional updater changes include:

• keeping VaultSync open until privileged update authentication succeeds;
• rejecting mismatched or duplicate patch-base inventories;
• correcting stale multi-version updater guidance;
• clearing remaining updater security and maintainability findings.

Guided setup and UI responsiveness

Guided setup now provides more actionable next steps.

Guide and Schedule queries have been moved away from the UI thread.

Additional UI fixes include:

• removing unintended horizontal page and dialog scrolling;
• keeping metadata-conflict review readable in narrow windows;
• loading registered projects into the tray menu before another page has been opened.

Release, CI, and static-analysis cleanup

The exact 1.8.7 release state has been qualified and pinned workflow security actions have been updated.

Release-branch CI and Sonar execution have been deduplicated and bounded.

Remaining Sonar findings have been cleared across:

• core code;
• updater;
• onboarding;
• storage hygiene;
• release automation.

Failed installer downloads are now removed immediately.

Additional reliability fixes

1.8.8 also includes fixes for:

• scan-cache publication before snapshot persistence;
• metadata-conflict and backup-repair busy-state isolation;
• isolated profiles opening the normal database;
• abandoned release-cache writes;
• abandoned identity and credential-index writes;
• abandoned support-bundle staging;
• deferred metadata replay;
• backup destination disappearance;
• restore rollback;
• cancellation timing;
• patch inventory validation;
• macOS system Python compatibility.

Warning

Clean reinstall may be required

If VaultSync 1.8.8 does not update cleanly or behaves unexpectedly after updating, uninstall the application and install a fresh copy.

Your VaultSync database, registered projects, history, settings, and persistent app data are stored separately from the application and are not deleted by a normal uninstall.

• Windows Intel/AMD: use the Windows x64 package and uninstall from Settings → Apps.
• Apple Silicon Mac: use the macOS ARM64 / Apple Silicon DMG and replace VaultSync.app in Applications.
• Intel Mac: use the macOS x64 / Intel DMG and replace VaultSync.app in Applications.
• Linux Intel/AMD: use Linux x64 / x86_64; prefer the .deb package on Debian/Ubuntu/Zorin-style systems.

On Linux, remove only the installed package/application files. Do not manually delete VaultSync's user-data directories unless you intentionally want to reset the application.

The VaultSync website and GitHub Releases provide the same release packages.

Downloads

Packages for Windows, Linux, and macOS are available below.

Direct GitHub packages remain intentionally unsigned. Please download them only from the official VaultSync repository and verify downloaded files using the published SHA-256 checksums.

VaultSync is also available free through the Microsoft Store.

Links

• Website: https://fglabs.dev/vaultsync
• Microsoft Store: https://apps.microsoft.com/detail/9N9HRX4JCLCP
• Source: https://github.com/ATAC-Helicopter/VaultSync

---

Changelog

[1.8.8] -

Added

• [VS-1823] Added repeatable large-history and high-file-count performance budgets.
• [VS-1882] Added deterministic interruption and recovery qualification for plain and encrypted archives.
• Added native Wayland with automatic X11 fallback and opaque Linux windows.

Changed

• [VS-1885] Cleared Sonar findings in release automation, onboarding, and storage hygiene.
• [VS-1886] Reduced archive and support-package memory use with buffer reuse and streaming hashes.
• [VS-1887] Made guided setup actionable and moved Guide and Schedule queries off the UI thread.
• [VS-1884] Qualified exact 1.8.7 state and updated pinned workflow security actions.
• [VS-1888] Cleared remaining core Sonar annotations.
• [VS-1889] Qualified safe multi-version Linux patch updates with installer fallback.
• [VS-1821] Isolated snapshot creation, deferred hashing, checkpoint telemetry, and native-copy orchestration.

Fixed

• [BUG-18116] Removed unintended horizontal page and dialog scrolling.
• [BUG-18117] Confined retention cleanup across filesystem links.
• [BUG-18118] Failed backups when required snapshotted source files become unavailable.
• [BUG-18119] Isolated decrypted-open workspaces between app processes.
• [BUG-18120] Prevented disposable cleanup from traversing linked children.
• [BUG-18121] Removed abandoned verified release-cache writes safely.
• [BUG-18122] Removed abandoned identity and credential-index writes safely.
• [BUG-18123] Removed abandoned support-bundle staging safely.
• [BUG-18124] Limited recognized temporary telemetry exports to 30 days and 100 MB.
• [BUG-18125] Prevented predictable encrypted-restore staging collisions.
• [BUG-18126] Confined decrypted-workspace cleanup to exact OS temporary children.
• [BUG-18127] Isolated cancellation ownership between overlapping backup runs.
• [BUG-18128] Prevented duplicate and unbounded release-branch Sonar runs.
• [BUG-18129] Published scan-cache state only after snapshot persistence succeeds.
• [BUG-18130] Deduplicated and bounded release-branch CI and analysis runs.
• [BUG-18131] Prevented snapshot scans from following linked source paths.
• [BUG-18132] Propagated verification cancellation instead of reporting a mismatch.
• [BUG-18133] Rolled back interrupted restores instead of leaving partial target changes.
• [BUG-18134] Rolled back interrupted metadata imports and exports.
• [BUG-18135] Preserved completed backups when cancellation arrives after commit.
• [BUG-18136] Rejected scans cancelled while processing the final entry.
• [BUG-18137] Rejected vanished backup data before publishing metadata.
• [BUG-18138] Preserved rollback evidence when restore destinations disappear.
• [BUG-18139] Kept retention metadata while backup destinations are unavailable.
• [BUG-18140] Preserved deferred metadata when destinations disappear during replay.
• [BUG-18141] Isolated metadata-conflict and backup-repair busy state.
• [BUG-18142] Removed failed installer downloads immediately.
• [BUG-18143] Made cancellation performance checks deterministic on small runners.
• [BUG-18144] Kept isolated profiles from opening the normal database.
• [BUG-18145] Kept metadata-conflict reviews readable in narrow windows.
• [BUG-18146] Loaded registered projects into tray menus before opening a page.
• [BUG-18147] Kept Linux open until privileged update authentication succeeds.
• [BUG-18148] Kept script validation compatible with macOS system Python.
• [BUG-18149] Cleared updater security and maintainability quality-gate findings.
• [BUG-18150] Rejected mismatched or duplicate patch-base inventories.
• [BUG-18151] Corrected stale multi-version updater guidance.