Closed Lockszmith-GH closed 6 months ago
Hello,
does C:\Program Files\WingetUI\PackageEngine\Managers\winget-cli_x64\winget.exe report those missing updates?
Almost, it reports something, but not everything:
I've tried with --include-unknown, and it's a bit different, but still doesn't match PowerShell output.
Then, right before I hit send here, I tried:
& "${env:LOCALAPPDATA}\Microsoft\WindowsApps\winget.exe" upgrade --include-unknown
and got the 12 packages split into 2 sections.
So it seems to be a mixture of the winget version, as well as the --include-unknown flag.
I will study this.
Thanks, it was really late yesterday, and so I didn't go through better collection, below are some additional output:
& "${env:LOCALAPPDATA}\Microsoft\WindowsApps\winget.exe" upgrade --include-unknown
& "${env:LOCALAPPDATA}\Microsoft\WindowsApps\winget.exe" upgrade
& "C:\Program Files\WingetUI\wingetui\PackageEngine\Managers\winget-cli_x64\winget.exe" upgrade --include-unknown
& "C:\Program Files\WingetUI\wingetui\PackageEngine\Managers\winget-cli_x64\winget.exe" upgrade
& "C:\Program Files\WingetUI\PackageManagers\winget-cli_x64\winget.exe" upgrade --include-unknown
(same as above)Hello, What does "${env:LOCALAPPDATA}\Microsoft\WindowsApps\winget.exe" --version report?
old, bad output:
> & "${env:LOCALAPPDATA}\Microsoft\WindowsApps\winget.exe" --version v1.6.3482 > & "C:\Program Files\WingetUI\PackageManagers\winget-cli_x64\winget.exe" --version v1.6.2771 > & "C:\Program Files\WingetUI\wingetui\PackageEngine\Managers\winget-cli_x64\winget.exe" --version v1.6.3482
OK, that's very weired. I'm going to uninstall WingetUI, completely remove any trace and try again. I'll report back.
I reinstalled WinGetUI, now I only have a single cli_x64 winget.exe, this is the output:
> & "${env:LOCALAPPDATA}\Microsoft\WindowsApps\winget.exe" --version
v1.6.3482
> & "C:\Program Files\WingetUI\wingetui\PackageEngine\Managers\winget-cli_x64\winget.exe" --version
v1.6.3482
I've made sure Ignored Updates are clear, and now I have the following in the UI:
Below is the output of the cli tools, system and the WinGetUI version
& "C:\Program Files\WingetUI\wingetui\PackageEngine\Managers\winget-cli_x64\winget.exe" upgrade
& "C:\Program Files\WingetUI\wingetui\PackageEngine\Managers\winget-cli_x64\winget.exe" upgrade --include-unknown
The following is a screenshot when using the System Winget under advanced settings:
& "${env:LOCALAPPDATA}\Microsoft\WindowsApps\winget.exe" upgrade
& "${env:LOCALAPPDATA}\Microsoft\WindowsApps\winget.exe" upgrade --include-unknown
There is a difference between the embedded winget and the system winget, even though they are reporting the same version.
This might not be considered a bug, and if this was the case I would probably not have reported this.
Whatever was affecting my system, was some relic from previous installation.
Sorry to have wasted your time - I should have done this uninstall/reinstall first, following the first rule of IT
ImageMagick is still not shown in either, so there is still a minor bug if you still want to pursue this.
Sorry to have wasted your time - I should have done this uninstall/reinstall first, following
Don't worry, this bug shouldn't have occurred even if the older winget version was there.
I will investigate ImageMagick, since it should be shown on WingetUI.
I am sorry, but winget on windows 11 does not work in wingetui. If I use the above method I get in the latest PowerShell
& "${env:LOCALAPPDATA}\Microsoft\WindowsApps\winget.exe" --version v1.6.3482 & "C:\Program Files\WingetUI\wingetui\PackageEngine\Managers\winget-cli_x64\winget.exe" --version NO OUTPUT whatsoever
Somethging does not work. Uninstalling both and reinstalling them does not help.
It would be great if that bug could be found
Thanks.
Please try enabling "Use system Winget" from WingetUI Settings -> Experimental Features
Please confirm these before moving forward
Describe your issue
After I completed all updates with WinGetUI, one of my apps, prompted me for an update, but it wasn't listed as available in WingetUI.
Using the official Microsoft.WinGet.Client PowerShell Module has become the most convenient cli method for me, so I listed the available updates using powershell and got a list of additional packages not listed in the UI.
Things I treid to validate the issue is WinGetUI and not my actions:
The Log output below is right at restart, using the internal WinGet when it returned nothing. Interestingly enough, the Total packages entry in the log matches the count from PowerShell: 242.
Steps to reproduce the issue
Make sure you are using the latest PowerShell (not Windows PowerShell)
Launch
pwsh
and install the module:Simplest way would be to clean WinGetUI Software Updates view by updating everything, otherwise compare the output below to the view:
WingetUI Log
WingetUI Log
```text 🟢 Using cached lang file 🟡 Using bundled lang file (forced=True) 🔵 It took 0.04169011116027832 to load all language files 🟢 checkQueue Thread started! 🔵 Language file up-to-date 🔵 Found default chocolatey installation on expected location --------------------------------------------------------------------------------------------------- WingetUI version 2.2.0 (version number 2.2) log All modules loaded successfully and sys.stdout patched correctly, starting main script Translator function language set to "en" --------------------------------------------------------------------------------------------------- Log legend: 🔵: Verbose 🟢: Information 🟡: Warning 🟠: Handled unexpected exception 🔴: Unhandled unexpected exception 🔴 Traceback (most recent call last): 🔴 Traceback (most recent call last): 🔴 File ".\__main__.py", line 69, inPackage Managers Logs
Relevant information
No response
Screenshots and videos