Scoop error.

[fabcard]

Hello there, I downloaded and installed the WingetUI v1.2.0 on my win10pro 21H2 19044.1826. When opened, it shows 4 available updates, as you can see on the picture. I click upgrade all packages and I get 4 popup errors and nothing gets updated. Tried again with same results. Also tried to uninstall and install again with no luck.

Thanks in advance.

[marticliment]

Hi,

do you have scoop installed in your system?

[fabcard]

Hello, I did not manually install Scoop. Wasn't WingetUI supposed to install Scoop during its installation process? Thank you.

[marticliment]

It is, but it might eventually fail. In the about section you will find a table regarding the status of winget and scoop. There you will find if they are installed or not.

[fabcard]

Hi, So I guess I'll just wait for the next update, hopefully you guys can fix this Scoop fail on installation. Again, thank you.

[marticliment]

If you want, you can manually install scoop and see if that fixes the issue

[rp1231]

I installed scoop manually and installed WingetUI through scoop. But Scoop shows up and not installed in the ui. I'm also getting those random scoop updates as shown in the screenshot in the first post.

[rp1231]

Here are the screenshots:

[marticliment]

Hi,

quick question: is you scoop installation a custom one or is it the standard one?

[rp1231]

I followed the instructions on the scoop site

[rp1231]

https://scoop.sh/#:~:text=%3E%20Set%2DExecutionPolicy%20RemoteSigned%20%2DScope%20CurrentUser%20%23%20Optional%3A%20Needed%20to%20run%20a%20remote%20script%20the%20first%20time%0A%3E%20irm%20get.scoop.sh%20%7C%20iex

[rp1231]

Seems to have been solved for me in version 1.3

[marticliment]

@Hellements,

is this true for you?

[Spacellary]

Scoop | Not Found | Unknown

I do have scoop properly installed as it works from the Terminal but it is still "Not Found" in the Components.

I also did install WingetUI from scoop but that didn't work aswell.

[rp1231]

Yes it broke again for me as well after installing 1.3.1

[rp1231]

Ok nvm, It showed unknown, but now it's showing fine after I ran scoop update through command line and then ran ran wingetui. Not sure if doing the above steps resulted in it working again, but these were the steps that I did before it started working

[rp1231]

Ok I think i've identified the problem. If I start wingetUI from the start menu by searching for it, it shows scoop not found and unknown.

But if I right click on the start menu icon, click open file location and then run wingetui from the shorcut in windows explorer, It runs fine and detects scoop.

Really weird, but I was able to reproduce it multiple times.

[Spacellary]

Ok nvm, It showed unknown, but now it's showing fine after I ran scoop update through command line and then ran ran wingetui. Not sure if doing the above steps resulted in it working again, but these were the steps that I did before it started working

That did not work for me unfortunately.

But if I right click on the start menu icon, click open file location and then run wingetui from the shorcut in windows explorer, It runs fine and detects scoop.

Not even that worked for me. I'm cursed.

[rp1231]

When I type in scoop info wingetui in cmd This is the info I get:

Name        : wingetui
Description : A GUI to manage Winget and Scoop packages
Version     : 1.3.1
Bucket      : extras
Website     : https://github.com/martinet101/WingetUI
License     : LGPL-2.1-or-later
Updated at  : 06-09-2022 14:00:21
Updated by  : github-actions[bot]
Installed   : 1.3.0.0
              1.3.1
Shortcuts   : WingetUI
Suggestions : extras/vcredist

In the installed section it shows both 1.3.0 and 1.3.1

Posting this in case it helps in identifying the problem.

[rp1231]

I uninstalled and reinstalled wingetui and now it doesn't show two versions in the installed section.

Ok I think i've identified the problem. If I start wingetUI from the start menu by searching for it, it shows scoop not found and unknown.

But if I right click on the start menu icon, click open file location and then run wingetui from the shorcut in windows explorer, It runs fine and detects scoop.

Really weird, but I was able to reproduce it multiple times.

Here is a screenshot illustrating this:

The upper one doesn't detect scoop if I run it directly from the start menu, but if I right click on it and click open file location, it points to a shortcut in this folder: %userprofile%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Scoop Apps If I run the shortcut from explorer, it detects scoop.

And the lower one points to the actual exe in%userprofile%\scoop\apps\wingetui\1.3.1 And detects scoop even if I run it directly from the start menu.

[marticliment]

If you try fully removing WingetUI and then installing WingetUI from the installer or from winget, does it work better?

[rp1231]

I've been installing from scoop, I'll try it from the other methods.

[marticliment]

Also, if you run Scoop-installed WingetUI as admin, does it work better?

[rp1231]

The same start menu problem persists with the one installed from winget.

But it does detect scoop if I run it as administrator.

[rp1231]

Also if you search for wingetui on winget, It still shows v1.2 and autoupdates it self later. Mentioning this in case it is not expected behavior.

[marticliment]

Yes, the PR to update is waiting for approval

[marticliment]

It'll come soon

[rp1231]

The st

The same start menu problem persists with the one installed from winget.

But it does detect scoop if I run it as administrator.

The same problem persists even if I install it manually.

[Spacellary]

Reporting back: Installing using scoop or the installer for me neither work, with or without admin running directly from each .exe after uninstalling all versions present.

[marticliment]

Hi guys,

those .exe that you can find on the start menu where are they placed? How did they appear? Because I can't find them nowhere.

[rp1231]

In windows 11, You just type wingetui in the start menu. And they will appear.

[Spacellary]

In my case I just browsed to the installation directory to find them.

[rp1231]

For me it's suddenly working fine after updating windows 11 to the 22h2 update.... Not sure if that was what fixed it for me, but everything works fine now.

[marticliment]

This issue should have been fixed (for users who are still experiencing it) and will be available in WingetUI 1.4