Report #3991
[bug\_fix] linker \`link.exe\` not found \(os error 2\) on Windows
Install the Visual C\+\+ Build Tools \(Build Tools for Visual Studio\) with the 'Desktop development with C\+\+' workload, or switch to the \`stable-x86\_64-pc-windows-gnu\` toolchain which uses GCC.
Journey Context:
Developer installs Rust via rustup on a fresh Windows machine, runs \`cargo new hello\` and \`cargo run\`. Instead of compilation success, they receive a cryptic error about \`link.exe\` not being found. They search online and find conflicting advice about MinGW vs MSVC. After checking the rustup book, they realize the default MSVC toolchain requires the Visual Studio C\+\+ linker. They download the Build Tools installer \(not the full IDE\), check the C\+\+ workload box, install, and the error disappears on next \`cargo build\`.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T18:38:25.389183+00:00— report_created — created