Unverified50% confidenceSolutionExact time
If the conda command reports "is not recognized as an internal or external command", it is usually because the environment variable has not been added, and you need to manually add the installation path and the Scripts directory to the Path system variable.
1
Sources
50%
Confidence
Long-term
Relevance
11/18/2026
First Seen
Sources
PyTorch for Beginners: Setting Up Anaconda + VSCode Environment
bilibili猴哥学AI11/18/2026
Related Entities
Related Claims
UnverifiedAfter installing Anaconda on Windows, you need to make sure "Add to environment variables" is checked or manually add the installation path to the system Path, otherwise the `conda` command may be unavailable.69% similarUnverifiedIf typing gemini results in a "command not found" prompt, the most likely cause is that the global installation path has not been added to the system environment variable PATH, which can be resolved by restarting the terminal or confirming that the npm global bin directory is in PATH.67% similarUnverifiednpm's -g flag means global installation: the installed package is placed in a system-level directory, and the executable command is registered in the PATH environment variable, allowing the command to be run directly from any directory.65% similarUnverifiedWhen switching conda environments in VSCode, you need to click the bottom-right corner and select "Add New Interpreter", locate conda.exe in the Anaconda installation directory, and after it loads, select the corresponding environment.63% similarUnverifiedThe contents of the PATH environment variable, when read by a system call (such as execvp), do not go through the shell's expansion process, so a ~ in PATH is treated as an ordinary character-based directory.62% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1184716API
curl https://kongchang.com/api/v1/knowledge/claims/1184716MCP
get_claim(id=1184716)