Pakua SysManager 1.56.4

[1.56.4] - 2026-08-03
Fixed
- Kept DNS changes and Undo bound to the same captured network adapter. Since snapshot-based Undo was introduced in v1.20.5, capture and apply selected the active adapter in separate PowerShell calls. A VPN connection, cable change, or adapter transition between those calls could capture interface 12, modify interface 27, and later restore only interface 12. Snapshots now include both the interface index and stable adapter GUID. Preset apply and DHCP reset verify that identity plus the confirmed IPv4/IPv6 addresses and automatic/static sources in the same PowerShell script that performs the first mutation; each later command rechecks adapter identity, and preset IPv6 revalidates the post-IPv4 DNS state before its second mutation. Undo resolves the stable GUID again before every restore command, so the same adapter remains targeted even if Windows assigns it a new interface index.
- Made DHCP reset confirmable and reversible, and rejected incomplete snapshots. Reset to automatic now uses the same pre-change snapshot flow as preset apply, and each confirmation identifies the captured interface before mutation. After consent, the adapter and DNS state are captured again; if either changed while the dialog was open or before the guarded mutation began, the operation stops without changing DNS or leaving a stale Undo entry. Snapshots separately record whether IPv4 and IPv6 were automatic or static, so effective DNS addresses supplied by DHCP are never restored as persistent static overrides. If no active adapter, no valid stable identity, or no complete read of both address families and their configuration sources can be captured, the operation stops before changing DNS. Ambiguous partial failures retain a safety snapshot while proven pre-mutation failures expose the prior successful rollback point instead of hiding it. A successful retry now keeps the last trustworthy pre-failure snapshot instead of replacing it with partially changed state, and an IPv6 command failure is reported as a partial failure while Undo remains available.
- Preserved recovery for every adapter after interleaved partial failures. If ambiguous failures occur on more than one adapter before a retry succeeds, Undo now collapses only untrusted snapshots for the retried adapter. Recovery points for every other possibly changed adapter remain available in newest-first order through later successful changes, until each is restored.
- Kept DNS recovery status and consent accurate. A failed Undo now refreshes the displayed current DNS before reporting the error, because reset or reapply steps may already have changed one address family. Restore confirmation refers to the previously changed adapter rather than showing its stale captured interface index after Windows renumbers that adapter.
Verify the download
Get-FileHash .\SysManager-v1.56.4.exe -Algorithm SHA256
Expected SHA256: DD2BB74300D5804CE43354E1B3356BC1B9D6352B815A92C66F315A0BFF43BE21