doc/windows/package-manager/winget/settings.md
The settings command of the winget tool allows you to customize your Windows Package Manager client experience. You can change defaults and try out experimental features that are enabled in your client. The settings command will launch your default JSON editor. Windows by default will launch Notepad as an option. We recommend using a tool like Visual Studio code.
You can easily install Visual Studio Code, by typing
winget install Microsoft.VisualStudioCode
Launch your default JSON editing tool: winget settings
When you launch the settings for the first time, there will be no settings specified. At the top of the JSON we provide a link to https://aka.ms/winget-settings where you can discover the latest experimental features and settings.
We have also defined a schema for the settings file. This allows you to use TAB to discover settings and syntax if your JSON editor supports JSON schemas.
The following settings are available for the 1.0 release of the Windows Package Manager.
The source settings involve configuration to the WinGet source.
"source": {
"autoUpdateIntervalInMinutes": 3
},
A positive integer represents the update interval in minutes. The check for updates only happens when a source is used. A zero will disable the check for updates to a source. Any other values are invalid.
To manually update the source use winget source update
The visual settings involve visual elements that are displayed by WinGet
"visual": {
"progressBar": "accent"
},
Color of the progress bar that WinGet displays when not specified by arguments.
The installBehavior settings affect the default behavior of installing and upgrading (where applicable) packages.
Some of the settings are duplicated under preferences and requirements. preferences affect how the various available options are sorted when choosing the one to act on. For instance, the default scope of package installs is for the current user, but if that is not an option then a machine level installer will be chosen. requirements filter the options, potentially resulting in an empty list and a failure to install. In the previous example, a user scope requirement would result in no applicable installers and an error.
Any arguments passed on the command line will effectively override the matching requirement setting for the duration of that command.
The scope behavior affects the choice between installing a package for the current user or for the entire machine. The matching parameter is --scope, and uses the same values (user or machine).
"installBehavior": {
"preferences": {
"scope": "user"
}
},
The locale behavior affects the choice of installer based on installer locale. The matching parameter is --locale, and uses bcp47 language tag.
"installBehavior": {
"preferences": {
"locale": [ "en-US", "fr-FR" ]
}
},
The telemetry settings control whether winget writes ETW events that may be sent to Microsoft on a default installation of Windows.
See details on telemetry, and our primary privacy statement.
"telemetry": {
"disable": true
},
If set to true, the telemetry.disable setting will prevent any event from being written by the program.
The network settings influence how winget uses the network to retrieve packages and metadata.
The downloader setting controls which code is used when downloading packages. The default is default, which may be any of the options based on our determination.
wininet uses the WinINet APIs, while do uses the
Delivery Optimization service.
"network": {
"downloader": "do"
}
To discover which experimental features are available, go to https://aka.ms/winget-settings where you can see the experimental features available to you.