I have been writing Clonezilla (a free disk imaging tool that runs from a USB stick and copies whole partitions byte for byte) images to flash drives since the 2.x line. New versions of Clonezilla tend to land without anybody outside the recovery community noticing, because the tool only matters the day something breaks. That is the audience for 3.3.3-37 too. It is not a flashy release, and there is no headline feature to pitch. What it does, quietly, is fix several recurring failure modes that have been costing real people real evenings for a couple of years. If any of those failure modes match yours, the upgrade is worth doing now.
The rest of this article walks through what changed, who actually benefits, and which scenarios justify an immediate install.
The new kernel is the part most laptops were waiting for
Clonezilla typically ships with the newest LTS Linux kernel in the base image, and 3.3.3-37 jumped from 7.0 to 7.1. That headline matters because the live image needs to recognize your hardware before it can do anything useful. Anyone who has plugged a current year laptop into a Clonezilla stick and watched the screen refuse to see the internal drive already understands why this is not trivial. 7.1 adds broader support for newer Wi-Fi chipsets, current NVMe (Non Volatile Memory Express, the PCIe based SSD interface) controllers, and the GPU generations that ship after 2024, so the early boot console actually shows readable text instead of disappearing off the top of the screen.
Underneath the kernel, the project also refreshed the Debian Sid base to mid September 2026. That pulls in current fixes for every shell-out utility Clonezilla invokes during a restore. The base refresh does not get a headline, but it is the half of a maintenance release that decides whether the tool boots at all on oddball hardware.
The Lite Server fix is the one IT folks should care about
Clonezilla Lite Server is the build that broadcasts a boot image over the network and lets a sysadmin push the same saved image to dozens of machines at once. Most of the time that means PXE (Preboot Execution Environment, the standard for booting a machine over the network using DHCP and TFTP) or HTTPBoot (the same idea, but serving the bootloader over plain HTTP), and the choice was largely forced by whatever your switch room and firmware happened to support.
This release finally treats them as one workflow rather than two parallel ones. Secure Boot (the firmware setting that refuses to load unsigned bootloaders) over HTTPBoot also works now, which means a fleet with locked down firmware no longer forces you to either flip everything to legacy mode or hand sign a bootloader per site. For a home user with one laptop that section is irrelevant. For anyone re-imaging a classroom, a repair bench, or a small business, it removes hours of fiddling every time a build changes.
One specific error string is gone
There is a single error that has been showing up in forum threads for years whenever someone tries to restore a Clonezilla image on a Secure Boot laptop. The boot menu appears, the restore starts writing, then EFI text mode handoff runs into a policy check and refuses to continue. Most people hit this once, give up, and reinstall the OS by hand rather than debug it at 11 PM.
3.3.3-37 patches the underlying case. The tool now runs efitextmode conditionally under Secure Boot lockdown so the boot menu no longer trips the policy check at the worst possible moment. It is a one line changelog entry that is going to save a real number of evenings.
Smaller items that mostly remove old workarounds
The rest of the release is a long list of small things, and most of them are the kind of thing that used to require a separate fix file kept on a sticky note. Grouped by what they actually change for a person running the tool:
- Boot speed. The live image now reaches the prompt a bit sooner, and the HiDPI menu text actually scales, because GRUB ships both a preferred and a fallback resolution that HiDPI displays honor.
- Font handling. CJK locales get a new
--font-sizeargument forfbterm, so large fonts scale instead of overflowing the screen. Thenetpbmandfonts-unifontpackages are also bundled. - Identical disk restores. When you restore to the exact same model disk you cloned from, the conversion step now skips. Same model in, same model out, restore finishes faster.
- Time sync.
ocs-live-time-syncreads the boot parameters and prompts when the hardware clock is set to local time, instead of silently writing the wrong value into the restored image. - Networking. The deprecated
net-toolssuite is replaced byiproute2, anddhclientgives way todhcpcdconfigured with a stableclientid, so DHCP reservations survive reboots. - QCOW2 conversion.
cnvt-ocsimg-qcow2was refactored with two packaging modes, more flexible naming, and a fix for the VHD boot kernel panic that occasionally broke round trips.
None of those are exciting on their own. Together, they remove a stack of “yeah we know about that” workarounds that used to live in every consultant’s notes folder.
What the tool supports, for context
The current Clonezilla release handles EXT2, EXT3, EXT4, ReiserFS, XFS, JFS, FAT, NTFS, HFS+, UFS, minix, and VMFS. LVM2 (Logical Volume Manager, the Linux subsystem that pools physical disks into a single logical volume group) volumes work, multicast push works, and the live image boots on both 32-bit x86 and 64-bit x86_64 hosts. That covers imaging Linux, macOS, and Windows machines from the same USB stick. LUKS2 (the newer Linux disk encryption standard) repository targets work too, which matters if your backup pool is encrypted at rest.
How to actually update
Grab the ISO or USB image from the project site, then write it to a stick the same way you wrote the old one, whether that is dd, Etcher, or your tool of choice. The full changelog lives on the project page if you want to read every commit instead of trusting me.
Trade-offs
A maintenance release still costs you a Saturday. You have to write the new image to a stick, boot every machine you care about once to confirm it still sees your hardware, and update any PXE environment that points at the older ISO. If you maintain a hand patched fork or a custom initramfs (the small initial filesystem Linux loads into RAM before the real root filesystem is mounted), read the changelog carefully before you upgrade, because the kernel jump from 7.0 to 7.1 will surface any out of tree patches you were carrying.
If your current setup works and you are not hitting any of the failure modes above, there is no urgent reason to reinstall tonight. If, on the other hand, you have lost hours to Secure Boot restore errors, fought with menu text on a HiDPI screen, or struggled to PXE boot a fleet onto recent laptops, this is the release that makes those workflows boring. Boring is what you want from a backup tool. The next time a drive dies at the worst possible moment, you will be glad you updated.