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] Scoop was not found on WingetUI 3.x, works fine on 2.2 #2157
Comments
|
Hm? Both the WingetUI and Packet Manager logs are already there for 3.0.0 (same result on 3.0.1 and 3.0.2) and 2.2. |
Sorry, I didn't see them. What happens when you run the command |
C:\Users\uXp>where scoop |
How did you install scoop? |
I have the same issue. I have changed the environment variable and installed scoop in a custom path. |
You have scoop added on user path or on system path? |
same here, (fresh windows 11 23H2 installation) |
Here is the log, just in case. |
same here, (fresh windows 11 23H2 installation), too |
i did |
No, I was asking on which path do you have scoop, user OR system path |
Same issue here, I installed Scoop directly from WinGetUI on a pretty fresh Windows installation, but it isn't recognized. I tried rebooting, adding Scoop to system path (it was already added to user path), I have no clue what to do to get it working. If I invoke scoop through any terminal window it works, it's just WinGetUI that doesn't recognize it. |
@ipisano commented on May 20, 2024, 1:14 PM EDT:
I partially fixed my problem by deleting the scoop folder inside the app scoop/apps then reinstalled it via WingetUI but it took several attempts in order to make it recognize scoop! Still this doesn't seem to be very reliable since when searching with apps it doesn't show those who are in scoop buckets but the updates somehow work! |
Please confirm these before moving forward
Describe your issue
When using any 3.x version of WingetUI it says "Scoop was not found".
Using version 2.2 it works totally fine.
Steps to reproduce the issue
No response
WingetUI Log
Package Managers Logs
Relevant information
No response
Screenshots and videos
No response
The text was updated successfully, but these errors were encountered: