Skip to content

Commit c3fc2ac

Browse files
Merge pull request #6329 from MicrosoftDocs/main
Auto Publish – main to live - 2026-02-27 05:00 UTC
2 parents 05cb66f + c72c2a8 commit c3fc2ac

5 files changed

Lines changed: 5 additions & 1 deletion

File tree

-121 KB
Binary file not shown.
-34.1 KB
Binary file not shown.
Binary file not shown.
Binary file not shown.

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)