-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Windows installation documentation to recommend manual method #1247
Comments
The install script installs into |
It looks like if you open PowerShell as Administrator the default Sorry that's not a lot of help, I probably know windows less than you, but do have a windows 10 laptop here I can test with :) |
Hey everyone! As kennethd stated the default directory when starting powershell as admin is As follows: |
It just installed Rustlings in my System32 folder too. The intructions need to mention that you need to navigate to the desired folder first or the script needs to act more intelligently. Current situation is not very user friendly and will mean a broken installation for most users on the first try. |
Updated the script to install in |
This issue will be prevented by #1919 |
I am a linux user & do all of my development there, but started playing around with rust on a windows machine & just blindly followed the instructions at https://github.com/rust-lang/rustlings/#windows
This installation method requires installing with administrator privileges, installs into a protected system folder, which is read-only by default, and therefore, upon completion, rightly triggers errors from anti-virus software
Vim won't even
cd
to this protected directoryUpon realizing all of this, I undid it all by running
cargo uninstall rustlings
from the same administrator PowerShell session & manually deletingc:\\Windows\System32\rustlings
, and did the manual installation steps as a regular user with no problemThere have been a couple past issues created by people who found themselves in trouble after following these instructions, e.g. #878
The text was updated successfully, but these errors were encountered: