Rust 1.100.0 demotes 32-bit Windows targets to std-only

The Rust compiler team has confirmed that Rust 1.100.0 will demote both 32-bit Windows targets, ending the era of building the compiler itself on a 32-bit Windows host. The change was announced on the Rust Blog on 2 October 2026 by Mateusz Mikuła and Ralf Jung on behalf of the compiler team.

What changes in 1.100.0

The i686-pc-windows-msvc target drops from Tier 1 with host tools to Tier 1 without host tools, and i686-pc-windows-gnu drops from Tier 2 with host tools to Tier 2 without host tools. In plain terms, the prebuilt standard library will still be published, but the compiler and the other host tools will not.

After Rust 1.100 it will no longer be possible to install a Rust toolchain on a 32-bit Windows host. Anyone who still needs 32-bit Windows binaries will have to cross-compile them from a supported 64-bit toolchain, which is the workflow the team now recommends. Other 32-bit platforms are unaffected.

Why the project is doing it

The team's reasoning is blunt: desktop and server x86 CPUs that only do 32-bit have not been sold for more than 15 years, and general 32-bit Windows support ended in October 2025. The platforms these targets exist for barely exist, and where they do, they are not usually capable development machines.

There is a maintenance problem too. Building i686 Windows toolchains on modern x86_64 hardware has proved unreliable, with compiler binaries crashing when built with the i686 MSVC target and the GNU C++ toolchain running out of memory during LLVM builds. Cross-compiling from a better supported target is the team's answer.

The i686-pc-windows-msvc target will still be tested in CI as a Tier 1 target for now, and the demotions are documented in RFC 3999 and MCP 1020.

Our opinion

Target demotions are the unglamorous housekeeping that keeps a language trustworthy, and this one is long overdue. A target is a promise, and promising to build a modern compiler on hardware nobody has manufactured since before the first iPhone is a promise that quietly costs maintainers hours every month. Rust's tier system exists precisely so the project can retire old platforms in public instead of letting them rot. What makes this a good example is the timing: the standard library keeps shipping, CI keeps testing the MSVC target, and cross-compilation is a well-trodden path. Anyone still building on a genuinely 32-bit Windows box is already running an operating system its own vendor stopped patching a year ago. The bigger signal is what it says about Rust's centre of gravity, which is now firmly the 64-bit machine you are almost certainly reading this on.