The headline “recommend downgrading” reflects one user's April 2026 experience, not a current IceWhale recommendation. Marcio reported frequent freezes, poor remote access, and unreliable VPN behavior on ZimaOS 1.6.1. They then rebuilt the server from scratch using 1.5.4 and said the system became stable, remote access improved, and backups worked.
IceWhale did not dismiss the complaint. 777-Spider said the team understood that 1.6.0/1.6.1 had not met some users' expectations and that engineers were working through reported issues. The team also invited users to test a new remote-access solution. Current ZimaOS is now 1.7.1, so this article should preserve the historical regression experience without telling present-day users to move back to 1.5.4.
The Source User Reported Three Main 1.6.1 Problems
- system freezing that required server restarts;
- poor/unstable remote access;
- VPN client behavior that did not run smoothly.
The source does not contain crash dumps or a single root-cause diagnosis tying all three symptoms together.
The User Did Not Actually Perform an In-Place Downgrade
When another participant asked how to downgrade, Marcio clarified that they had been testing the system and simply rebuilt everything from scratch on 1.5.4. They kept only the Home Assistant workload they needed.
This distinction matters: the source validates a clean-install comparison, not a safe 1.6.1 → 1.5.4 rollback procedure that preserves apps and storage configuration.
The 1.5.4 Rebuild Was Stable for That User
Marcio said the 1.5.4 installation stopped the frequent freezes and connection loss they experienced on 1.6.1. Another user later said they also moved away from 1.6.1 after Immich problems.
These are community experiences, not proof that 1.5.4 was universally better on every hardware/software combination.
IceWhale Acknowledged the 1.6.0/1.6.1 Feedback
777-Spider wrote that 1.6.0/1.6.1 “may not have met the expectations of some users” and said the team was working quickly on reported issues.
That is a product-level acknowledgment of a difficult release period, but not a statement that everyone should downgrade.
IceWhale Was Already Testing a New Remote-Access Solution
IceWhale specifically responded to the remote-access complaint by inviting users to test a new connection solution that had performed better in internal/community testing.
This became part of the platform's continuing remote-access evolution rather than a permanent requirement to remain on 1.5.4.
Current ZimaOS Is 1.7.1
IceWhale now identifies ZimaOS 1.7.1 as the latest stable release. Its changelog focuses on security, stability, memory usage, backups, USB devices, RAID, app data, Docker startup/networking, WebUI port handling, YAML compatibility, and app migration.
See the current ZimaOS 1.7.1 stability fixes before deciding that a 2026 1.5.4 rebuild is still the right answer.
If a Current System Freezes, Diagnose the Current Failure
Do not assume a 1.7.1 freeze is “the old 1.6.1 bug.” Capture:
- hardware model and BIOS version;
- current ZimaOS version;
- previous-boot kernel/system logs;
- RAM/storage health;
- which app or network action preceded the freeze;
- whether the whole host, only WebUI, or only remote access stopped.
Rollback/Reinstall Is a Recovery Project, Not a Button Press
A version rollback can affect Docker apps, databases, storage metadata, newer settings, and feature compatibility. Back up user data, AppData, custom Compose definitions, and important storage metadata before reinstalling an older build.
The source itself avoided this complexity because the system was still a test deployment.
Do Not Stay on 1.5.4 Indefinitely for Historical Stability Alone
Older builds miss later security, storage, application, and remote-access fixes. A version that felt stable in April 2026 is not automatically safer in September 2026.
ZimaOS 1.6.1 Stability FAQ
Did Marcio perform a supported in-place downgrade?
No. They rebuilt the system from scratch on 1.5.4.
Did 1.5.4 work better for that user?
Yes. They reported better stability, remote access, and backups after the clean rebuild.
Should current ZimaOS users downgrade to 1.5.4?
Not based on this historical thread alone. Current users should reproduce the problem on the latest stable release and protect data before any rollback or reinstall.
