A ZimaOS installer that reaches the install screen but either stalls near completion or produces a disk the BIOS will not boot can involve more than one failure mode. This April 2025 thread combined an NVMe install that stopped around 95% with a SATA installation that completed but did not appear as a bootable device.
Start with the Official Firmware Requirements
Zima-Jerry gave two baseline requirements for installing and booting ZimaOS on a laptop: use UEFI boot mode and disable Secure Boot. Zima-Giorgio later added that the SATA controller should be in AHCI mode.
Those requirements still match the current installation flow. Before changing disks or rewriting images repeatedly, verify the current ZimaOS boot prerequisites on the target machine.
Separate an Installation Failure from a Boot-Entry Failure
The NVMe disk in the original report stalled during installation, while the SATA disk completed installation but was not recognized by the BIOS as bootable. Those are not the same problem.
- If installation does not finish, investigate the target device, installer media, storage mode, and drive geometry.
- If installation finishes but BIOS shows no boot target, focus on UEFI boot detection and firmware configuration.
One Community NVMe Case Was Caused by 4096-Byte Logical Blocks
A community participant reported that they had changed an NVMe drive's logical block address size from 512 bytes to 4096 bytes. Their ZimaOS image deployment failed until they changed the drive back to 512-byte logical blocks.
That result is valuable but model-specific. IceWhale asked for more detail and did not publish a universal statement that every 4Kn NVMe device is unsupported. Treat it as a diagnostic clue when a known-good NVMe behaves differently from SATA, not as a command to reformat every NVMe device.
A Different NVMe Worked for Another User
Another participant tried several older drives on a 10th-generation Intel platform and eventually completed installation quickly on a newer Kioxia NVMe. They suspected an old-hardware or installer-driver interaction, but the thread did not establish a specific driver defect.
ZimaOS Boot Failure FAQ
Which BIOS settings did IceWhale explicitly recommend?
UEFI boot, Secure Boot disabled, and AHCI for the SATA controller.
Does a 95% install stall prove the SSD is bad?
No. The thread contains examples involving logical block size and different drive behavior, not a confirmed single cause.
Can 4096-byte logical sectors cause trouble?
One community user said switching their NVMe from 4096-byte logical blocks back to 512 resolved image deployment. IceWhale did not publish that as a universal compatibility rule.
Was the original thread fully solved?
No. It collected several useful boot and storage clues without publishing one confirmed root cause for the original laptop.
