An Intel NUC10i7FNK2 user completed the ZimaOS installer successfully, removed the USB drive, and then saw the machine power off while ZimaOS started from slot A. The useful clue was that an Ubuntu live environment also shut the same NUC down, while the same ZimaOS installer worked on an older Lenovo ThinkCentre.
The thread was ultimately resolved by changing one BIOS setting: Intel Turbo Boost Technology was disabled. That fixed this particular NUC. This should be treated as a hardware/firmware-specific case rather than a universal ZimaOS installation requirement.
What the Thread Already Ruled Out
The user had already updated the NUC BIOS, restored BIOS defaults, disabled Secure Boot, enabled UEFI, used AHCI mode, enabled virtualization, recreated the boot media with Balena Etcher, tried multiple USB drives and ports, and tested several ZimaOS stable builds.
The strongest diagnostic detail was cross-OS behavior: Ubuntu also powered off during initial loading. That makes a ZimaOS-only software fault less likely and shifts attention toward firmware, processor power behavior, thermals, or another platform-level interaction.
The Setting That Fixed This NUC
The original poster reported that the shutdown stopped after disabling Intel Turbo Boost Technology under the BIOS Performance → Processor settings.
Do not treat this as the first setting to change on every x86 system. Turbo Boost normally works on supported hardware. It is better understood as a targeted troubleshooting test when the machine powers off during Linux boot and the same symptom appears with more than one Linux-based environment.
How to Troubleshoot a Similar Boot Shutdown
- Confirm the installation image and USB media by testing them on another supported x86 machine when possible.
- Update the BIOS or firmware and load sane defaults before adding custom tuning.
- Verify UEFI, storage mode, and boot-device settings against the current ZimaOS install steps.
- Test another Linux live environment. If it also powers off, investigate the hardware platform rather than repeatedly reinstalling ZimaOS.
- Only then test processor performance settings such as Turbo Boost one at a time and document what changes the behavior.
Current Firmware and Installation Context
The thread is most useful when read as a process of elimination. The current ZimaOS installation troubleshooting covers USB media, UEFI, Secure Boot, storage mode, boot order, and third-party x86 compatibility, while the broader ZimaOS installation guide separates clean installation from later upgrade problems. If you are repurposing non-Zima hardware, the old laptop home server also shows why firmware preparation should be checked before repeatedly rewriting the installer.
Intel's Intel Turbo Boost behavior explains that Turbo Boost raises frequency only while the processor stays within power, current, and temperature limits. That supports treating the successful BIOS change in this NUC case as a platform-specific power/firmware clue, not proof that Turbo Boost is generally incompatible with ZimaOS. The Ubuntu bootable USB workflow also explains why a live Ubuntu environment is useful as a cross-check: it can boot and test Linux without altering the installed system.
Bottom Line
In this community case, ZimaOS was not failing because the installer was corrupt. The Intel NUC also shut down with Ubuntu, and disabling Intel Turbo Boost stopped the unexpected power-off. That makes the result useful as a BIOS troubleshooting lead, not as a general ZimaOS configuration rule.
