Skip to content
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

solana cli v1.18.18 on windows 10 installation error #2421

Closed
jpablogn opened this issue Aug 2, 2024 · 5 comments
Closed

solana cli v1.18.18 on windows 10 installation error #2421

jpablogn opened this issue Aug 2, 2024 · 5 comments

Comments

@jpablogn
Copy link

jpablogn commented Aug 2, 2024

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?

@ripatel-fd
Copy link

Do you run anti-virus on your machine?

@jpablogn
Copy link
Author

jpablogn commented Aug 7, 2024

yes

@Nagaprasadvr
Copy link

Can u run it as administrator

@ripatel-fd
Copy link

yes

Then this is most likely a permission error caused by your anti-virus and not a problem with the Agave software.

@steviez
Copy link

steviez commented Aug 16, 2024

Agreed with Richard's assessment that this looks to be an issue on your system, and not with Agave. As such, closing the issue

@steviez steviez closed this as completed Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants