Demoting i686 Windows targets to std-only

Rust 1.100.0 stops distributing host compilers for 32-bit Windows. Standard libraries remain available; developers must cross-compile from a supported host.

An Intel Pentium Pro processor in its motherboard socket.
Archive photograph, 6 December 2019: a Pentium Pro, an early i686-family processor. Illustrates the architecture discussed in Rust’s Windows target change; not a photograph of the release. Resized and converted to WebP; full frame retained. Capitalistcakes · CC0

What changes

Rust’s compiler team announced that version 1.100.0 will remove host-tool distributions for both 32-bit Windows targets. The MSVC target remains Tier 1 and the GNU target remains Tier 2; their standard-library builds will still be distributed. The MSVC target also retains CI testing.

What remains possible

The change concerns machines running the compiler, rather than eliminating 32-bit Windows applications. Developers can continue producing those binaries by cross-compiling from a supported host toolchain, including a 64-bit Windows host. Other 32-bit platforms are outside the scope of this announcement.

Why builders should check their build hosts

A workflow that installs the compiler directly on 32-bit Windows needs a supported build host for the affected release. The team describes reliability and memory problems encountered while building those toolchains. Its recommendation is to move compilation to a better-supported host while retaining the 32-bit application target.

Sources

[Compiler-team announcement](https://blog.rust-lang.org/2026/10/02/demoting-i686-windows-targets-to-std-only/).

Rust Blog