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

Hitting that link.exe not found error is pretty much the classic rite of passage when getting started with Rust on Windows. Most people assume they can just run a single installer and call it a day, but Rust on Windows actually leans heavily on native platform tools.

If you skip installing the right C++ packages or forget to tweak Windows Defender, your compile times will grind to an absolute crawl. Taking ten minutes to dial in your setup right now will easily save you hours of head-scratching later.

Core Toolchain: MSVC (default, and by far the smoothest option)

Required Dependency: Desktop development with C++ (from Visual Studio Build Tools)

Default Install Path: %USERPROFILE%\.cargo\bin

Quick Performance Hack: Add an exclusion for your .cargo folder in Windows Defender

The Big Choice Up Front: MSVC vs GNU

Before you install anything, you’ll want to pick your toolchain, which sets the tone for your whole workflow. For 95% of people, MSVC is the way to go because it talks directly to native Windows APIs, handles system libraries cleanly, and plays nicely with the rest of the OS. The catch is that you need Microsoft’s build tools installed, but the payoff is rock-solid stability.

The GNU toolchain relies on MinGW instead. You really only need to touch GNU if you're wrangling legacy C libraries that stubbornly refuse to play well with Microsoft's compiler. Unless you already have a very specific reason to avoid MSVC, stick with the default - it will save you endless compatibility headaches down the road.

Step-by-Step: Getting Rust Running on Windows

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

Under the hood, Rust doesn’t ship its own linker for Windows; it borrows the one from Microsoft to stitch your code into an actual .exe. Head over to Microsoft’s site, grab the Visual Studio Build Tools installer, launch it, and make sure you check the box for Desktop development with C++.

You really don't want to skip this step if you're using MSVC. If you leave that box unchecked or bypass the installer entirely, the very first time you try to build a basic project, the compiler is going to stop dead in its tracks and throw linker errors at you.

Step 2: Run rustup-init to Fetch the Core Bits

Next, bounce over to rustup.rs and download rustup-init.exe. Fire it up, and you’ll see a simple command-line prompt asking how you want to proceed. Just hit 1 to accept the default settings, which sets up the MSVC toolchain cleanly.

The installer will quietly pull down rustc (the actual compiler), cargo (the package manager and build runner), and the standard library, tucking everything neatly into your %USERPROFILE%\.cargo\bin folder.

Step 3: Refresh Your Terminal for the PATH Update

Behind the scenes, the installer injects that new .cargo\bin directory straight into your system PATH. The catch is that any terminal you already had open before running the installer won't see the changes yet. Go ahead and completely close out of your Command Prompt, PowerShell, or Windows Terminal windows.

Fire up a brand-new terminal window and run a quick sanity check to make sure the binaries are picked up properly:

Bash

rustc --version
cargo --version

That quick restart saves you from that annoying "command not recognized" error that confuses almost everyone on their first install.

Working Without Admin Rights: Scoop and Winget

If you're stuck on a locked-down work laptop where IT won't hand over local admin rights, don't worry - you still have good options. Windows has built-in package managers that let you pull down developer tools without fighting UAC dialogs. If you have Winget available, just pop open PowerShell and run:

PowerShell

winget install Rustlang.Rustup

Alternatively, Scoop is brilliant for user-space installs. It drops everything directly into your user profile and handles your environment paths cleanly without ever nagging you for elevated system permissions:

PowerShell

scoop install rustup

Dialing in VS Code and rust-analyzer

For your editor, pairing Visual Studio Code with the official rust-analyzer extension gives you an incredible development workflow. Head over to the VS Code Extensions tab, search for rust-analyzer, and install it.

Once that's in place, open up your settings and tell the extension to use clippy as its check command instead of plain cargo check. Clippy is Rust’s built-in linter, and running it on save means you'll spot unidiomatic patterns and subtle bugs right as you type, well before you ever trigger a manual build.

JSON

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

Speeding Up Your Windows Build Times

Tell Windows Defender to Ignore .cargo

Every time you compile a Rust crate, the build system churns out thousands of tiny intermediate files in rapid succession. By default, Windows Defender tries to scan every single one of those files in real time, which ends up completely throttling your CPU during builds.

Head into Windows Security > Virus & threat protection > Manage settings > Exclusions, and add an exclusion for both your %USERPROFILE%\.cargo folder and wherever you keep your project code. You will notice an immediate, night-and-day difference in how fast projects compile.

Take Advantage of Windows 11 Dev Drive

If you are running Windows 11, Microsoft built a feature called Dev Drive specifically to solve these kinds of heavy disk I/O bottlenecks. It formats a storage volume with ReFS instead of standard NTFS, which handles high-frequency file reads and writes far better.

Set up a dedicated Dev Drive partition and keep your Rust workspaces there. Because it eliminates a ton of filesystem overhead and security filter bloat, you can easily see compile speeds jump by 20 to 30 percent on larger, dependency-heavy projects.

Troubleshooting the Classic Gotchas

Fixing the "link.exe Not Found" Error

If you run into this, it just means Rust tried to assemble your executable but couldn't find the Microsoft C++ linker anywhere on your path. It almost always means the Visual Studio Build Tools either aren't installed or you missed that one specific checkbox. Pop open the Visual Studio Installer, click Modify on your build tools installation, and double-check that Desktop development with C++ is turned on.

When "rustup self update" Hits a File Lock

Trying to run an update while VS Code is open in the background almost always fails with an access error. That’s because the rust-analyzer extension keeps the background Cargo and compiler binaries actively open in memory. Just shut down your IDE completely before you run your update routine:

Bash

rustup self update
rustup update stable

Dealing with Error 0xC0000005 (STATUS_ACCESS_VIOLATION)

This nasty-looking crash usually rears its head right during the initial download phase when rustup is grabbing components. More often than not, an aggressive third-party antivirus is intercepting the download stream and breaking the process mid-transfer. Pause your real-time antivirus protection for two minutes, run the install again, and switch your security back on once it finishes.

Spinning Up Your First Project

Once the tooling is in place, Cargo handles the rest of the heavy lifting for you - from building and testing to pulling in third-party libraries. Open up your terminal, hop into your workspace folder, and tell Cargo to generate a fresh starter app:

Bash

cargo new my_project
cd my_project
cargo run

Cargo will automatically compile the default template and run it, printing "Hello, world!" straight to your console. From there, you can pull in new packages with cargo add [crate], clean up your styling with cargo fmt, and run thorough static checks with cargo clippy.

Keeping a grasp on how C and C++ behave under the hood is also super handy here, especially if you ever find yourself linking native Windows C++ libraries via vcpkg or bridging legacy code through Rust's FFI system.