-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[Bug] Installing Scoop fails: "The term 'Select-CurrentVersion' is not recognized" #4783
Comments
/cc @niheaven |
Could you please try this first and see if works? |
We are now seeing this same issue on our Github actions-based CI: https://github.com/tinygo-org/tinygo/runs/5460413855?check_suite_focus=true#step:3:16 |
Sorry, will be fixed today, and please use a pre-release script that I mentioned above. |
Thanks for the quick reply @niheaven it is appreciated! |
it works for me |
i tried this way, but it's not work |
For me the problem was in Company Group Policy + PORT was locked i hope this helps |
Please check ScoopInstaller/Install#advanced-installation for documentation about this issue. |
I reinstalled the app when this bug was fixed, everything is ok. |
Apparently a bug was introduced with the scoop installer ScoopInstaller/Scoop#4783 They suggest to install it directly
Is this new? This looks like a breaking change on our side as the script was working fine in GH Actions context before, but now needs to be done differently without any change. |
It's an updated and standalone installer written by @chawyehsu. It looks like it's breaking a lot of automated actions which run as admin. @chawyehsu can we introduce a workaround for this to have parity with the old installer? |
Apparently a bug was introduced with the scoop installer ScoopInstaller/Scoop#4783 They suggest to install it directly
@rashil2000 this issue is closed, do we need a new one to track the concern in your message? |
The Readme for installation has been updated. |
Попробуй |
thanks 👍 |
yes this works :) Ensure the command is executed in a PowerShell with administrative privileges: iex "& {$(irm get.scoop.sh)} -RunAsAdmin" also this has been reported with the same solution on Stackoverflow |
Bug Report
Current Behavior
I am trying to install Scoop. Running in the installer script (https://get.scoop.sh) fails:
Expected Behavior
I expect Scoop to install without any errors reported.
Additional context/output
Possible Solution
System details
Windows version: 10
OS architecture: 64bit
PowerShell version:
Additional software:
Scoop Configuration
Not applicable.
The text was updated successfully, but these errors were encountered: