TheITCloudGuy
commented
2 years ago Same issue here.
Location: UK
Open tranquilcarbon opened 2 years ago
TheITCloudGuy
commented
2 years ago Same issue here.
Location: UK
tranquilcarbon
commented
2 years ago Same issue here.
Location: UK
perhaps this is a issue with something in the UK, does winget use region specific servers or something like that?
additionally, i have attached a screenshot, in case this helps.
LukasDotEU
commented
2 years ago Same issue here in Germany since more than a week i think.
(basically the same just with German language)
since i am in Germany it is probably not an issue regarding something in the UK
szlevi
commented
2 years ago Yeah, I don't think it is country-specific - I'm in NYC and it's completely broken here too:
Not only that, but it also mis-detects the version to be 7.2.5.0 when I actually have 7.3.0 installed for some time now...
irzyxel
commented
2 years ago having that problem for a long time. winget upgrade lists a package. but then it doesnt upgarde, neiter by using --all nor by using any variant of its name. after a couple of days it usually works.
PS C:\Users\Michael> winget upgrade
Name ID Version Verfügbar Quelle
------------------------------------------------------------------------------
LibreOffice 7.4.2.1 TheDocumentFoundation.LibreOffice 7.4.2.1 7.4.2.3 winget
1 Aktualisierungen verfügbar.
1 Paket hat eine Versionsnummer, die nicht bestimmt werden kann. Wenn Sie „--include-unknown“ verwenden, werden möglicherweise weitere Ergebnisse angezeigt.
PS C:\Users\Michael> winget upgrade Libreoffice
Es wurden keine anwendbaren Aktualisierungen gefunden.
PS C:\Users\Michael> winget upgrade TheDocumentFoundation.LibreOffice
Es wurden keine anwendbaren Aktualisierungen gefunden.
PS C:\Users\Michael> winget upgrade --all
Name ID Version Verfügbar Quelle
------------------------------------------------------------------------------
LibreOffice 7.4.2.1 TheDocumentFoundation.LibreOffice 7.4.2.1 7.4.2.3 winget
1 Aktualisierungen verfügbar.
1 Paket hat eine Versionsnummer, die nicht bestimmt werden kann. Wenn Sie „--include-unknown“ verwenden, werden möglicherweise weitere Ergebnisse angezeigt.
PS C:\Users\Michael>
SamaelAmbrona
commented
2 years ago I have same issue with a couple of packages. In the beginning I was able to solve the issue by uninstalling the package and install it again with Winget but after a couple of updates it fails again
szlevi
commented
2 years ago In addition, I just discovered my PuTTY was removed - is it possible that, while failing to install the new one, winget first did successfully remove my existing version? If so, that's very much not cool...
mdanish-kh
commented
2 years ago In addition, I just discovered my PuTTY was removed - is it possible that, while failing to install the new one, winget first did successfully remove my existing version? If so, that's very much not cool...
@szlevi Please note that this was done intentionally to align with the publisher's changelog:
Note: installing the 0.78 or later Windows installer will not automatically uninstall 0.77 or earlier, due to a change we've made to work around a bug. We recommend uninstalling the old version first, if possible. If both end up installed, uninstalling both and then re-installing the new version will fix things up.
Please see https://github.com/microsoft/winget-pkgs/pull/87021
szlevi
commented
2 years ago In addition, I just discovered my PuTTY was removed - is it possible that, while failing to install the new one, winget first did successfully remove my existing version? If so, that's very much not cool...
@szlevi Please note that this was done intentionally to align with the publisher's changelog:
Note: installing the 0.78 or later Windows installer will not automatically uninstall 0.77 or earlier, due to a change we've made to work around a bug. We recommend uninstalling the old version first, if possible. If both end up installed, uninstalling both and then re-installing the new version will fix things up.
Please see microsoft/winget-pkgs#87021
Ah, I see, thanks. So it's just a temp issue, right?
mdanish-kh
commented
2 years ago Ah, I see, thanks. So it's just a temp issue, right?
That depends on the publisher. If future installers perform "in-place" upgrade instead of requiring the version to be manually uninstalled first, the behavior will be duly updated in the winget's manifest.
tranquilcarbon
commented
1 year ago i've found another package that has the same issue, the microsoft visual C++ redistributable 2013, specifically the x64 version has the issue, not the x86 version which updated fine. can we have a developer explain why this issue is appearing?
denelon
commented
1 year ago The matching logic is based on comparing what values are written to the registry (it's the same thing that powers what you see in Windows Apps & Features), and what metadata is listed in manifests in all configured sources. Sometimes the installer isn't reporting things consistently to the registry and in other cases, the manifest doesn't have all the variations of what is reported.
WinGet looks at package family name, product code, upgrade code, display name, and display version. Depending on what is available, heuristics are used to determine the "best match" when there isn't an exact match.
As the Visual C++ Redistributable packages can be installed side-by-side for different versions and different architectures, it's been more challenging to capture all the correct metadata for all the variations. We are incrementally making improvements with both the manifests and the client (matching logic and upgrade/install logic), but clearly there is still more work to be done.
irzyxel
commented
1 year ago without any known changes, libreoffice today suddenly updated just fine. 7.4.2.1 -> 7.4.2.3
xd003
commented
1 year ago Facing this very same issue while upgrading Powershell, i don't know yet if this happens only with certain packages
denelon
commented
1 year ago There are a couple of classes of issues. One is when the installer type has changed. For the most part, I think we've isolated that path and resolved it.
Another is when it's an MSI based installer and we aren't getting a good match for the "Product Code" or "Upgrade Code".
Another is when the package is installed in either "user" or "machine" scope and the upgrade is defaulting to the opposite scope, or the user has a requirement in their settings which doesn't match the installed scope or the default scope specified in the manifest.
Trenly
commented
1 year ago [Policy] Command-Upgrade
erickvelasco11
commented
1 year ago Hi everyone, I'm from Colombia and I'm getting the same issue.
I have solved it adding flag --include-unknown
As my understanding, when the winget command try to get the apps to update, there are some packages with a "Broken" version in the repository. I don't understand the consecuences of upgrade with --include-unknown flag, but it works for me.
winget upgrade --all --include-unknown
pplmx
commented
1 year ago Encounter the same issue:
xd003
commented
1 year ago Still facing this issue even now :/
lreynolds1989
commented
1 year ago I'm getting the same issue after successfully upgrading about 4-5 apps, then none would upgrade after that and I was met with the "no installed package found matching input criteria." message when trying to upgrade any of the 7 that remained.
I done some googling (as you do) and tried with a slightly different command syntax, instead of specifying the ID I just specified the name of the application.
So instead of winget upgrade --id VideoLAN.VLC I tried winget upgrade "VLC Media Player"
This appeared to work, at least for VLC Media Player.
I'm really not sure of the implications of doing it this way, I'm not sure if my Winget just had a temporary issue and it would have worked using the original commands eventually (as others have mentioned on google)
lreynolds1989
commented
1 year ago Exactly same behaviour for Git, specifying it by ID did not work, specifying it by the Name did work. Very odd!
BartJolling
commented
1 year ago I got the same issue running the winget upgrade -all command from an elevated PowerShell. But it worked when I ran it in a non-elevated cmd.exe. Real PITA having to type my admin user and password for every single update
jonkeren
commented
1 year ago FYI, upgrade worked here for Microsoft .NET SDK 7.0.203 (x64) (to version 7.0.401) -- by not using the app Id (in this case Microsoft.DotNet.SDK.7), but by entering the complete name between quotes.
Like so winget upgrade "Microsoft .NET SDK 7.0.203 (x64)". You may even have to do a --force.
JJ
TUNlX
commented
1 year ago Same issue here
winget upgrade
No installed package found matching input criteria.
WinGet-2023-09-17-21-45-02.112.log
winget upgrade --all
No installed package found matching input criteria.
Tried resetting winget as described here, but no luck. Tried re-installing winget, no luck.
Using cmd instead of Powershell or running them with or without admin rights as suggested by @BartJolling did not help either.
winget --info
Windows Package Manager v1.6.2561
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.19045.3448
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.21.2561.0```
huskylogic
commented
1 year ago I know it's an old thread, but I was having this issue as well. I solved it by running these two commands.
winget uninstall Microsoft.Winget.Source_8wekyb3d8bbwe winget source reset --force
sh0ou
commented
1 year ago I have same issue for VLC Media Player (VideoLAN.VLC) .
ELFswe
commented
1 year ago I have same issue for VLC Media Player (VideoLAN.VLC) .
Same here. I got it working by doing what @jonkeren wrote in his post (https://github.com/microsoft/winget-cli/issues/2686#issuecomment-1721441017)
Use the name instead of the id.
GingerGraham
commented
1 year ago Just to note I'm seeing the same behaviour with winget install on a clean Windows 11 (reset) build. I've got a script with a number of packages to install based on the ID and it just loops this error for all of them
toarujs
commented
11 months ago this error also occurs when updating .net and anaconda
ztrhgf
commented
11 months ago Any update on this issue? Same for SSMS. And using a name instead of ID is nice as a workaround, but not as a fix :(
JoydeepMallick
commented
9 months ago I know it's an old thread, but I was having this issue as well. I solved it by running these two commands.
winget uninstall Microsoft.Winget.Source_8wekyb3d8bbwe winget source reset --force
Thanks, it worked finally😱
This thing had been bugging me since 2021 with similar issues for it being present but no progress. ✔
One thing is that the winget source reset --force needs to run in elevated prompt meaning cmd/powershell with administrative privileges that it👍🏼
cmd or powershell with admin rights :-winget uninstall Microsoft.Winget.Source_8wekyb3d8bbwe
winget source reset --forceOn reset windows ask to accept the agreement that it will detect location, accept it and that is it.
Is there any plan to revive appget?
yg-i
commented
7 months ago I find that I only run into this problem when upgrading the runtimes of programming languages, e.g. Julia and Racket. The reason appears to be that when winget upgrades those packages, winget (or rather, the installers for those runtimes) by default installs the new version side by side with the old version (see screenshot below), in a different folder. Which of course make sense for runtimes (it's not uncommon to run into, say, python scripts that will run on 3.11 but not 3.10). But this also means that, even after a successful upgrade, the old version of the runtime continues to exist and so will continue to show up in the output of winget list --upgrade-available! This also explains why winget upgrade {app id} causes no installed package found ...: you already have the latest version of {app id} installed.
The solution is to use --uninstall-previous when doing winget upgrade for this kind of package if you want the new version to replace the old version.
shablin
commented
6 months ago getting the same one when I try to remove WSL distro
jazzydog
commented
6 months ago In my case, it's was net problem.
FaserF
commented
5 months ago Same issue here:
08:07:03 - Updating Remote Desktop from 1.2.5326.0 to 1.2.5405.0... 08:07:03 - ########## WINGET UPGRADE PROCESS STARTS FOR APPLICATION ID 'Microsoft.RemoteDesktopClient' ########## 08:07:03 - -> Running: Winget upgrade --id Microsoft.RemoteDesktopClient -e --accept-package-agreements --accept-source-agreements -s winget -h
██▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ 1024 KB / 10.8 MB █████▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ 2.00 MB / 10.8 MB ████████▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ 3.00 MB / 10.8 MB ███████████▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ 4.00 MB / 10.8 MB █████████████▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ 5.00 MB / 10.8 MB ████████████████▒▒▒▒▒▒▒▒▒▒▒▒▒▒ 6.00 MB / 10.8 MB ███████████████████▒▒▒▒▒▒▒▒▒▒▒ 7.00 MB / 10.8 MB ██████████████████████▒▒▒▒▒▒▒▒ 8.00 MB / 10.8 MB ████████████████████████▒▒▒▒▒▒ 9.00 MB / 10.8 MB ███████████████████████████▒▒▒ 10.0 MB / 10.8 MB ██████████████████████████████ 10.8 MB / 10.8 MB No installed package found matching input criteria.
Dayflare
commented
5 months ago i have the same issue with the package Lenovo.DockManager
Log:
Executing C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_1.24.1763.0_x64__8wekyb3d8bbwe\winget.exe install --id Lenovo.DockManager --custom '/noicons /noui' --silent --accept-package-agreements --accept-source-agreements --scope machine
Handles NPM(K) PM(K) WS(K) CPU(s) Id SI ProcessName
------- ------ ----- ----- ------ -- -- -----------
31 10 440 2516 0,05 5012 0 winget
-
\
████████████▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ 1024 KB / 2.39 MB
█████████████████████████▒▒▒▒▒ 2.00 MB / 2.39 MB
██████████████████████████████ 2.39 MB / 2.39 MB
-
No package found matching input criteria.
Script Finishedwinget source reset doesn't help. When i search the name instead of the id it works. This should be fixed.
JoydeepMallick
commented
5 months ago winget source reset doesn't help. When i search the name instead of the id it works. This should be fixed.
Did you apply the --force flag, my issue was related to updates and packages and on adding force flag it did work as I said here https://github.com/microsoft/winget-cli/issues/2686#issuecomment-1933740296
Dayflare
commented
5 months ago winget source reset doesn't help. When i search the name instead of the id it works. This should be fixed.
Did you apply the
--forceflag, my issue was related to updates and packages and on adding force flag it did work as I said here #2686 (comment)
yea, i tried it exactly like this:
winget uninstall Microsoft.Winget.Source_8wekyb3d8bbwe
winget source reset --forceI tried the package with --force too, but didn't worked. Tried it with --moniker lenovo-dock-manager, didn't work. It only works by Name "Lenovo Dock Manager". Why have an unique ID when i can't query it?
edit: when installing the package by Name "Lenovo Dock Manager" i can't use the --custom parameter so this is not a workaround for me
JoydeepMallick
commented
5 months ago Why have an unique ID when i can't query it?
Strange enough😐.
o-l-a-v
commented
3 months ago Just faced this now with VideoLAN.VLC.
PS > winget upgrade
Name Id Version Available Source
------------------------------------------------------
VLC media player VideoLAN.VLC 3.0.20 3.0.21 winget
1 upgrades available.
5 package(s) have pins that prevent upgrade. Use the 'winget pin' command to view and edit pins. Using the --include-pinned argument may show more results.
PS > winget upgrade --silent --id VideoLAN.VLC
No installed package found matching input criteria.
PS > winget --version
v1.8.1911
PS >Verbose logs:
I then uninstalled VLC with Geek Uninstaller. Then:
ps > winget install --silent --id VideoLAN.VLC --version 3.0.20
Found VLC media player [VideoLAN.VLC] Version 3.0.20
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://download.videolan.org/videolan/vlc/3.0.20/win64/vlc-3.0.20-win64.msi
██████████████████████████████ 56.2 MB / 56.2 MB
Successfully verified installer hash
Starting package install...
Successfully installed
PS > winget upgrade
Name Id Version Available Source
-------------------------------------------------------
VLC media player VideoLAN.VLC 3.0.20.0 3.0.21 winget
1 upgrades available.
5 package(s) have pins that prevent upgrade. Use the 'winget pin' command to view and edit pins. Using the --include-pinned argument may show more results.
PS > winget upgrade --silent --id VideoLAN.VLC
A newer version was found, but the install technology is different from the current version installed. Please uninstall the package and install the newer version.
PS >Verbose logs:
Related:
bferg317
commented
3 weeks ago I can't be the only one who has never--not one single time--been able to update PowerShell Core with winget, despite only ever installing it from winget.
I also cannot be the only one who sees the very Microsoft-flavored irony in that. Glad I can update foobar2000, though. Music is a great cope.
JoydeepMallick
commented
3 weeks ago I can't be the only one who has never--not one single time--been able to update PowerShell Core with winget, despite only ever installing it from winget.
Did 👉🏼https://github.com/microsoft/winget-cli/issues/2686#issuecomment-1933740296 work for you???
You problem seems similar to mine, after resetting things just started working fine!!! Strange enough.
Brief description of your issue
when i run winget upgrade, several programs have updates. for some, such as mozilla thunderbird, attempting to run the update causes a "No installed package found matching input criteria." error.
if i uninstall the program and reinstall using winget, it works find however.
example command: winget upgrade Mozilla.Thunderbird
Steps to reproduce
use command winget upgrade Mozilla.Thunderbird on version 102.4.1. it might appear.
Expected behavior
winget begins to upgrade the application
Actual behavior
winget throws a error "No installed package found matching input criteria."
Environment