GUARD: baixar versions anteriors

GUARD v0.5.5 is a bug-squashing release. Testing the app's daily usage and thoroughly reading through the codebase turned up several faults: a few instances where GUARD would stay silent or unresponsive when something went wrong, the possibility that your files or settings could get stranded, and an unlikely, but possible, app crash.
Fixed
- Restoring app settings could move your settings folder aside and put nothing back, then report success. GUARD renames an existing settings folder aside before copying the saved copy over it. If the drive holding the saved copy was disconnected during the reinstall that runs first, the copy quietly did nothing, the folder stayed renamed, and the summary counted it as restored. GUARD now re-checks the saved copy just before each folder is restored; a restore that cannot read it leaves your folder exactly where it is, and the summary names the folders it left alone.
- A . or \ destination subfolder was accepted, and a Mirror backup would then delete the rest of your backup. Both mean the destination itself, so a pair saved that way mirrored into the root and the next run purged every other folder's backup. Both are now refused when a folder is added or edited. Folders already saved that way keep working and are left alone.
- Saving one page's settings could replace the other page's with defaults. If the settings file could not be read at that moment - held open by another program, or on a drive that had gone away - GUARD treated the failure as "no settings yet" and wrote defaults over the fields the page does not own. Starting GUARD while the file was unreadable could then overwrite it entirely. GUARD now tells the difference between "no settings yet" and "settings could not be read", refuses to save over what it could not read, and says so.
- A backup that gave up before it started said nothing at all. An unreachable destination, or a scheduled backup already holding the run lock, ended the run before the first folder, so no outcome was announced and the progress line kept reading "Measuring folders...". Worse, a run skipped because another backup held the lock left the previous run's green "succeeded" on screen as the only signal. Every run now ends with a spoken outcome, and one skipped for the lock says so.
- Stop Backup did nothing if pressed before the backup itself started. The button was live during the save and folder checks that precede the run, but a press in that window went nowhere. It now takes effect at the next step, and acknowledges the press immediately either way.
- Stopping a reinstall while settings were being restored hid where your folders went. The cancelled run reported only the app counts, leaving out the restore tally and, with it, the location of any folder that had been moved aside and could not be put back.
- An app list containing an empty entry closed GUARD without a message. Importing JSON with a null entry in it crashed the app on the spot; such entries are now skipped.
Full changelog: https://github.com/PlanetLinux98/guard/blob/main/CHANGELOG.md#055---2026-08-14

GUARD v0.5.4 is a data-safety release. A use-case audit turned up four ways GUARD could break a backup, or tell you it had protected something when it hadn't.
Fixed
- A Mirror-mode folder pair could delete the rest of your backup. Typing . as the destination subfolder - a reasonable way to ask for "put these files at the top of the backup drive" - sent that pair to the destination root, and the check that stops two pairs mirroring into the same place didn't recognize it as the root, so the save went through and the next run's mirror deleted every other folder's backup. GUARD now reads . as the root it is, and blocks the save the way it already blocks two pairs sharing a folder.
- A backup whose source folders were all missing reported success. If the drive holding them didn't mount, or a network share was down, the run still finished green and an unattended run raised the "finished successfully" notification, so you could go weeks believing you were protected while nothing was being copied. A source that isn't there is now reported as an error. If you back up a drive that isn't always connected, runs made while it's absent will now report an error instead of success.
- Updating while a scheduled backup was running could leave a broken install. GUARD waited for its own window to close, but not for a scheduled backup, which runs as a second GUARD process. The update could unpack over files still in use and leave the folder part old and part new, with GUARD never restarting. It now waits for every GUARD process, and will abandon an update rather than unpack over one that's still running.
- The scheduled system image could be left switched on, or never switched on at all. GUARD reported the schedule as saved whether or not Windows accepted the change: one you switched off could keep taking images on schedule, and one you switched on could never be registered if the Administrator prompt was declined. Either way the page showed the schedule as saved and Save was greyed out, so there was no way to try again. GUARD now checks what Windows actually did, says so when it didn't take, keeps Save available to retry, and notices at startup if the scheduled image has gone missing.
Full changelog: https://github.com/PlanetLinux98/guard/blob/main/CHANGELOG.md#054---2026-08-06

GUARD v0.5.3 fixes various bugs to ensure GUARD keeps protecting the things you ask it to, and adds a way to clean up its data on-demand.
Added
- Settings gains Remove GUARD's Scheduled Tasks, which unregisters GUARD's schedules from Windows. Run it before deleting or uninstalling GUARD, so that tasks don't get left behind and keep firing at an app that's been removed.
- GUARD now warns when a folder has nothing left to back up while your backup still holds files from it, and when the backup destination is empty but records show a backup has run (deleted backup or reformatted drive).
Changed
- Installed with winget, GUARD now keeps its settings, scripts and logs in %LOCALAPPDATA%\GUARD and updates through winget upgrade rather than updating itself: winget deletes its whole install folder on upgrade and uninstall, which would destroy anything kept there. Set your settings up once more after this update; they'll survive from now on. A folder you extracted yourself stays fully portable.
Fixed
- GUARD installed via winget install would previously not launch, and a scheduled backup task saved under that install would silently never run, because winget's portable packages launch through a symlink Windows reports as the app's real location.
- The default backup folders (Documents, Desktop, etc.) were fixed paths, so if Windows moved one - OneDrive's "Back up your folders", or a folder's Location tab - GUARD backed up the empty folder left behind and still reported success. GUARD now tracks each default row and offers to follow a move.
- Every date GUARD showed or wrote followed the system locale's calendar, so on a Thai or Arabic Windows the versioned backup folder names carried Buddhist or Hijri dates. That's the dangerous one: pruning deletes the oldest by name, so a later locale change could make it delete the newest backups first. If you're on such a Windows with existing versioned backups, delete the old wrongly-named folders once.
- Online-only OneDrive files could be left out of backups, size estimates included.
- Folder paths in warnings and confirmation dialogs were shown unexpanded, the literal %USERPROFILE%\Documents text was visible on screen, and a screen reader read it out as "percent USERPROFILE percent backslash." They now show, and announce, the real path names as they're actually written.
- Two portable copies of GUARD installing winget at once could wipe each other's half-finished download.
- Building recovery media, and "View Existing Images", failed with nothing to show on a copy where no backup had run yet.
Full changelog: https://github.com/PlanetLinux98/guard/blob/main/CHANGELOG.md#053---2026-08-01

Largely a bug-fix release: a broad pass over the app closed up crashes, races, and a few data-safety gaps that had crept in.
Safer backups and app settings
- A drive that isn't your real backup destination can no longer be adopted silently: if the last-used drive letter now points at a different, reachable volume (for example, the real drive was unplugged and something else took its letter), Save now warns and needs a second Save to confirm, instead of risking that drive's files being deleted as "extras" in Mirror mode.
- Restoring app settings no longer risks losing the original folder: if putting the saved copy back failed right after the existing folder was renamed aside, GUARD now tries to move the original back first, and only reports it separately (with its location) if that also fails.
- A backup that robocopy couldn't fully reconcile (a "Mismatch", such as the destination having a file where the source now has a same-named folder) is now counted and called out in the run summary instead of being reported as a clean "Backup complete".
- Restoring app settings only accepts the three folder locations GUARD's own export writes (%APPDATA%, %LOCALAPPDATA%, %USERPROFILE%\.config), closing a gap where an imported manifest could target other folders for rename-aside-and-replace.
- App settings export and restore are more accurate: a symlinked or hard-linked file is now skipped like the folders around it (matching robocopy's own behaviour), and a subfolder that fails to enumerate is counted as an abandoned subtree rather than a single skipped file.
No more silent crashes
- A locked or momentarily unreadable settings file (an antivirus scan, the file open elsewhere, a laggy portable or network copy) no longer crashes GUARD on launch or the headless scheduled backup task; both fall back to defaults.
- Non-ASCII paths, drive names, and PowerShell error text are no longer mangled: GUARD's shell-based tooling now writes and reads UTF-8 throughout, fixing failed backups, skipped folders, broken self-update for non-ASCII usernames, and garbled captured errors.
- Self-update no longer fails when GUARD is installed at a drive's root (like the top of a USB stick) or under a path containing a literal %.
- An unusual GitHub release response with no assets at all no longer crashes the update download; it now falls through to the normal "no compatible download" message.
Recovery Media and System Image, hardened
- The recovery-media wizard is more robust against interruption: closing GUARD while it's writing a USB is now blocked, and a preparation error before the elevated step starts lands on the wizard's own "Could not finish" result instead of crashing GUARD.
- The USB list now warns before erasing a drive much larger than a typical recovery stick, so an external hard drive isn't mistaken for a blank flash stick.
- Opening System Image on a Windows edition without wbadmin (like Home) no longer invents an unsaved change when it automatically unticks a saved schedule.
- The System Image page's "Next run" time now loads when GUARD opens, not only after a save.
- A scheduled system image now registers correctly on non-Gregorian-calendar Windows locales (such as Thai or Umm al-Qura).
- Saving a system image now warns about a destination containing a stray %, matching the same protection File Backup already had.
More accurate status, fewer races
- Only one action runs at a time: backup, system image, winget reinstall/update, app-settings export, and app scan now check whether another is already running and name it, instead of racing each other with stacked elevation prompts.
- The installed-app scan no longer mistakes "winget doesn't know the version" for "already up to date" when a row has a blank installed version but a populated available-upgrade version.
- A fast double-click on Reinstall Selected or Update All Apps can no longer start two overlapping runs.
- Closing GUARD while "Update All Apps" is running with Administrator rights now actua

Largely a bug-fix release: three audit passes over the whole app polished up many of the rough edges that had crept in across GUARD's development, alongside a few additions that round out existing features.
Sturdier day to day
- Several ways GUARD could crash or lock up are gone: a settings save that fails (for example, GUARD run from a read-only folder) now shows an error instead of crashing, double-clicking Run Now can no longer start two backups at once, a failed folder picker no longer takes the app down, and an error during a reinstall or settings restore no longer leaves the App Management buttons disabled for the rest of the session.
- A hung winget or PowerShell no longer pins its page for the whole session (a scan stuck on "Scanning...", a save that never finished): background helpers now have a hard deadline and are stopped and reported when they exceed it.
- Save Settings now blocks setups that could never produce a good backup: Mirror-mode folders that share or nest their destination subfolders (each run purged the other's files), and a fully-unticked folder list that would "succeed" while copying nothing.
- Settings files, generated scripts, and app-list exports are written crash-safe, so a crash or power cut mid-save can no longer leave a truncated file behind.
- Only one backup runs at a time: a scheduled run firing during an in-app run (or vice versa) now skips cleanly instead of interleaving two passes over the same log, and a second GUARD.exe launched from the same folder brings the open window to the front instead of running twice.
- Elevated actions (System Image, Recovery Media, task registration) are more reliable and safer: the script now travels inside the PowerShell command rather than through a temp file, fixing corrupted non-ASCII account and install paths and closing a brief tampering window; an apostrophe in GUARD's folder path no longer breaks Create Image Now.
- A moved or renamed GUARD folder no longer silently breaks scheduled backups: the tasks re-register against the new location at the next launch or save.
- Skipping an offered update now really skips it: it also cancels a copy that auto-install had already staged, and each portable copy of GUARD stages updates in its own folder so two copies can no longer apply each other's update. An update also now refuses to install when the release lacks its SHA256SUMS checksum file.
Quieter and more honest
- Scheduled and on-connect backups now run with no visible window: the on-connect check (every 15 minutes) no longer flashes a console while you are signed in. Existing tasks migrate automatically.
- The backup size estimate now honours exclusions, so large excluded trees (like node_modules) no longer trigger false "space may be too low" warnings, and Preview writes its own log instead of overwriting the real backup log.
- The app scan is more truthful: Microsoft Store apps are labelled "Store" instead of "Winget", apps whose names winget truncated no longer show up twice, and the scan now works on localized (non-English) Windows, where every app was previously reported as "Manual".
- Fresh installs no longer pre-tick the "Developer folders" exclusion preset, whose folder names ("bin" especially) can carry real user data.
Screen-reader polish
- Toggling a checkbox or radio button with its Alt access key is now announced by NVDA: the access key toggled the control without moving focus to it, so every access-keyed toggle now moves focus first.
- Keyboard focus starts on the navigation at launch instead of the empty pane, so a screen-reader user is no longer left on "GUARD, pane" needing an extra Tab.
- Silent status repaints from a background page no longer disturb the active page's announcements, which could re-announce an unchanged status or drop a changed one.
New in this release
- GUARD can now install winget itself on PCs that lack it (LTSC, Server editions, or no Microsoft Store): an "Install winget" notice appears when the app scan finds it miss