Closed stevehoek closed 1 month ago
Could you send me the output of winget upgrade
command ?
Also, is there any error in the logs ?
@Tigzy no errors in the logs, just a message saying it found 0 programs. My system is fully up to date right now so I will send the winget upgrade logs when I get a new update
Could you try out the latest BETA see if there's something ?
@Tigzy unfortunately BETA4 actually logs an error
2024/04/19 08:59:15:DEBUG [UCheck::GetWingetList] Getting winget programs list...
2024/04/19 08:59:19:CRITICAL [UCheck::GetWingetList] Unable to parse winget list output
2024/04/19 08:59:19:DEBUG [UCheck::GetWingetList] Found 0 winget programs and 0 updates available.
Here is my winget-list and winget-upgrade output
I see no problem with parsing those files in the latest changes. Let's see what the main release says.
Seems to work with the official release of 5.4.0... thanks!
Preliminary Checks
Beta Version
What happened?
Winget works on Windows Servers (2019, 2022) but has a few known issues. For one, the UWP call to get the resource strings does not exist on the Server platform, so by default Winget just shows its placeholder label. For instance, here is Winget's output showing CLI commands:
`WindowsPackageManager MainCopyrightNotice
ToolDescription
Usage [] []
AvailableCommands install InstallCommandShortDescription show ShowCommandShortDescription source SourceCommandShortDescription search SearchCommandShortDescription list ListCommandShortDescription upgrade UpgradeCommandShortDescription uninstall UninstallCommandShortDescription hash HashCommandShortDescription`
UCheck can't seem to parse the output of "winget list" in this case; I guess it is looking for the actual strings?
Here is my winget list output from a Server 2019 machine winget-list.txt
ucheck-report
No response
Is the issue reproductible?
Yes
Don't forget to vote !