If ZimaClient says “Device connection not ready” while the ZimaOS Web UI still works, treat it first as a client/connectivity-layer problem rather than a NAS outage. In this 2025 case, ZimaOS 1.4.1 was reachable in the browser and ZeroTier could also reach the device manually.
The thread never proved that ZimaOS 1.4.1 itself was the sole cause. The user had also moved from Windows 10 to Windows 11 without reinstalling ZimaClient 2.1.0, and IceWhale’s next troubleshooting step was to reinstall the client.
What the Source Case Ruled Out
Because the ZimaCube remained reachable through its normal browser interface, storage, boot and basic LAN availability were still intact. The failure appeared specifically when the desktop client initialized its connection path.
The user also reported that manual ZeroTier connectivity worked, which further narrowed the problem to ZimaClient state, integration or the Windows upgrade environment.
Use the Current ZimaClient Before Debugging an Old Build
The current ZimaClient installation guide documents manual ZeroTier installation as a troubleshooting path and provides current Windows/macOS log locations.
Do not keep reinstalling the historical 2.1.0 build just because it was mentioned in this thread.
Reinstall After a Major Windows Upgrade
When a desktop app includes networking helpers and background services, an in-place Windows upgrade can leave stale drivers, services or permissions. Uninstall ZimaClient, reboot if requested, install the current build, and test before making router or NAS changes.
The ZimaClient troubleshooting guide covers the same client-side layers in more detail.
Collect Logs Before Changing Multiple Things
If the current client still fails, capture the error and preserve logs from %AppData%\Zima\logs on Windows before another reinstall. Record Windows version, ZimaClient version, ZimaOS version, and whether direct browser access works.
The ZimaClient connectivity overview helps distinguish local discovery from remote-access behavior.
Bottom Line
The original thread does not support the simple conclusion “ZimaOS 1.4.1 broke ZimaClient.” Browser access and manual ZeroTier still worked, while Windows had also been upgraded. On a current system, reinstall the latest ZimaClient, verify ZeroTier, then use logs to isolate the desktop-client layer.
