error: toolchain 'stable' is not installed / override toolchain not found Rust Origin: Application & API OSI layer 7 · Application Last updated 5 Nov 2026

rustup: error: toolchain 'nightly-x86_64-unknown-linux-gnu' is not installed / error: no override and no default toolchain set

rustup can't find the toolchain requested by rust-toolchain.toml, an override, or no default is set.

Exact message you may see error: toolchain 'stable' is not installederror: no override and no default toolchain seterror: toolchain 'nightly-x86_64-unknown-linux-gnu' is not installederror: the 'cargo' binary, normally provided by the 'cargo' component, is not applicable to the 'stable-x86_64-unknown-linux-gnu' toolchainerror: component 'clippy' for target is unavailable
Explore the map of this error Full error map →
Seen on: Rust

Meaning

Install it: rustup toolchain install stable (or the one named), set a default with rustup default stable, or remove/correct rust-toolchain(.toml). In CI install the toolchain before building. Add targets/components: rustup target add wasm32-unknown-unknown, rustup component add clippy rustfmt.

Common causes

  • Fresh machine/CI without a default toolchain
  • rust-toolchain.toml names an uninstalled channel/date
  • Removed toolchain
  • Missing target/component
  • Corrupted rustup install

⚡ Quick fix

  1. rustup default stable
  2. rustup toolchain install nightly-2025-01-01 for pinned files
  3. rustup component add clippy rustfmt / rustup target add TARGET

Detailed fix by platform

Linux

  1. rustup show && rustup toolchain list

How to diagnose

  1. Toolchain — Installed?
  2. File — rust-toolchain.toml?
  3. Component — Present?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Application & API. Errors that are often confused with or caused by this one (click to open):

Blocking waiting for file lock on package cache / build directory — Cargo: Blocking waiting for file lock on package cache / on build directory (Rust)Blocking waiting for …cargo: failed to get from registry (spurious network error) — Cargo: warning: spurious network error (2 tries remaining): [35] SSL connect error / error: failed to download from `https://index.crates.io/...` (Rust)cargo: failed to get …cargo: failed to select a version for the requirement — Cargo: error: failed to select a version for the requirement `serde = "^2.0"` — candidate versions found which didn't match: 1.0.197 (Rust)cargo: failed to sele…E0004: non-exhaustive patterns — Rust: error[E0004]: non-exhaustive patterns: `None` not covered (Rust)E0004: non-exhaustive…E0658: use of unstable library feature — Rust: error[E0658]: use of unstable library feature `let_chains` / `#![feature]` may not be used on the stable release channel (Rust)E0658: use of unstabl…error: linker `cc` not found — Rust: error: linker `cc` not found — note: No such file or directory (os error 2) (Rust)error: linker `cc` no…feature edition2024 is required / Cargo.lock version too new — Cargo: error: failed to parse manifest — feature `edition2024` is required / lock file version 4 requires `-Znext-lockfile-bump` (Rust)feature edition2024 i…error: to…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.