If you don’t, you can run winget install vscode. If you happen to have Visual Studio Code installed and configured, you also get the benefit of the JSON schema for tooltips and code completion. The Windows Package Manager settings file is opened with your default JSON editor when you run winget settings. Note: The following example shows an error that was intentionally forced to occur. Manifest authors can add a “ReturnResponseURL” to the array of “InstallerReturnCode” values. We’re hoping this will help with troubleshooting why something didn’t go quite right. We’ve added an enhancement to provide not only a standard error message, but now a URL can also be included. exe-based installers can provide custom responses for various failure scenarios. You can also pass “–display-notes” or “–suppress-notes” to override settings. You can add “suppressInstallNotes” as a setting to prevent them from being displayed. The default behavior is to display these notes. We’ve also added arguments and settings to manage these notes. Installation notes will be displayed after the package is installed. Some other packages have nuances related to what a user should understand before running them the first time. Most command-line packages require a terminal restart for the environment variables to be loaded. You will now be able to see the documentation and an associated URL when you run winget show. Some packages include documentation associated with a package version. Manifest Improvements Display Documentation And the Windows Package Manager now supports portable applications. The progress bar was improved with more fine-grained blocks. If you run winget -info the system architecture is now displayed. A new setting allows verbose logs to be on by default. We’ve enabled better package version reporting. The team has been adding several enhancements to manifests to improve your package installation experience. Today I get to announce Windows Package Manager 1.3 has been released.

Winget packages