-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Winget says package is already installed, when it isn't #3910
Comments
Are there any difference in Windows Apps & Feature via settings between how these two applications appear when they are installed? |
I see what's happening. The part in parenthesis is generally ignored. This is often a mechanism used to indicate scope or architecture but hasn't been reliable enough to use as authoritative since it's just a "displayName" field. WinGet would see both entries as the same package. It may be possible to add Apps and Features entries to the manifests to clearly differentiate the "displayName" properties. We've been discussing changing the default logic to include what is in parenthesis when the Apps and Features entries are present in the manifest. |
We've been working on the side-by-side scenarios. You could try the latest release and enable the experimental feature on: Please provide feedback at: |
Is this problem still occurring with WinGet 1.8? |
Brief description of your issue
2 flavors of FFmpeg cannot be installed alongside each other, but the error message doesn't make sense and is confusing.
Steps to reproduce
Expected behavior
Either both packages install, or the second command explains that
Gyan.FFmpeg.Shared
cannot be installed alongsideGyan.FFmpeg
(ideally, it would also explain thatGyan.FFmpeg.Shared
is a superset ofGyan.FFmpeg
, and propose to uninstallGyan.FFmpeg
automatically before installingGyan.FFmpeg.Shared
).Actual behavior
The second command just says the package is already installed, which is not true and confusing. What's particularly problematic to me, is that the commands use IDs, so it doesn't make sense to me that 2 packages with different IDs cause this behavior.
Environment
The text was updated successfully, but these errors were encountered: