An Intel NUC 10 that appears to freeze during ZimaOS installation should be diagnosed as a compatibility/boot-path problem before assuming the installer is corrupt. In the April–May 2026 forum case, disabling Secure Boot allowed the installer to start, ZimaOS 1.5.4 progressed farther than the newer build the user had tried, and the final setup completed after the user switched to wired Ethernet and assigned a stable address.
That does not make 1.5.4 the right version to install now. The current release is much newer, so the old downgrade is best treated as evidence that installer/kernel compatibility can vary by hardware generation.
What the Original NUC 10 Thread Actually Verified
The installer repeatedly stopped after early Linux startup messages. The user had already tested several USB sticks, USB ports, HDMI/USB-C display paths, AHCI mode, disabled Secure Boot, and even disabled Turbo Boost. The thread therefore moved beyond the usual “bad flash drive” explanation.
After trying the older 1.5.4 build, the installer completed far enough to reach network setup. The user then moved from Wi-Fi to Ethernet and later reported the system was alive and stable enough to set a static IP.
Use the Current Installer First
The current ZimaOS installation guide remains the primary source. Use UEFI mode, keep Secure Boot disabled, prefer AHCI when the platform exposes RAID/RST versus AHCI, and flash the current installer cleanly before experimenting with historical builds.
The installation troubleshooting guide is especially relevant because it already treats Intel NUC compatibility as model-specific rather than universal.
Separate Boot Compatibility From Network Discovery
The thread had two different failures: first the installer appeared to hang; later the install finished but stalled while trying to obtain a network address over Wi-Fi. Do not combine those into one diagnosis.
If the installer finishes, connect Ethernet directly to a router or switch, confirm link lights, and check whether DHCP assigned an address. A static reservation on the router is useful after the device is visible; it is not a substitute for solving a missing driver or no-link condition.
When an Older Build Is Still Useful for Diagnosis
If the current installer consistently stops at the same point on one third-party machine while an older release boots, that comparison can help demonstrate a kernel or driver regression. It should be a diagnostic test, not the long-term production plan.
Record the exact NUC model, storage controller, NIC model, current ZimaOS version, and the last visible boot line before reporting the issue. That evidence is more useful than “NUC 10 does not work.”
Bottom Line
The original NUC 10 case was eventually made to work, but no single step was proven as a universal fix. Start with the current installer, UEFI/Secure Boot/AHCI checks and wired Ethernet. Use an older build only to isolate a possible compatibility regression, then return to a supported current release once the hardware path is understood.
