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
Documentation when installer types change #4391
Comments
Would it also be a good idea to detect and inform the user what the other "installer technology" is, even if only possible part of the time? |
I'm open to that. I don't know users necessarily understand, but if we're linking to documentation with guidance they could certainly learn. WinGet does know the installer type for the currently installed version in almost every case, and it does know the new type based on the manifest for the newer version, otherwise the error message wouldn't be possible. |
I think it would go a long way. I don't have a problem with having to uninstall. I just have a problem with not knowing what the next step is. If I knew how something was installed, I'd have a better idea of what to do next |
When installer types change between versions of packages, WinGet displays:
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.
This causes users to be frustrated and or confused. Documentation should be added to Microsoft Learn for this case so users can be informed about the options, and the reasons for WinGet's behavior. In addition, an aka.ms URL should be added to the error message output so users can get more information and understand their options.
Originally posted by @denelon in #2155 (reply in thread)
The text was updated successfully, but these errors were encountered: