AnduinOS 2.0.4's headline feature is a graphical Rescue Center for dead systems — and its release notes are refreshingly honest about what it can't fix yet.

Point releases of small distributions usually read like grocery lists: a version bump here, a theme tweak there. AnduinOS 2.0.4, released October 4, is a point release about something much less glamorous and much more valuable — getting you back into your machine when it refuses to boot. It is, in effect, a reliability release wearing a point-release number, and the way the project's own release notes talk about its limits is the best part.

What the Rescue Center actually does

AnduinOS is a Windows-lookalike, Ubuntu-based distribution built by former Microsoft engineer Anduin Xue, aimed squarely at people migrating off Windows. Its new Rescue Center lives in the Live desktop and does the job that usually requires a chroot session and a memorized cheat sheet: it discovers installed AnduinOS systems and opens a dedicated recovery workspace.

Concretely, it offers password resets, file browsing, and restoration of compatible Btrfs system snapshots — even when the installed desktop won't start. Before a restore, it takes a safety snapshot of the current system by default while leaving the separate Home subvolume untouched, and it rechecks the selected device before modifying anything.

That last detail matters. A recovery tool that blindly trusts its own UI is a data-loss tool with good branding. AnduinOS's choice to snapshot-first and re-verify before writing reads like someone who has answered enough forum posts about bricked systems.

Guided boot repair, with the guardrails spelled out

Alongside the Rescue Center comes guided boot repair: the tool diagnoses boot files and performs guided repair for supported offline UEFI installations, with live progress and expandable command output. An emergency terminal is also available from the Live environment, mounted inside the selected offline system.

What separates this from a marketing bullet point is the list of things it cannot do yet: encrypted filesystems and automated package repair are explicitly out of this release. Guided repair requires the installation's EFI partition to be on the same disk — BIOS setups, separate /boot, and cross-disk EFI layouts need manual diagnosis. A successful repair still needs a real reboot to confirm the machine actually starts.

This is unusual candor for release notes, and it is the correct engineering posture. A recovery tool that documents its own boundaries teaches users to trust it within those boundaries. The alternative — silent failure in edge cases — is how recovery tools earn their reputation for making things worse.

The installer got the same treatment

The release carries the same reliability obsession into installation. The Live boot now checks the installation medium and reports progress or a recoverable error, and the installer verifies its source image again as a privileged preflight step before touching partitions — a failed or unavailable check blocks installation. A fun, specific fix: the ISO now uses a volume label that can't collide with AnduinOS boot-parameter names, closing a case where Rufus, writing in ISO mode, could alter boot arguments and strand users at an unexpected login screen.

The installation screen itself was rebuilt around a full presentation view with an Output button that shows live command logs — and installation failures now open that log view automatically instead of burying it. Other fixes read like a support-ticket greatest hits list: NVIDIA modules matched to the right kernel before first reboot, BitLocker partitions preserved in manual partitioning, boot images rebuilt only for installed kernels during recovery, and a 6 GiB minimum root size enforced so nobody installs onto a filesystem too small to use.

Why this release is worth noticing

Big distributions ship Rescue Centers as afterthoughts — a "recovery mode" GRUB entry and a wiki page. AnduinOS 2.0.4 treats recovery as a first-class feature with a GUI, safety snapshots, and documented limitations. For a small, donation-funded project aimed at Windows migrants, that prioritization is exactly right: the users most likely to need a rescue tool are the users least equipped to do the job with a terminal.

The broader lesson for anyone running an install: your recovery story is only as good as your honesty about its limits. AnduinOS wrote the limits into the release notes. More projects should.

Sources: AnduinOS 2.0.4 release notes (github.com/aiursoftweb/anduinos-docs, October 2026).