← SafeDSXEarly-access release notes
Release: 1.0.1 preview, 5 October 2026.
Updated
- Server-registered 90-day trial, signed licensing, product keys with device limits and revocation.
- Separate download-request and first-launch statistics; an owner-only administration service.
- Optional metadata-only error reporting and signed update metadata.
- Read-only USB disk imaging with volume locks, avoiding unsupported removable-disk offlining.
- File/folder/disk plans, saved source identity, editing, last result and progress records.
- Selected plan source and destination are displayed in full. Recent results appear before secondary columns.
- Disk retention affects only that plan’s completed archives. Existing incremental baselines are retained until chain-aware cleanup is available.
- SQL services that were already stopped remain stopped. Partially stopped services are restarted on failure.
- Scheduled backups use a SafeDSX-specific protected-folder permission instead of disabling Windows protection globally.
- Updates refuse to interrupt an active backup or recovery operation.
Validation
51 regression tests passed. Additional license expiry, signature and clock tests passed. A complete attached USB image and full archive verification succeeded without source changes. Scheduling and file backup were exercised separately.
Still requiring release validation
- The installer is not yet Authenticode signed.
- Booting the recovery USB and full physical Windows restoration need independent hardware validation.
- Small-target migration depends on supported partition layouts; used data fitting alone does not guarantee disk-image restoration.
- SSD sanitize support depends on the controller. Unsupported hardware cannot be advertised as securely erased.
- Some technical error text can still originate in English from Windows and external components.
- Cloud-source imports use locally synchronized content; direct Google/iCloud account ingestion and writable encrypted virtual-disk drivers are not included.
This remains an early-access release. Keep current recovery points and test restoration before relying on a backup.