-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Interactive installation parameter does not work #365
Comments
I don't understand the issue description to be honest. A silent (a.k.a unattended) installation is the opposite of an interactive installation. Are you asking to be able to provide some sort of parameter to the
|
winget install -? already documents a switch for interactive installations. For an MSI this is standard behavior to pass a /QN for silent installation or don't pass it for interactive. For EXE installers it's typically adding a /S or not. The following options are available: |
Ah, I had to read your last response and then your original issue a number of times to actually understand what you consider the problem. I would recommend updating your original issue description and title to more clearly describe the issue and provide a concrete test case. Title suggestion: |
I'm glad that you finally understand this simple problem. I think it was worded just fine but I updated it to try to make you happy. PS- I'm not sure why I would use winget show to manually download and install the MSI. That kind of defeats the purpose of winget doesn't it? |
To me the purpose of winget is to run unattended installations of libraries and applications. I might want to add additional parameters that I want to be passed to the embedded installer to customize the installation. In my opinion winget resembles a typical command line tool like homebrew, apt or chocolatey for which I never had the need to run an interactive setup. If I wanted an interactive installation I would not expect winget to do that for me - I'd grab the setup file and run it interactively completely bypassing winget. |
Unattended installations, e.g. as part of a batch file, are one usecase. But I see winget also as a tool for people that want to go through the normal installation wizard (e.g. to customize installation options) but that do not want to go through all the manual steps of searching the Internet first for the homepage, downloading the right installer, installing, deleting the installer, etc. |
Brief description of your issue
winget install -i for an MSI pkg doesn't provide an interactive experience.
Steps to reproduce
winget install -i iswix
I authored the iswix.msi and iswix winget-pkg. I simply provided the url to the installer and that it was type .msi. No arguments, -i and -s all provide a silent installation. I would expect winget-cli to automatically know how to set the MSI UILevel property since the command line help shows these options.
Expected behavior
I'd expect the installer to be called with UILevel 5 so that the MSI wizard loop to appear so I can do advanced selections.
Actual behavior
The resulting logfile shows UILevel is set to 2 whether I include the -i switch or not.
Environment
Windows: Windows.Desktop v10.0.19635.1
Package: Microsoft.DesktopAppInstaller v1.0.41331.0
The text was updated successfully, but these errors were encountered: