Kali Linux 32-Bit (i386): What to Run Instead

Kali stopped building 32-bit i386 images in late 2024 — 2024.3 was the last release with one, and the current 2026.2 comes as 64-bit x86 or ARM64 only. But before you go hunting for a 32-bit distro, run lscpu and read the CPU op-mode(s) line. If it says 32-bit, 64-bit, your processor is 64-bit and you can install the normal Kali image today — most people asking this question are in that group, running a 32-bit operating system on 64-bit hardware. If the line says 32-bit only, Kali really is not coming back for that machine, and the honest options are antiX, Debian 12, or using the laptop as a terminal into Kali running somewhere else.

Six laptops Jake nearly threw away

Jake took six trade-in laptops off a college at $25 each. Wipe them, put Kali on them, sell them to the students on the security course who keep asking for something cheap to practice on. A hundred and fifty dollars in, maybe six hundred back.

Then he lost a Saturday. Every machine ran a 32-bit copy of Windows, so he went looking for a 32-bit Kali download, found the announcement that they stopped making them, and read four pages of forum posts saying the same thing. By the evening he had written the lot off as scrap.

"They're 32-bit," he said. "Nobody makes 32-bit Kali. That's a hundred and fifty quid of firewood."

"Boot one off a live stick and run lscpu," Ethan said. "Before you write off anything."

Five of the six came back with CPU op-mode(s): 32-bit, 64-bit — 64-bit processors that had spent their working lives running a 32-bit operating system, because that is what the college imaged them with in 2013.

"So the laptops were never 32-bit. Only the Windows on them was."

"Correct. And you're not unusual for missing it — everything you read yesterday answered a question about Kali, when yours was about a processor."

That is this article in one paragraph. The 2024 announcement is settled and true. It is also, for most people who land on it, not what they needed to know.

Step 1: is your machine actually 32-bit?

Do this before anything else. It takes twenty seconds and decides which half of this article applies to you.

From any Linux, including a live USB

lscpu reads the processor's own description of itself. The line you want is CPU op-mode(s):

• 32-bit, 64-bit — 64-bit capable. Install the normal 64-bit Kali; the second half of this page is not for you.
• 32-bit alone — genuinely 32-bit hardware. Skip to the honest options.

Jake ran the second command too, got i686, and stopped. "That says 32-bit. Which is lying?"

"Neither," Ethan said. "They answer different questions, and uname -m is answering the one you didn't ask — it reports the kernel running right now, not what the chip can do. A 64-bit processor booted into a 32-bit system says i686 every time. That single line is where most people get their wrong answer, which is why I never quote it."

If lscpu is missing on some minimal system, the flags list works too:

lm is long mode, the name for 64-bit operation on x86. Flag present, the chip can do 64-bit; nothing printed, it cannot.

From Windows, before you wipe anything

Open Settings → System → About and read System type. This is the reliable route, because it names two separate things in one sentence:

Look at that middle row. Windows is telling you plainly that the operating system and the processor disagree, and that the processor is the more capable of the two. That row is why this article exists.

Do not use systeminfo at a command prompt for this. Its System Type field describes the Windows installation, not the chip, so on that middle row it reports an x86-based PC — the opposite of the truth. Our walkthrough on finding which bit version of Windows you are running covers that side properly.

The blunt version, if you cannot get in

Write the normal 64-bit Kali live image to a USB stick and try to boot it. If it reaches a desktop, the hardware is 64-bit and you are finished. Live mode writes nothing to the disk.

If it does not boot, keep two failure modes straight. A genuinely 32-bit processor usually refuses with a message about an unsupported CPU. A 64-bit processor behind 32-bit firmware acts as if the stick is not bootable at all and goes straight to Windows — the next section.

Once inside a running Kali, our guide to reading manufacturer, model and processor details from the terminal gets you the model number you will need when searching for driver support.

The rough date rule, and where it breaks

AMD shipped the first consumer 64-bit x86 chips in 2003, Intel followed on Pentium 4 parts in 2004, and Intel's Core 2 line from mid-2006 was 64-bit throughout. In practice an x86 machine built after roughly 2007 is almost certainly 64-bit capable. The exceptions are specific:

• Intel Core Solo and Core Duo, early 2006 — badly named, since the Core 2 chips months later were 64-bit.
• Pentium M laptops and the Celeron M parts beside them. Some lack PAE as well, which stops most modern 32-bit kernels booting at all.
• Early netbook Atom chips, the N270 and N280 generation of 2008 to 2010 — the classic genuinely-32-bit machines still in circulation.

The trap nobody documents: 64-bit CPU, 32-bit firmware

There is a whole class of hardware — cheap Windows tablets, small 2-in-1 convertibles, some mini PCs, mostly the Atom-based Bay Trail and Cherry Trail generation — where the processor is 64-bit but the manufacturer paid for 32-bit UEFI firmware.

UEFI is the software baked into the machine that runs before any operating system, and it is what goes looking for something to boot. A 32-bit UEFI can only load a 32-bit boot file; your 64-bit Kali stick contains a 64-bit one. The firmware looks, recognizes nothing, and quietly boots Windows instead — with no error at all. So an entirely 64-bit machine sends its owner hunting for a 32-bit ISO that would not have helped, because the 32-bit part is the firmware, not the processor and not the operating system.

The fix is to give the firmware something it can start. It scans removable media for EFI/BOOT/BOOTIA32.EFI, so a 32-bit build of GRUB placed there under that exact name gets picked up — and it then loads the ordinary 64-bit kernel from the same stick. One small file bridges the gap; everything above it is standard 64-bit Kali.

Two caveats. The file must be self-contained, because the firmware loads one binary and nothing else, so a stripped GRUB expecting a modules folder will stall. And you are on unsupported ground: when it fails, the answer lives in a forum thread about your specific model.

"So it's 64-bit, the processor's fine, and it won't boot because of a file name," Jake said.

"One file name, yes," Ethan said. "My honest opinion on those tablets: worth understanding, rarely worth attempting. Awkward wireless chipsets, sound that needs a hand-written config, a rotated display, 2 GB of soldered RAM. One evening on the bootloader, two more on everything else."

What "i386 dropped" does and does not mean

The vocabulary first, because four words get used for two things and that is half the confusion. i386 is Debian's name for the 32-bit x86 architecture, after Intel's 80386 chip of 1985. x86 casually means the same 32-bit family. amd64 and x86_64 are two names for one thing, the 64-bit extension AMD designed and Intel adopted — Debian calls it amd64 even on Intel chips, which surprises people. ARM64 is an unrelated family: Raspberry Pi, phones, Apple silicon.

Now the sequence, which explains why nobody was being difficult. Debian, which Kali is built from, stopped building a 32-bit kernel. From Linux 6.11 onward there was no i386 kernel for Kali to put in an image, and an image without a kernel is not an installer. So from the weekly builds at the end of October 2024, Kali stopped producing the i386 installer, live image and pre-built virtual machines. 2024.3 was the last release with them; 2024.4 the first without.

Fedora and Ubuntu had made the same call in 2019, and Debian went further afterwards: in Debian 13, i386 is no longer a regular architecture at all — no kernel, no installer, and it now requires SSE2 instructions many older 32-bit chips lack. The release notes say plainly that i386 users should not upgrade, and should reinstall as 64-bit or retire the hardware. That is why nothing is coming back.

What did not happen

This is the part that gets flattened into "Kali dropped 32-bit".

• The i386 packages stayed in the repository, deliberately, so 32-bit software keeps running on 64-bit installs. An ordinary supported scenario, not a workaround.
• i386 container images are still published. They run on a 64-bit host — a 32-bit userspace without a 32-bit machine.
• 32-bit Raspberry Pi builds are still made. Kali's current downloads list both 32-bit and 64-bit Pi images.

So "Kali has no 32-bit version" is not quite right. It has no 32-bit PC version: 32-bit software is alive and supported; 32-bit PCs are not.

Running 32-bit software inside 64-bit Kali

A separate question from ISOs, and one people conflate constantly. Your machine is 64-bit, your Kali is 64-bit, and you have a 32-bit binary to run — an old exploit, a vendor tool nobody recompiled, a challenge binary.

The first line tells the package system this machine will now consider 32-bit packages as well as 64-bit ones. Debian calls that multiarch; nothing is downloaded by it. apt update then has to run, because your package lists were fetched for one architecture and now need fetching for two — skip it and every install afterwards fails with a confusing message.

The symptom that sends people here is a binary refusing to run with No such file or directory even though the file is visibly right there. That is the loader saying the 32-bit interpreter is missing, not the shell complaining about your file. Installing libc6:i386 resolves it more often than not.

If apt complains about a half-configured package instead, repair that first — our post on the dpkg was interrupted error covers the recovery. One warning: adding i386 pulls a second copy of many libraries onto the disk. Add it when you need it, not preemptively.

Genuinely 32-bit hardware: the options, honestly ranked

You ran the check and the op-mode line said 32-bit, nothing else. Stated once: for truly 32-bit hardware in 2026, the answer is mostly not Kali. No clever workaround is being withheld.

Jake did not take that quietly. "I've a shelf of these in the back. They're landfill because a distro changed its mind?"

"They're not Kali machines," Ethan said. "That's a much smaller claim than landfill. And Kali didn't change its mind — Debian stopped building a 32-bit kernel, so there was nothing left to put in an image. Nobody is arguing that back into existence."

What exists instead, ranked properly:

Option 1: make the old machine a window onto Kali somewhere else

The best answer for most people asking, and almost nobody offers it. Kali does not have to run on the laptop in front of you. Put a light 32-bit Linux on the old machine, use it as a terminal, and run Kali on something 64-bit — a desktop in the corner, a virtual machine on a newer laptop, or a small cloud instance. Kali publishes cloud images for the major providers, and a modest instance costs single-digit dollars a month if you stop it when you are not using it. Current Kali, current kernel, full tool set, driven from the keyboard you already have.

What you lose matters too. Anything needing direct hardware access does not travel down an SSH connection — monitor-mode wireless, USB adapters, Bluetooth. And a remote box on somebody else's network is the wrong place to scan your own from. Excellent for studying tools and finishing a course; not the answer for wireless practice.

Option 2: buy the cheapest 64-bit thing that exists

Unromantic, often correct. A used small-form-factor office desktop from the mid-2010s costs very little and runs Kali better than any 32-bit machine ever did, and a current Raspberry Pi runs the official ARM64 build on almost no power. Jake's shop sees the arithmetic weekly: three evenings fighting an old netbook, or a $70 used mini PC working in an hour.

If the replacement is modest rather than fast, our guide to changing the desktop environment on Kali is worth reading — the default Xfce is already the light one, and staying on it is most of what makes an older machine usable.

Option 3: a light 32-bit distribution, for general use

If the point is keeping the laptop useful rather than running Kali, two choices are realistic.

antiX. antiX 26 arrived on 21 March 2026, built on Debian 13, and still ships a 32-bit edition when Debian itself no longer does. That build uses a legacy 5.10 kernel compiled without PAE, so it boots on the very old chips most modern 32-bit kernels reject — the Pentium M class above.

Debian 12. Security support moved to the long-term support team in July 2026 and runs to 30 June 2028, with i386 among the architectures covered. A defined horizon, in writing, about two years out. Do not upgrade it to Debian 13 — Debian's own release notes say not to.

"Which would you actually put on them?" Jake asked.

"antiX, without hesitating," Ethan said. "Debian 12 is the safer-sounding answer and it has a support date in writing, but that runs out in 2028, and antiX is the project that actually wants this hardware rather than putting up with it. If you're reselling those laptops, antiX is what I'd ship them with."

Now the honest part: neither is Kali. You can install a handful of well-known tools from Debian's repositories — a port scanner, a packet capture tool, a password cracker — and they work. What you cannot get is the curated set, the metapackages, and the tools Kali packages that Debian does not. And if somebody tells you to "just add the Kali repositories to Debian", do not: that produces a machine neither project will help you with.

Option 4: the archived 2024.3 i386 image, and why it is last

The old images are still downloadable and Kali documents where they live, so this looks like the obvious answer. It installs. It boots. It looks like a win for about a week. Then:

• The kernel is frozen. No i386 kernel is built any more, so the one that image shipped with is the last that machine will ever have. Every kernel vulnerability found since is permanent on it.
• Kali rolls; your install cannot. The repository moves continuously, and packages built against newer libraries stop resolving against what you have. It degrades rather than breaking cleanly.
• The tools go stale, and current tooling is the reason to run Kali at all — a late-2024 snapshot loses that reason quickly.
• It is the wrong thing to hand a learner — an unpatched kernel, pointed at hostile things.

One defensible use: an isolated, offline machine you want to poke at out of curiosity. That is just not "a Kali laptop".

Ethan is blunter. "Every hour you spend forcing Kali onto that netbook is an hour you're not learning anything. It's a waste of an evening dressed up as a project."

Option 5: make it the target instead of the attacker

The one people never think of, and for anybody learning security it may be the best value on this page. You do not need the old laptop to run the tools. You need something to point the tools at. A real machine on your own network that you are allowed to break teaches more than a stack of tutorials, and being obsolete makes it better at the job. Put an old operating system on it deliberately, leave services running, and practice against it from the 64-bit machine.

The 32-bit machine was never going to be the attacking machine. It can be an excellent target, a small file server, a machine for a child to learn on, or an honest trip to a recycling center — all better endings than three weekends forcing a 2009 netbook to run a 2026 security distribution.

If you already have a 32-bit Kali install running

Nothing was switched off. Your machine boots today exactly as it did in 2024 — worth saying, because the announcements read as though something was taken away from running systems.

What changed is slower. Your install is drifting, not being maintained. The kernel is final — none is built for i386 any more, so apt can update plenty of packages but never the kernel, security fixes included. Updates get patchier too: Kali rolls, the i386 side of the archive gets less attention as it moves, and dependency chains that used to resolve stop resolving. The usual sign is a dist-upgrade that wants to remove a long list of things to satisfy one package — when you see that, stop, do not confirm it. And upstream is unambiguous: Debian tells i386 users not to upgrade, and to reinstall as 64-bit or retire the hardware.

Back it up before anything else

Do this today, whatever you decide afterwards. The contents of a working install are the hard part to replace:

• The whole home folder, hidden files included — shell configuration, tool settings, SSH keys.
• /etc, or at least what you edited: network configuration, service files, anything changed at two in the morning.
• Custom wordlists, scripts, notes and engagement records — the irreplaceable category.
• A list of what you installed, so rebuilding is an afternoon rather than a fortnight.

Put it on an external drive, not another partition of the same disk. A drive from a decade ago is on borrowed time, and the machines arriving in Jake's shop for data recovery are overwhelmingly the ones somebody was keeping going "just a bit longer". A $30 external drive is cheaper than that conversation.

Then decide: freeze it, or move

Freeze it. If the machine does one job well, stop updating it and stop connecting it to anything that matters. An appliance on an isolated network segment is defensible. A half-updated machine on your main network is not.

Move. Migration means a fresh 64-bit install on different hardware with your files restored onto it, not an in-place conversion — there is no supported route from 32-bit to 64-bit. Our walkthrough of downloading and setting up a current Kali release covers the fresh install, and if you are unsure what the old machine thinks it is running, checking your Kali version properly answers that in one command. Then bringing Kali and Metasploit fully up to date is the first job on the new machine.

Questions people actually ask about this

Is Kali Linux still available in 32-bit?

Not for 32-bit PCs. Kali stopped building the i386 kernel and the i386 installer, live and virtual machine images in late 2024. The current release comes for 64-bit x86 and ARM64 only. The one surviving 32-bit build is for Raspberry Pi, a different processor family entirely.

How do I check if my computer is 32-bit or 64-bit?

On Linux run lscpu and read the line listing the CPU operating modes. If it shows both 32-bit and 64-bit, the processor is 64-bit capable and a normal 64-bit system will install. On Windows, Settings then System then About names the operating system and the processor separately.

My laptop runs a 32-bit OS. Does that mean the hardware is 32-bit?

No, and this is the most common misunderstanding behind the whole question. A 64-bit processor runs a 32-bit operating system perfectly well, and millions of machines shipped that way. Windows will say 32-bit operating system on an x64-based processor, which means the hardware is fine.

Which was the last Kali release with an i386 image?

Kali 2024.3 was the last release that shipped i386 images. The change took effect with the weekly builds at the end of October 2024 and with the 2024.4 release, so 2024.4 was the first without them. Those images are still archived, but installing one is a worse idea than it looks.

Can I still run 32-bit programs on 64-bit Kali?

Yes, and this is a separate question from whether a 32-bit image exists. Add i386 as a foreign architecture with dpkg, refresh your package lists, and you can install 32-bit libraries and run 32-bit binaries alongside everything else. Kali kept those packages in the repository for exactly this.

Why will the 64-bit Kali installer not boot on my tablet?

Because a class of cheap tablets and small 2-in-1 machines pairs a 64-bit processor with 32-bit firmware. The firmware can only start a 32-bit boot file, so it finds nothing it can load and moves on without an error. Add one to the stick and the kernel that loads is the ordinary 64-bit one.

What is the best Linux for a genuinely 32-bit laptop?

antiX is the strongest current choice: it still ships a 32-bit edition, it is deliberately light, and it targets old hardware rather than tolerating it. Debian 12 is the conservative alternative, with long term support to 2028 and i386 covered. Neither gives you Kali's tools.

Will my existing 32-bit Kali install keep working?

It keeps booting, and updates keep partly working for a while, but it is drifting rather than being maintained. No new kernel is built for it, so the kernel you have is the kernel you keep, security fixes included. Back up what you care about now and plan the move.

Should I download the old Kali 2024.3 i386 image?

Almost certainly not. It installs, it boots, and it looks like a win for about a week. Then Kali rolls forward while that machine cannot, so updates gradually stop fitting and the kernel never gets patched again. An unpatched kernel on a security distribution is the wrong thing to hand a learner.

Does Kali still build any 32-bit images at all?

Yes, but not for your PC. Kali still publishes 32-bit builds for Raspberry Pi hardware, which uses ARM processors rather than the Intel and AMD family, so an i386 laptop cannot use them. It also still publishes i386 container images, which run on a 64-bit host.

How much RAM does 64-bit Kali actually need?

For the default desktop install the documented floor is 2 GB of RAM and 20 GB of disk, and 4 GB is where it stops feeling like a compromise. A minimal setup with no desktop runs in far less, from around 128 MB with 512 MB recommended.

Can I run 64-bit Kali in a virtual machine on a 32-bit PC?

No. A virtual machine cannot invent processor features the physical chip does not have, so a 64-bit guest needs a 64-bit host processor underneath it. If your host is genuinely 32-bit only, no virtualization software will give you 64-bit Kali.

Why did Kali drop i386 in the first place?

Because the layer underneath moved first. Kali is built on Debian, Debian stopped building a 32-bit kernel, and from kernel 6.11 onward there was no i386 kernel to put in an image. Fedora and Ubuntu had made the same move years earlier.

What can I do with an old 32-bit laptop instead?

If you are learning security, make it the target rather than the attacker. A real machine on your own network that you are allowed to break teaches more than any tutorial, and being obsolete makes it better at the job. Failing that, a light 32-bit distribution keeps it useful.

Does the uname command tell me if my CPU is 64-bit?

No, and trusting it here sends people down the wrong path. It reports the architecture of the kernel currently running, not the capability of the chip. A 64-bit processor running a 32-bit system reports a 32-bit answer, which is not a verdict on the hardware.

What happened to the six laptops

Five took the standard 64-bit Kali image without argument. Two needed an extra stick of RAM. They sold.

The sixth was a 2009 netbook with an Atom N270 — genuinely 32-bit, no way around it. It did not become firewood either. It sits behind the counter running an old operating system on purpose, and the students who buy the other laptops get to scan it and break into it while they are standing there. It is the most useful of the six and it cost the least.

"So the thing I couldn't install Kali on turned out to be the demo machine."

"It was never going to be the attacking machine. It's a very good thing to attack."

"And I nearly binned a hundred and fifty quid of stock because I read uname -m instead of lscpu."

"You read the operating system when you meant to read the processor. It's the most expensive twenty seconds people don't spend."

The Kali announcement is settled — there is no 32-bit PC image and there will not be one. But the question underneath it, what is this machine actually capable of, has an answer you can get in one command, and it is often a different answer from the one people assume. Run it before you decide anything, including whether to throw the thing away.

Revision note. Originally published in November 2024, reporting the announcement on the day it landed — that Kali would stop building i386 kernels and images from 2024.4 onward. Rewritten on 9 August 2026. That announcement held: 2024.3 was the last release with i386 images, and Kali 2026.2 ships for 64-bit x86 and ARM64 only. What changed is which part of it is useful. Two years on, almost nobody arriving here wants the news — they are holding an old laptop and want to know what to install on it tonight. So this version leads with the check that decides the question, and gives the genuinely 32-bit reader a ranked set of options instead of a workaround that does not exist. We kept the vocabulary, because x86, i386, amd64 and ARM64 really do confuse people, and added the boot problem that looks like an architecture problem and is not. If your machine does something this page does not cover, do write in through the contact page and tell us what you saw — odd hardware is exactly what improves a page like this, and we would genuinely like to hear about it.