[FEATURE REQUEST] location of local installation?

[neslekkim]

I would like to see where I have an certain package/app installed: Only think I can get here is package detalis, which tells me info about the new package, not where I have the current one.

I just updates this package, tesseract: I used voidtools - everything to find it on disc first, and found it under programfilesx86, after updating, it was still located there, but I got the new one under programfiles, so now I have a duplicate of this program. Not same issue, but if one install lot of updates, you can end up with duplicates like this, withouth knowing it?

[marticliment]

This is an issue with Winget.

Please note that WingetUI does not install the software, but rather call the winget.exe cli.

You might, if you want to, post this issue on microsoft/winget-cli.

However, I will take a look at it, and will inform you if I manage to fix it or not

[neslekkim]

I kinda like the idea of using winget for the packages that I install through winget, but winget takes over the whole computer, and wants to install everything, that I don't like (that is a winget problem, not wingetui problem ofcourse), I wonder why they did it like that, would be better that I could over time, migrate the apps I have installed separately over to winget (uninstall from appwiz.cpl, and reinstall using winget). If it was possible to have a list of packages that winget should not touch, it would be better I think, and avoid this type of issue.

[marticliment]

You can ignore updates, both from the Updates tab and from the Installed Software Section.

Also, you can use other package managers with WingetUI, such as Chocolatey or Scoop, which tend to give less issues when upgrading packages

[Wosamarak]

I came here to report this as an error. After installation of WingetUI I see three multiple lines of the same program beeing installed. Trying to install the update, one of the lines installs the update, while the other lines just report errors, that this program can't be updated.

So it would be really helpful to see, where the other versions should be located, to resolve this issue.

Edit: The same happened with some Microsoft Redistributables, the error message says: "No installed package found matching input criteria."

This looks like, that winget collects some evidence, that a give application/package may bei installed, but it isn't. So it would be really helpfull, if package details could reveal the location of the evidence, leading to an installation listing.

[marticliment]

could you please attach the actual output you are getting?

Thanks!

[Wosamarak]

Here two examples: First a DotNet Runtime upgrade:

Second Incscape: This is installed in the most recent version, however I receive messages, that two older versions should be installed and ready for update.

[marticliment]

can you please share your WingetUI log?

[Wosamarak]

Here is my log: 🟡 Using bundled lang file (forced=False) 🟡 Using bundled lang file (forced=True) It took 0.02203226089477539 to load all language files 🟢 checkQueue Thread started! 🔵 Starting main application... Scanning for instances... Found lock file(s), reactivating... 🔵 Starting update check b'v1.4.10173\r\n' None updating winget 🟢 Downloaded latest metadata to local file 🔵 Loaded metadata from local file b'1.2.1\r\n' None 🔵 Version URL: https://versions.marticliment.com/versions/wingetui.ver 🟢 Updates not found Reactivation signal ignored: RaiseWindow_[1685788995.0414717] {'wingetFound': True, 'scoopFound': False, 'chocoFound': True, 'sudoFound': True, 'wingetVersion': 'v1.4.10173\r', 'scoopVersion': 'Scoop ist deaktiviert', 'chocoVersion': '1.2.1\r', 'sudoVersion': 'gsudo v2.0.4 (Branch.tags-v2.0.4.Sha.506efa024af0cef6e4b0cfec42e0c8c5d0b1472c)\r'} 🔵 Reached main ui load milestone Can't disconnect 🔵 Starting winget search 🔵 Starting choco search 🟢 Discover tab loaded 🟢 Found valid cache for winget! Can't disconnect 🟢 Found valid cache for chocolatey! Can't disconnect 🟢 Starting winget search, winget on C:\Users\XXXXXXXX\AppData\Local\Programs\WingetUI\winget-cli\winget.exe... 🟢 Starting choco search, choco on C:\Users\XXXXXXXX\AppData\Local\Programs\WingetUI\choco-cli\choco.exe... 🟢 Upgrades tab loaded Can't disconnect 🟢 Starting winget search, winget on C:\Users\XXXXXXXX\AppData\Local\Programs\WingetUI\winget-cli\winget.exe... 🟢 Starting choco search, choco on C:\Users\XXXXXXXX\AppData\Local\Programs\WingetUI\choco-cli\choco.exe... 🟢 Discover tab loaded 🔵 Starting winget file update... 🟢 Starting choco search, choco on C:\Users\XXXXXXXX\AppData\Local\Programs\WingetUI\choco-cli\choco.exe... 🟢 Chocolatey uninstallable packages search finished Can't disconnect 🟢 Settings tab loaded! 🟢 Chocolatey search finished 🟢 About tab loaded! 🟢 Main application loaded... Win32Mica Error: win32 version 19045 is not supported 50 🟢 Total packages: 14004 🟢 Searching for string "" 🟢 Searching for string "" 🟢 Winget search finished 🟡 Package WinDirStat.WinDirStat version Unknown is ignored 🟡 Package Microsoft.VCRedist.2013.x86 version 12.0.30501.0 is ignored 🟡 Package Microsoft.VCRedist.2013.x86 version 12.0.21005.1 is ignored 🟡 Package Microsoft.VCRedist.2013.x86 version 12.0.40660.0 is ignored 🟢 Searching for string "" 🟢 Searching for string "" 🟢 Total packages: 63 🟡 package Update for (KB2504637) failed parsing, going for method 2... Update for (KB2504637) {CFEF48A8-BFB8-3EAC-8BA5-DE4F8AA267CE}… 1 80 🟢 Winget uninstallable packages search finished 🟢 Searching for string "" 🟢 Searching for string "" 🟢 Total packages: 341 🟢 Winget cache rebuilt 🟢 Total packages: 14004 🟢 Chocolatey search finished 🔵 Starting winget search 🔵 Starting choco search 🟢 Found valid cache for winget! 🟢 Found valid cache for chocolatey! 🔵 Starting winget file update... 🟢 Total packages: 10270 🟢 Total packages: 14036 🟢 Winget cache rebuilt 🟢 Total packages: 14036 🔵 Copying log to the clipboard...

[Wosamarak]

And another weird piece: I habe Ultraedit installed in the most recent version 2023.0.0.41 However WinGetUI reports, that there is a newer Version 2023.0.41 When trying to update it fails with a very cryptic information:

[Wosamarak]

And the next problem: Trying to update AutoHotkey. The Installer starts, stops at 50% with the information: This package requires an install location This is also the last piece of the live log. From that point on WinGetUI is unusable, as all other actions are waiting for this action to finish. There is no other window visible, where I could influence or cancel the installation. I need to kill the process tree or reboot the system to continue.

Updating this myself from commandline, the installer asks for the Location, where the update should be installed (question why? as it knows already that it is updateable). Entering the path, the update runs through.

[marticliment]

When trying to update it fails with a very cryptic information:

This issue is not related with WingetUI. In this case you should follow its instructions, since this is how Winget works

Trying to update AutoHotkey. The Installer starts, stops at 50% with the information: This package requires an install location

A fix is on its way

[Wosamarak]

This issue is not related with WingetUI. In this case you should follow its instructions, since this is how Winget works

I see it somehow related. WinGetUI reports, that this could be updated, which is not true.

For most of the reported errors, it would be very helpful, if I could find the full command line with all parameters, which caused this error. This would be a very first step to dig deeper. This should be part of the error description. By long lasting errors, like that one where the installer is waiting forever for an location path, there is the possibility to find the parameters with the help of process explorer.

[marticliment]

This issue is not related with WingetUI. In this case you should follow its instructions, since this is how Winget works

I see it somehow related. WinGetUI reports, that this could be updated, which is not true.

For most of the reported errors, it would be very helpful, if I could find the full command line with all parameters, which caused this error. This would be a very first step to dig deeper. This should be part of the error description. By long lasting errors, like that one where the installer is waiting forever for an location path, there is the possibility to find the parameters with the help of process explorer.

There's a planned feature that will log last X done installs/updates/uninstalls, to allow better debug.

Also, processes hanging will be fixed with winget 1.5, coming with WingetUI 2.0

[marticliment]

Hello,

The issue with process hanging has been fixed (the patch will be included with the next release). The issue was that the cancel button was not actually killing the hung process.

The Installation history feature also has been implemented