Skip to content

Commit 3e1c165

Browse files
Merge pull request #5837 from DandelionSprout/patch-3
Reflecting recent changes about installerTypes from https://github.com/microsoft/winget-cli/blob/master/doc/Settings.md
2 parents 05cb66f + b98d339 commit 3e1c165

1 file changed

Lines changed: 5 additions & 1 deletion

File tree

hub/package-manager/winget/settings.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -191,7 +191,11 @@ The `architectures` behavior controls what architectures will be selected when i
191191

192192
#### installerTypes
193193

194-
The `installerTypes` behavior controls what installer types will be selected when installing a package. The matching parameter is `--installer-type`.
194+
The `installerTypes` behavior affects what installer types will be selected when installing a package. It can also determine which type to install by default if a manifest has multiple types: The list is in priority order, with the first listed type being preferred over the others, and so on. This is convenient for users who for instance prefer portable packages or MSIX/AppX installations. The matching parameter is `--installer-type`, which will override the settings.
195+
196+
Allowed values as of version 1.12.470 include: `appx`, `burn`, `exe`, `font`, `inno`, `msi`, `msix`, `msstore`, `nullsoft`, `portable`, `wix`, `zip`
197+
198+
By default, and with all other properties being equal, WinGet defaults to the installer type that is listed first in the manifest's installer YAML if the package has not been installed yet. If it is already installed, the same installer type will be required to ensure a proper upgrade.
195199

196200
```json
197201
"installBehavior": {

0 commit comments

Comments
 (0)