Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Win11 min MSVC prerequisites rustup handbook not enough to make rustup-init.exe detect MSVC

Aperta
  • Qualcosa non va?
#4,699 5 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
38/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
rust
Ambito
devtools

Direzione di ricerca

Inizia dalla pagina dei prerequisiti Windows MSVC del rustup handbook e dall’entry point di rilevamento MSVC di rustup-init.exe. Riproduci il malfunzionamento usando solo i componenti Visual Studio elencati, quindi determina se il handbook o il comportamento di rilevamento è errato; il lavoro è completo quando i requisiti minimi sono accurati e le indicazioni risultanti sono verificate.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
Verification
Problem

On this page of the rustup handbook, there is a description of the minimum requirements necessary to make rustup-init.exe not complain about a missing MSVC installation. Quoting the manual, the minimal requirements are as follows:

  • MSVC v143 - VS 2022 C++ x64/x86 build tools (Latest)
  • Windows 11 SDK (10.0.22621.0)

I already had an installation of Visual Studio Community 2022, that came with the installation of Unity3D, so I opted to modify it in the installer. In the modification, I chose those the exact two packages as above. However, after the installation was complete, I was still greeted by the following message when starting rustup-init.exe:

Rust requires the Microsoft C++ build tools for Visual Studio 2017 or later, but they don't seem to be installed.

I tried installing several other components, among which the Universal C Runtime, all without result. The only thing that worked, was exactly what I was trying to prevent: installing the "Desktop development with C++" workload, which installs a whole bunch of stuff that I don't need and therefore wastes several GBs and some time.

Steps
  1. Install Visual Studio Community 2022 (just to be sure, via a Unity3D installation)
  2. After it is done, modify the installation via the Visual Studio Installer to include the minimal individual components as indicated here, which are: MSVC v143 - VS 2022 C++ x64/x86 build tools (Latest), Windows 11 SDK (10.0.22621.0)
  3. Download and run rustup-init.exe. It will tell you: Rust requires the Microsoft C++ build tools for Visual Studio 2017 or later, but they don't seem to be installed.
  4. Now go back to the Visual Studio Installer, modify the installation, and select the "Desktop development with C++" workload, then commence.
  5. When the installer is done, start rustup-init.exe again. It will no longer complain about missing build tools.
Possible Solution(s)

If reproducible by others, it would be nice if this suggestion of the manual was either removed due to incorrectness, or updated with the actual minimal set of components and actions necessary to make rustup-init.exe detect the tools that it needs, to prevent future time wasting. Furthermore, it would be nice to be able to more easily find how exactly rustup-init.exe goes about detecting these tools, as this information has been exceedingly hard to find and would help a lot with troubleshooting installation issues - perhaps this could be included in the handbook?

Notes

I also tried to install 2017 versions of the toolchain as the message suggests (so MSVC v141 - VS 2017 C++ x64/x86 build tools (v14.16)), same result.

Rustup version
rustup-init 1.28.2 (e4f3ad6f8 2025-04-28)
Installed toolchains
MSVC v143 - VS 2022 C++ x64/x86 build tools (Latest), Windows 11 SDK (10.0.22621.0)
OS version
Windows 11 (10.0.26200 Build 26200)
Lingua principale
Rust
Stelle
7.1k
Fork
1.1k
Merge medio
1g 10h
PR unite (30g)
42

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di rust-lang/rustup

Tutte le issue di rust-lang/rustup

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.