scoop.fatal in the update section

[ppvnf]

I'm using the latest version of WingetUI and Windows 10 x64 21h2 and I'm getting a bunch of scoop.fatal packages in the update section. There's also scoop.git and scoop.to. I can see the actual updates if I scroll down. Out of 37 updates availables only 3 are real packages.

[marticliment]

What happens if you run scoop status in a cmd window?

[ppvnf]

It seems scoop is not being properly detected by WingetUI. I did a few tests. I can update and uninstall scoop apps through WingetUI but if I try to install a new one nothing happens (I can still install through CMD tho). Winget works perfectly.

[marticliment]

if you run "scoop status in cmd what happens?"

[marticliment]

cmd, not powershell

[ppvnf]

[marticliment]

weird... I'll take a look

[marticliment]

Does WingetUI 1.3 work now?

[ppvnf]

Does WingetUI 1.3 work now?

Partially. I successfully used WingetUI 1.3 to install Google Chrome from scoop, which I couldn t do previously through WingetUI 1.2. I can t, however, uninstall scoop apps using WingetUI 1.3. I could uninstall using 1.2 though. Besides that there are still dummy packages in the update section and scoop isn`t properly detected as installed.

[ppvnf]

[marticliment]

When uninstalling, are you using the "remove app data" context menu option or are you simply double-clicking?

[ppvnf]

When uninstalling, are you using the "remove app data" context menu option or are you simply double-clicking?

I was double-clicking. I just tried the context menu option and it works!

[marticliment]

ah, that was not expected...

Amnyway, i'll take a look

[ppvnf]

ah, that was not expected...

Amnyway, i'll take a look

I had this idea after reading another issue. I tried running WingetUI as administrator and all issues were solved! By the way, instead of always right-clicking to run as administrator you can do this automatically. I would say my issue is mostly fixed, but I guess having to run as administrator is not ideal.

"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."

Originally posted by @rp1231 in https://github.com/martinet101/WingetUI/issues/104#issuecomment-1238384644

[marticliment]

I guess having to run as administrator is not ideal

It is definitely not

[marticliment]

Could you try uninstalling WingetUI from scoop and then installing from WingetUI or manually?

[ppvnf]

Could you try uninstalling WingetUI from scoop and then installing from WingetUI or manually?

Same result. The problems are fixed only by running as administrator

[marticliment]

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

[ppvnf]

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

Awesome!

[ppvnf]

I've tried 1.4 without admin privilages and scoop still isn't recognized and fake updates still appear =(. log.txt

[ppvnf]

LMAO Building WingetUI wasn't totally successful, but I accidentally fixed this issue on https://github.com/martinet101/WingetUI/issues/163#issuecomment-1264737794 I will left this open so you can decide if this "fix" can be applied to other users Maybe it was because of git config --global --add safe.directory...

[marticliment]

Git should mark by default scoop dirs as safe, i guess this is more a scoop issue...

[ppvnf]

Git should mark by default scoop dirs as safe, i guess this is more a scoop issue...

I believe so