We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According to this: https://docs.solanalabs.com/cli/install#windows
On a PowerShell terminal with admin priviledges: Step 1. Download .exe the file: OK. Step 2. Execute:
C:\solana-install-tmp\solana-install-init.exe v1.18.18
It download a temp file but gives following error and deletes the temoral folder.
Error: Unable to extract "C:\\Users\\JPGN\\AppData\\Local\\Temp\\.tmpNAAk3w\\download" to "C:\\Users\\JPGN\\.local\\share\\solana\\install\\releases\\1.18.18": Acceso denegado. (os error 5)
Checking the folders seems to be installed in ("temp-extract" instead of "1.18.18"):
C:\Users\JPGN\.local\share\solana\install\releases\tmp-extract\solana-release\bin
Adding this folder to the PATH it seems to be working:
C:\Users\JPGN>solana --version solana-cli 1.18.18 (src:83047136; feat:4215500110, client:SolanaLabs)
Seems like it doesn't have priviledges to change the folder's name when installing but it shouldn't be the case.
Should I report this like a bug?
The text was updated successfully, but these errors were encountered:
This repository is no longer in use. Please re-open this issue in the agave repo: https://github.com/anza-xyz/agave
Sorry, something went wrong.
No branches or pull requests
According to this: https://docs.solanalabs.com/cli/install#windows
On a PowerShell terminal with admin priviledges:
Step 1. Download .exe the file: OK.
Step 2. Execute:
It download a temp file but gives following error and deletes the temoral folder.
Checking the folders seems to be installed in ("temp-extract" instead of "1.18.18"):
Adding this folder to the PATH it seems to be working:
Seems like it doesn't have priviledges to change the folder's name when installing but it shouldn't be the case.
Should I report this like a bug?
The text was updated successfully, but these errors were encountered: