Users on ZimaOS 1.4.2-beta2 reported that App Store installations and ZVM operating-system images remained at 0 percent and eventually failed. The problem affected Wi-Fi and wired systems in multiple countries, so the thread did not reduce it to one router or ISP.
Different actions produced different results: one user recovered after a complete shutdown and cold boot; changing ISP did not help two others; restarting the app-management service moved one install to 25 percent but did not finish; and at least one participant confirmed that direct image download worked.
Confirm What Is Actually Failing
- Can ZimaOS reach websites and remote access normally?
- Do existing apps update while new apps fail to install?
- Do both App Store images and ZVM ISO files stall?
- Does the progress remain at 0 percent or advance before failure?
- Does a direct official test file download succeed?
In the source, one participant could update existing apps but could not install new ones. That suggests the failure can occur after basic internet connectivity is already working.
Start With the Low-Risk Checks
- Record the ZimaOS release and whether it is stable or beta.
- Perform a full shutdown and cold boot, not only a browser refresh.
- Check date, time, DNS, free system space, and network connectivity.
- Temporarily test wired Ethernet and a second network only to isolate routing.
- Capture the installation error and service logs before repeated retries.
The thread included wired, Wi-Fi, India, and Italy reports. A second ISP and phone hotspot did not fix the original poster's system, so do not keep changing networks after the evidence points elsewhere.
Historical Official Service Restart
An IceWhale team member supplied the following for users familiar with the CLI on ZimaOS 1.4.2-beta2:
sudo -i
systemctl restart zimaos-app-managementOpen the web terminal through Settings > General > Developer mode, then authenticate with your own credentials. This restart does not delete AppData, but it interrupts app-management operations. In the thread it changed one user's progress from 0 to 25 percent without completing the install, so it was diagnostic rather than a universal fix.
Direct ISO Links Were a Network Diagnostic
IceWhale later provided temporary or version-specific Windows and Linux ISO URLs to test whether the files were reachable outside the ZVM interface. At least one participant said this worked. Those 2025 image URLs and OS versions should not be treated as current recommended downloads.
For current ZimaOS media and releases, use the official ZimaOS releases page. For guest operating systems, use the vendor's current download and licensing terms.
This Was a Beta-Release Incident
The affected build was 1.4.2-beta2, and IceWhale said that release included app-installation experience and stability changes. Do not assume the same service behavior on a current release. Update through the supported channel after backing up important data and application configuration.
What to Include in a Support Report
- ZimaOS version and hardware model;
- country, ISP, wired/Wi-Fi, VPN, firewall, and DNS;
- free system storage;
- the exact app or ISO and timestamp;
- whether existing app updates work;
- screen recording and app-management logs;
- results of cold boot, alternate network, and direct-download tests.
Stuck App and VM Download FAQ
Did a reboot help anyone?
Yes. One wired user reported recovery after a complete shutdown and fresh boot.
Did restarting app management fix everyone?
No. One user's install advanced to 25 percent and then stalled.
Should I reuse the old ISO links?
No. They were historical diagnostics containing old OS versions; use current vendor sources.
