Hey everyone,

VaultSync 1.8.6 is now available.

This release has been a bit different from 1.8.4 and 1.8.5.

Those updates did a lot of work around recovery: better evidence, recovery drills, clearer readiness states, and making the distinction between having a backup and knowing you can recover it much more explicit.

While building that out, another problem became increasingly obvious.

VaultSync had become much better at knowing what was happening, but not always good enough at explaining it.

A scheduled backup could be behaving exactly as intended while still looking confusing.

A project could need attention, but the important part could be surrounded by too much information.

And as more capabilities were added, some basic questions — What needs my attention? What happens next? Where do I go to fix it? — were becoming harder to answer than they should be.

That is what 1.8.6 — Everyday Clarity is mostly about.

A Dashboard built around what matters first

The Dashboard has had one of its biggest reorganizations so far.

Instead of trying to show a little bit of everything at once, the top of the page is now built around a few immediate things:

• current protection/recovery status;
• the highest-priority action that needs attention;
• the next scheduled run;
• recent activity;
• the latest known-good recovery point.

There are also direct paths into Recovery, Schedule, and History when you need to go deeper.

The idea is pretty simple: opening VaultSync should tell you what matters before making you hunt for it.

Scheduling finally has a proper workspace

Schedule has also been rebuilt into a dedicated operational page.

It now brings together:

• whether automatic protection is ready to run;
• which projects participate;
• when each project was last backed up;
• destination and runtime conditions;
• the next scheduled opportunity;
• upcoming timer opportunities;
• shared scheduling policy;
• explanations when work is delayed.

One distinction I especially wanted to make clearer is that a scheduled opportunity does not necessarily mean another backup will be written.

VaultSync can check a project and find that nothing changed, or runtime conditions can delay the work.

Those cases should look intentional rather than like the scheduler simply failed.

Project folders are now properly optional

Project folders have had quite a bit of work too.

If you don't need folders, you don't have to use them.

Projects outside folders continue to use the normal project-card list.

If you do want organization, folders now have explicit membership, expandable project lists, aggregate protection health, contextual management, and folder-level snapshot, backup, pause, and resume actions.

Grouped projects stay inside their folder instead of also being duplicated at the top level.

Moving a project into a folder is also now an explicit preview-and-move action rather than something that silently reorganizes the hierarchy.

Folders are organizational objects inside VaultSync, with safe folder deletion built into the workflow.

Project settings are much easier to manage

Individual projects now expose more of their configuration directly.

You can edit:

• destination;
• snapshot preset;
• exclusions;
• tags;
• encryption;
• automatic-backup participation.

Project removal has also been made much more explicit.

Removing a project from VaultSync removes its local registration and history-index state.

It does not delete the original source files or the stored backup payloads.

The confirmation UI now explains that distinction before you commit to the action.

The Guide follows what you've actually done

The old first-run overlays are gone.

They have been replaced by a compact, resumable sequence driven by the real state of VaultSync.

The path is essentially:

1. Set up VaultSync
2. Protect a project
3. Choose when protection runs
4. Browse and restore
5. Prove recovery

It tracks actual source, destination, project, schedule, restore-point, and recovery-drill state rather than simply deciding that you completed onboarding because you clicked through a tour.

One change I particularly wanted here: recovery proof is not considered complete until a recovery drill has actually passed.

The Guide also now gives consistent definitions for terms like backup, snapshot, restore point, verification, known good, protected, and recovery drill.

Backup progress is no longer inferred from UI text

There is also a less visible change underneath the interface that I think is important.

VaultSync previously had places where backup stages were derived from display text.

1.8.6 replaces that with shared typed protection activity states.

VaultSync now explicitly understands states such as:

• queued;
• scanning;
• hashing;
• writing;
• verifying;
• waiting;
• retrying;
• completed;
• cancelled;
• failed.

The same semantics are used across manual and automatic protection activity.

It sounds like a small internal detail, but it makes progress reporting far less ambiguous and gives the UI something reliable to build on.

Safer actions and better accessibility

There has also been a pass over accessibility and potentially destructive operations.

Primary workflows now have additional screen-reader names and help.

Settings actions such as reset, clearing local cache, removing project-index data, credentials, or encryption passwords now have reviewable confirmation previews before anything is changed.

The same idea applies elsewhere in the app: if an action has consequences, VaultSync should explain them before asking you to confirm it.

And quite a bit underneath all of that

There are a lot of smaller fixes in 1.8.6 as well.

Folder identity now carries through Schedule, Backups, Recovery, and History, including folder-aware search and grouped scheduling information.

Backup cards now refresh correctly when things like tags, folder membership, or external identity change.

Additional diagnostics were added around scan-cache writes, NAS staging checks, and deferred-backup migrations where failures could previously be too quiet.

Rich-text links are now restricted to approved external URI schemes rather than allowing file, script, data, or shell links to be launched from rendered content.

There has also been work on narrow and wide layouts, theme consistency, release validation, static-analysis findings, and the VaultSync visual identity across the various platforms.

The optional-folder workflow has also been completed across all maintained locales.

1.8.4 and 1.8.5 pushed VaultSync much further toward recovery confidence.

1.8.6 is about making the rest of the application easier to understand around it.

There are fewer assumptions now about what the user is supposed to infer from a status, a timer, a folder, or a button.

And that's really what I wanted from this release.

As always, feedback is very welcome — particularly around the Dashboard, Schedule page, project folders, project editing, and Guide.

GitHub:
https://github.com/ATAC-Helicopter/VaultSync

Microsoft Store:
[https://apps.microsoft.com/detail/9N9HRX4JCLCP]()

Website:
https://fglabs.dev/vaultsync

[link] [comments]