What changed
On October 2, 2026, Rust's compiler team announced that Rust 1.100 will demote i686-pc-windows-msvc from Tier 1 with host tools to Tier 1 without host tools, and i686-pc-windows-gnu from Tier 2 with host tools to Tier 2 without host tools. The project will continue distributing standard libraries for these targets, but not native compiler/host-tool binaries for 32-bit Windows machines. To produce 32-bit Windows programs after the change, builders must cross-compile from a supported host such as 64-bit Windows.
Why it matters
This affects a small but real set of legacy build machines, CI workers and vendors maintaining 32-bit Windows binaries. A pipeline that builds 32-bit executables from a modern 64-bit host can continue, while a workflow that installs rustup and runs rustc natively on 32-bit Windows will stop working with Rust 1.100. The distinction matters because the announcement does not say 32-bit Windows binaries are no longer supported. It shifts where compilation can happen, reflecting the maintenance and resource costs of old host toolchains.
Two target triples lose host tools
The change applies to i686-pc-windows-msvc and i686-pc-windows-gnu. Their standard-library targets remain available; the project stops shipping host tools for those 32-bit Windows environments. The MSVC target continues Tier 1 CI testing without host tools.
Cross-compilation remains the migration path
Developers producing 32-bit Windows executables should move builds onto supported 64-bit hosts and target the i686 Windows triples. Audit CI runners, artifact packaging and any scripts that assume rustup can install a native 32-bit Windows compiler.
Why the compiler team is withdrawing support
The Rust team says 32-bit-only Windows development machines are now exceptionally old, and toolchain builds have suffered compiler crashes and out-of-memory failures. It considers cross-compilation a more sustainable route than maintaining native 32-bit compiler distributions.
The announcement is about host toolchains, not runtime execution
A 32-bit binary produced by cross-compilation can still target the supported standard library. Application runtime compatibility remains a separate matter to test on the Windows versions your users actually run.