ZimaOS 1.5.4 Makes Encrypted Folders a Beta Feature
ZimaOS 1.5.4 introduces encrypted folders, but the release announcement explicitly labels the feature as Beta. The ZimaOS team advises users to back up their data before relying on it. That warning matters more than the feature label: an encrypted folder should not be the only copy of important files, especially while the implementation is still being tested.
The creation control is available from the new-folder flow in Files. A team reply illustrated where the “New encryption folder” option should appear. One user could see it in Chrome but not Firefox until clearing Firefox cookies and cache, so an absent menu on an upgraded system can be a stale-browser-state problem rather than proof that the feature failed to install.
After clearing browser data, reopen Files and repeat the same new-folder action. Recovery is confirmed only when the encrypted-folder option appears and a test folder can be created and reopened after signing out and restarting the browser.
SMB and Storage Management Received New Controls
The release adds the ability to stop an SMB share while keeping the stopped share in the management list. It also fixes a case where canceling a share on one folder unintentionally canceled shares on subfolders, and it allows Files to connect to Samba shares through IPv6 addresses and domain names.
A Storage button now appears in the Files sidebar, and the storage-management page was redesigned. RAID repair and expansion disk selection, uppercase BTRFS database records, and unnecessary extra partitions on USB system disks are among the storage issues listed as fixed.
A later reply described an older QNAP that stopped connecting after the update while Synology shares remained available. The user enabled SMB 3 on the QNAP and confirmed recovery. This is a device-specific community result, not evidence that every post-update SMB failure has the same cause.
The Release Includes Security, Files, Backup, and Network Fixes
The official fixed list includes an authentication bypass involving system-level username handling and an open redirect in the login page. It also covers network parsing when one NIC has multiple logical names and member usernames containing a specific character sequence.
Files can now download names containing commas and preview additional HEIC files. The previous 10,000-file browsing limit was removed, while backup error messages and handling for directories containing socket or pipe files were improved.
Recycle Bin behavior was corrected for a full system disk and for BTRFS space reclamation. These entries describe the team's release scope; they do not replace a backup or a version-specific reproduction test for a system that still shows the old behavior.
Choose the Correct Update Path and Verify the Result
Systems on ZimaOS 1.4.1 or later can normally use the red update indicator on the dashboard. The topic also provides a ZimaOS 1.5.4 installer image for a first installation.
For a manual upgrade, the announcement links the ZimaOS 1.5.4 RAUCB update package. One user on 1.5.3 did not see the dashboard update and reported that the manual path worked.
After updating, verify the displayed version, open Files and Storage, inspect existing shares, and test one normal file operation. If encrypted folders are part of the goal, use noncritical data first and keep a separate readable backup.
FAQ
Why is the encrypted-folder option missing after updating?
In one confirmed case, Firefox retained stale site data. Clearing cookies and cache made the option appear. This does not rule out other causes, but it is a reversible first check.
Are encrypted folders production-ready in ZimaOS 1.5.4?
The release calls them Beta and asks users to back up data before use. Treat encryption and backup as separate controls.
Does ZimaOS 1.5.4 require SMB 3?
The release does not state a universal SMB 3 requirement. One older QNAP connection recovered after SMB 3 was enabled, while other shares continued working.
