Microsoft is now releasing the Windows Package Manager version 1.4 (winget) with a slew of improvements and new features, such as support for zip-based packages, command aliases, and more.
Support for Winget zip files
The winget command now extracts and runs app installers (MSIX, MSI, and EXE) inside a ".zip" file, or installs many portable packages from the compressed file, according to the official announcement.
Aliases for command
This update includes commands that are more easily identifiable without being specific. For example, using the winget search vscode command is the same as using the winget search vscode command.
The available commands will be displayed when you run the winget command without arguments. The available aliases will also be displayed when you run the winget --help.
Changes to upgrade packages
In this release, there are a few additional enhancements to detect that a package was already installed and switch to the upgrade flow. If you don't want the upgrade, you may pass --no-upgrade.
Microsoft is changing the default behavior for upgrade packages that can be upgraded manually. If you run the winget upgrade --all command and one or more of these packages are encountered, they will be skipped. If you want to include them, use the --include-explicit option.
Winget's option to wait is activated.
When you run a script or debugging, Windows Package Manager version 1.4 includes the --wait option.
Final results from the winget show will include more manifest values, such as tags and purchase URLs.
The package manager is packaged with the operating system's App Installer application.
The Windows Package Manager is an open-source project, allowing other package managers to leverage the database of valid packages. Software vendors may also make apps available to users after their package manifests have been reviewed and accepted by Microsoft by using the free-source Microsoft Community Package Manifest Repository onGitHub.