Winget upgrade package, No applicable update found #1191
Comments
|
Hmmm, i can't replicate this.. |
|
Here my output
|
|
I can confirm that I am affected by the same issue. |
|
@denelon you might not want to move every subject about this to the Package Repo when it points to a issue with winget-cli |
|
@OfficialEsco I'm trying to balance which ones can be addressed with the package metadata vs. closing them as duplicates. Do you think this one belongs in CLI? |
|
As i said i cannot replicate this with a clean install, therefore there is no issue on the Package side and there most be a bug with the CLI as this have been reported since |
ghost
added
the
denelon
added
Issue-Bug
|
This issue might be related to winget-pkgs I was able to replicate this issue by installing old version of Firefox using WinGet's Firefox manifest only contains msi installer so that might be the issue. |
|
@KaranKad thanks for figuring this one out. We do try to avoid updating a package with a different "InstallerType". |
|
winget CLI need to explain this instead of |
only installed it from winget. as others in the screenshot. |
|
@denelon It actually does not upgrade even if previously installed using |
|
@KaranKad I've just tested that. reults the same. it might the issue with cli. |
|
And |
|
Can actually confirm this is happening on a PC which i installed Firefox on via Winget before, the issue might be the ProductCode on the Firefox MSI installer which is not changing? |
|
Somehow the winget has this problem when the app doesn't provide the version number to windows. Or is it just me?
|
|
7-Zip has this problem: |
|
Currently only the EXE is released. |
This shouldn't be a problem right? Reinstalling does work btw |
According to that commit you should be asked if you want to replace the MSI with the EXE, however its not even implemented in version |
|
Any update yet? I'm facing the same issue... |
|
These issues should be worked around in https://github.com/microsoft/winget-cli/releases/tag/v1.3.431 |
This doesn't appear to have fixed yet.... |
|
I can’t seem to find that package mentioned in this thread but it looks like a easy fix (will make a Fix PR in about 1h) For any future relevant issues/info please read my comment from a different thread #752 (comment) Edit: Apparently its not as simple because i've found a new issue 😁 microsoft/winget-pkgs#47777 |
|
So go 1.18 is out and winget does show 1.18 with search command. But cannot upgrade. [interesting] (as it's more verbose and easier to type plus more programming like than emoji) |
|
This is still an issue |
|
Please provide more details in the error message when winget thinks it can't update (like "app was installed manually; please uninstall, first"). |
|
I have the same issue "No applicable update found." for the package PostgreSQL.PostgreSQL. |
|
@lmachegger you have PostgreSQL 9.5 installed somewhere else on your computer and/or remaining registry strings from PostgreSQL 9.5. However we could probably split the major versions into different folders(packages) as they can be installed side by side Use RevoUninstaller to actually get a clean install. |
|
Also same issue with trying to update MS VCRedist: |
|
The same problem with winget upgrade Name Id Version Available SourceGoogle Chrome Google.Chrome 60.0.3112.78 108.0.5359.125 winget |
|
Or another issue winget upgrade --id="Nvidia.GeForceExperience" -e winget upgrade --id="Nvidia.GeForceNow" -e Buit winget upgrade shows that nothing changed! |
|
If you are trying to upgrade PowerShell and you use the Terminal application, it is possible that winget installs are being downloaded - but are being stored in the Terminal application as an additional profile. This is what happened to me. I installed an updated PowerShell and the $PSVersionTable command kept returning the same 5.XX version after I used winget to upgrade to 7.XX. I think it'll be sooooo awesome if MS consolidated all CLI to the Terminal application 🙃. If not possible, at least integrate the products a bit better. As of right now - Terminal, Powershell, Powershell Preview all seem to behave somewhat independently. |
|
The PowerShell that you download and install has to be separate from the in-box version because they are managed, updated, and handled in general differently from each other. |
|
This still seems to be a problem: |
|
I was having this issue with the Microsoft Visual C++ 2013 Redistributable (x86) package. I figured out that winget was correctly showing that the package had an available upgrade, but it was showing the wrong id when listing the available upgrades. It was using the id of the x64 version, which was already upgraded. Once I used the correct id, the problem was solved. PS C:\> winget upgrade Name Id Version Available Source ----------------------------------------------------------------------------------------------------------------------- Windows PC Health Check Microsoft.WindowsPCHealthCheck 3.1.2109.29003 3.7.2204.15001 winget Microsoft Visual C++ 2013 Redistributable (x86) - … Microsoft.VCRedist.2013.x64 12.0.30501.0 12.0.40664.0 winget 2 upgrades available. PS C:\> winget list Microsoft.VCRedist.2013 Name Id Version Available Source ----------------------------------------------------------------------------------------------------------------------- Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.40… Microsoft.VCRedist.2013.x64 12.0.40664.0 winget Microsoft Visual C++ 2013 Redistributable (x86) - 12.0.30… Microsoft.VCRedist.2013.x86 12.0.30501.0 12.0.40664.0 winget |
|
Hey all, this issue was closed. Take a look at open Issues with the "Area-Matching" label to see current gaps and work in progress. |
Check this out :- #2686 This command did help me:- winget uninstall Microsoft.Winget.Source_8wekyb3d8bbwe
winget source reset --force |
and others
Brief description of your issue
if i run
winget upgraded packagename& update available, it should update the package but it shows No applicable update found even though it's showing the newer version available.Steps to reproduce
winget upgradelist of the available updateswinget upgrade --allorwinget upgrade Python.Python.3Expected behavior
It should update the actual selected package or all incase of
--allActual behavior
throws
No applicable update foundand if i runwinget install packagenamethen installs the update.Environment
Windows 10 Enterprise 21H1 build 19043.1055
Experience Pack 120.2212.2020.0
The text was updated successfully, but these errors were encountered: