Esta es una versión anterior. La versión actual es 0.5.5. GUARD 0.5.5 · Fecha de publicación:
Archivos de instalación 0.5.3
| Arquitectura | Tipo | Ámbito | Tamaño del archivo | Descargar | SHA256 |
|---|---|---|---|---|---|
| Cualquier procesador | ZIP → Portable | — | — | github.com | VirusTotal |
El enlace y el SHA256 proceden del manifiesto comunitario del Administrador de paquetes de Windows. Conviene comparar el hash del archivo descargado antes de ejecutarlo.
Notas de la versión
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
