Install Rust on Windows: rustup, Cargo, VS Code, and Common Fixes

Install Rust on Windows with rustup, set up VS Code with rust-analyzer, choose MSVC vs GNU toolchain, and fix the most common Windows-specific errors.

Ekin Yalgın

April 18, 2026·4 min read

Install Rust on Windows: rustup, Cargo, VS Code, and Common Fixes

The 'link.exe not found' error is the exact moment most developers realize installing Rust on Windows requires more than just running a single executable. Skipping the C++ Build Tools or ignoring Windows Defender exclusions will severely bottleneck your compile times. Optimizing your environment from day one saves countless hours of debugging later.

Core Toolchain: MSVC (default and highly recommended) Required Dependency: Desktop development with C++ (Visual Studio Build Tools) Default Install Path: %USERPROFILE%\.cargo\bin Critical Performance Step: Exclude the .cargo folder from Windows Defender

The Critical Choice Before Installing Rust: MSVC vs GNU

Selecting the right toolchain defines your entire development experience. MSVC offers the best interoperability with native Windows APIs and libraries. It requires the Visual Studio Build Tools but guarantees seamless integration with the OS ecosystem.

The GNU toolchain relies on MinGW. You only need GNU if your project specifically demands legacy C dependencies that refuse to compile under MSVC. Stick to MSVC for a friction-free Windows environment.

How to Install Rust on Windows Step by Step

Step 1: Install Visual Studio Build Tools (C++ Workload)

Rust needs a C++ linker to compile your code into an executable. Download the Build Tools directly from Microsoft. Run the installer and select the Desktop development with C++ workload.

This step is non-negotiable for the MSVC toolchain. Failing to check this exact workload triggers the notorious linker errors during your first build attempt.

Step 2: Download Core Components with rustup-init

Head to rustup.rs and grab the rustup-init.exe file. Running this executable opens a command prompt interface. Press 1 to proceed with the default installation.

This process automatically fetches rustc, cargo, and the standard library into your %USERPROFILE%\.cargo\bin directory.

Step 3: The PATH Variable and the Terminal Restart Rule

The installation script modifies your system PATH automatically. You cannot use the Rust compiler in any currently open terminal windows. Close your command prompt or PowerShell completely.

Open a fresh terminal session and type the verification commands.

rustc --version
cargo --version

This simple restart prevents the frustrating 'rustc is not recognized' silent failure that trips up most first-time installers.

Alternative for Non-Admin Users: Scoop and Winget

Corporate laptops often restrict administrator privileges. You can bypass the standard installer using package managers. Open PowerShell and run the winget approach for a native Windows installation.

winget install Rustlang.Rustup

Scoop provides an even cleaner user-space installation that handles the PATH configuration without triggering UAC prompts.

scoop install rustup

VS Code and rust-analyzer Configuration

Visual Studio Code paired with the rust-analyzer extension creates the optimal Rust IDE. Install the extension directly from the VS Code marketplace.

Open your workspace settings and change the Check Command to clippy. This forces the analyzer to run Rust's official linter on every save. You catch unidiomatic code before you even run a build.

{
  "rust-analyzer.check.command": "clippy"
}

Boost Your Windows Rust Build Speed

Windows Defender Exclusions for .cargo

Incremental builds in Rust generate thousands of tiny temporary files. Windows Defender aggressively scans every single one of these files during compilation.

Open Windows Security > Virus and threat protection > Manage settings > Exclusions. Add your %USERPROFILE%\.cargo folder and your main project directories to the exclusions list. The compile time reduction is immediate and significant.

Using Windows 11 Dev Drive

Microsoft introduced Dev Drive specifically for heavy workloads like Rust compilation. It uses the ReFS file system to handle thousands of small file operations efficiently.

Create a dedicated Dev Drive partition and move your Rust projects there. This architecture eliminates the hard link overhead and delivers a 20 to 30 percent faster build speed compared to standard NTFS volumes.

Fixing Common Rust Installation Errors on Windows

Solving the link.exe Not Found Error

This error means the Rust compiler cannot locate the Microsoft C++ linker. You either skipped the Build Tools installation entirely or forgot to select the C++ workload. Rerun the Visual Studio Installer and ensure the Desktop development with C++ box is explicitly checked.

rustup self update Fails Due to File Lock

Running the update command while VS Code is open almost always fails. The rust-analyzer extension locks the .cargo binary files in the background. Close VS Code completely before running the update command.

rustup self update
rustup update stable

Error 0xC0000005 STATUS_ACCESS_VIOLATION

This memory access violation usually happens during the initial component download. Overzealous third-party antivirus software blocks the network requests. Temporarily disable your antivirus during the installation phase, then re-enable it after the download completes.

Running Your First Project with Cargo

Cargo handles everything from dependency management to building the final binary. Open your terminal and scaffold a fresh application.

cargo new my_project
cd my_project
cargo run

You will see the compiler fetch the necessary crates and execute your code. From here, use cargo add [crate] to add dependencies, cargo fmt to format your code, and cargo clippy to run the linter.

Understanding the differences between C and C++ is useful context for choosing between Rust and existing C++ codebases, especially when vcpkg or FFI bindings are part of your stack.

FAQ

Frequently Asked Questions

Download rustup-init.exe from rustup.rs and run it. Press 1 for the default installation. This installs rustc, cargo, and the standard library to %USERPROFILE%\.cargo\bin. Close your current terminal completely and open a fresh one before testing with cargo --version.

You need the Visual Studio Build Tools with the Desktop development with C++ workload selected, but not the full Visual Studio IDE. The Build Tools are free and provide the MSVC linker that Rust requires to produce executables.

MSVC is the default and recommended choice on Windows. It integrates natively with Windows APIs and libraries. GNU uses MinGW and is only necessary when your project depends on legacy C libraries that will not compile under MSVC.

The two main causes are Windows Defender scanning .cargo files during incremental builds, and NTFS hard link overhead. Add %USERPROFILE%\.cargo to Windows Defender exclusions for an immediate improvement. On Windows 11, moving projects to a Dev Drive gives a further 20 to 30 percent speed gain.

This error means the MSVC C++ linker is missing. Rerun the Visual Studio Installer, select Modify, and check that the Desktop development with C++ workload is installed. Restart your terminal after installation before running cargo build again.

No. The rustup installer adds %USERPROFILE%\.cargo\bin to your PATH automatically. The only step required is closing your current terminal and opening a fresh session for the PATH change to become active.

Yes. Use winget install Rustlang.Rustup for a native Windows approach, or scoop install rustup via the Scoop package manager. Both install entirely within your user profile without requiring UAC elevation.

Install the rust-analyzer extension from the VS Code marketplace. In workspace settings, change the Check Command to clippy for continuous linting on save. For debugging, install either CodeLLDB or the Microsoft C++ extension depending on your preferred debugger.

Published in

Programming