Closed peter-altherr closed 1 month ago
Please go to UniGetUI settings -> WinGet -> Disable Use bundled WinGet instead of System WinGet
Thank you very much for this super fast reply :-) Please see the screenshot of my current settings.
Looking at your logs, it looks like you don't have WinGet installed.
What happens when you call winget.exe
on a command-prompt window?
I called winget.exe --version within the PowerShell that came with Windows 11 as well as in the PowerShell 7.4.5 and finally in a cmd.exe-window. Please find below the output.
Windows builtin PowerShell `Windows PowerShell Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
Installieren Sie die neueste PowerShell für neue Funktionen und Verbesserungen! https://aka.ms/PSWindows
PS C:\Users\peter> winget.exe --version v1.8.1911 PS C:\Users\peter>_`
Powershell 7.4.5 `PowerShell 7.4.5
Loading personal and system profiles took 653ms.
PS C:\Users\peter> winget.exe --version
v1.8.1911
PS C:\Users\peter>_`
cmd.exe `Microsoft Windows [Version 10.0.26100.1742] (c) Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\peter>winget.exe --version v1.8.1911
C:\Users\peter>_`
As i wrote in my first post when i copy/paste the install command from the UniGetUIs package detail window in a PowerShell 7.4.5 the installation goes through without any error including UAC popup.
Huh, this is weird. winget.exe is not being detected by UniGetUI. I will investigate
Thank you. If I can serve you by providing any additional information and logs or by doing some tests, just let me know. In the meantime I will use UniGetUI on this machine for getting informed about pending package updates. The update itself I will do by manually copy/paste the install command into a PowerShell.
Same issue on all of my Windows 11 Enterprise 24H2 machines. All installation or upgrade attempts lead to Exit Code: -1978335231. No difference with build in winget or without. Winget itself works fine on command line.
I am afraid the error you are receiving here is APPINSTALLER_CLI_ERROR_INTERNAL_ERROR
, and I can't help with that if neither bundled or system WinGet works
So this sounds like a winget issue to be investigated/adressed by the winget team?
Yep
This is fixed by 3.1.2 Beta 4. Thanks a lot 👍🏼
I can confirm 3.1.2 Beta 4 fixed the issue on all my machines, thank you! :)
Please confirm these before moving forward
UniGetUI Version
3.1.1
Windows version, edition, and architecture
Windows 11 Enterprise 24H2
Describe your issue
Since updating UniGetUI from 3.1.0 to 3.1.1 i always get the error message update failed when a package is getting updated, no matter what package. Following an example of the Logitech.GHUB package.
Steps to reproduce the issue
Starting package update operation for package id=Logitech.GHUB with Manager name=Winget Given installation options are <InstallationOptions: SkipHashCheck=False;InteractiveInstallation=False;RunAsAdministrator=False;Version=;Architecture=;InstallationScope=;InstallationScope=;CustomParameters=;RemoveDataOnUninstall=False> Process Executable : C:\Program Files\UniGetUI\winget-cli_x64\winget.exe Process Call Arguments : update --id "Logitech.GHUB" --exact --source winget --accept-source-agreements --disable-interactivity --silent --include-unknown --accept-package-agreements --force Working Directory : C:\Users\peter Process Start Time : 18.09.2024 12:51:39 **Process Exit Code : -1978335231** Process End Time : 18.09.2024 12:51:39
Taking a look at the package details page shows:
`Package ID: Logitech.GHUB Manifest: https://github.com/microsoft/winget-pkgs/tree/master/manifests/l/Logitech/GHUB Installed Version 2024.5.586677 - Update to 2024.6.476 available
Installer Type: Not available Installer URL: Not available Installer SHA256: Not available Installer not available
Last updated: Not available Release notes: Not available Release notes URL: Not available`
UniGetUI Log
Package Managers Logs
Relevant information
A quick web search for the process exit code brought some hits related to winget but it is not a winget issue at least not only. When i copy/paste the following command line
winget.exe update --id "Logitech.GHUB" --exact --source winget --accept-source-agreements --disable-interactivity --silent --include-unknown --accept-package-agreements --force
into a user (non-admin) powershell window the package download and installation works fine including UAC admin popup so it does for every other failed package update. Please note: if you copy the above line in your powershell it does not work for this particular Logitech.GHUB package as this package does not pass the hash check. This is a package problem while the issue in general is a UniGetUI issue.
Screenshots and videos
No response