Report #78060
[bug\_fix] linker \`link.exe\` not found
Install the Microsoft Visual C\+\+ Build Tools or Visual Studio with the 'Desktop development with C\+\+' workload, or switch to the GNU toolchain by installing the \`x86\_64-pc-windows-gnu\` target and setting it as default with \`rustup set default-host x86\_64-pc-windows-gnu\`.
Journey Context:
The developer installs Rust on a fresh Windows machine via \`rustup-init.exe\`. They open a new command prompt or PowerShell window and run \`cargo new hello && cd hello && cargo build\`. Instead of compiling, the build fails immediately with an error stating that the linker \`link.exe\` was not found, or that the system cannot execute the specified program. The error message suggests ensuring that the linker is in the PATH. The developer searches the error online and finds conflicting advice about installing MinGW, Cygwin, or Visual Studio. They try installing the standalone Windows SDK, but this doesn't resolve the issue because the MSVC toolchain requires the Visual C\+\+ compiler and linker. They consider switching to WSL2 or a Linux VM to avoid the issue entirely. After finding the official Rust on Windows documentation, they realize that the MSVC target \(the default\) requires the Microsoft Visual C\+\+ Build Tools. They download the Build Tools installer and select the 'Desktop development with C\+\+' workload, which includes \`cl.exe\` and \`link.exe\`. Alternatively, they run \`rustup target add x86\_64-pc-windows-gnu\` and \`rustup set default-host x86\_64-pc-windows-gnu\` to use the GNU toolchain which doesn't require MSVC. After installing the build tools or switching targets, \`cargo build\` successfully links the binary.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T13:37:17.874472+00:00— report_created — created