Microsoft has announced the availability of WinGet 1.4. This update has notable zip support that can automatically extract and install installation packages from zipped folders. Installer packages that are supported are MSIX, MSI, and EXE. This The release also includes new command aliases for those more familiar with other command line tools.
Here’s what’s new in Windows Package Manager (OneGet) 1.4:
Improvements to WinGet show
Some other visible values such as tags and purchase URL were added to the output (if they exist). The Wingate Show . Below I have an example running. Wingate Show Oh My Posh Wingate. Since Oh My Posh is available in both the Microsoft Store and the Windows Package Manager Community Repository, I limited the results to the “wingate” source. If you like the colorful display in my prompt, this is the prompt theme engine I’m using.
Muscle memory can be difficult to overcome. If you’ve ever tried typing “dir” on a Linux system or “ls” on Windows, you know what I mean. WinGet has added several new command aliases that may help a bit. when you run Wingate With no arguments, the default help displays the available commands. If you drill while running a bit. winget –help You will see if an alias is available. Below, you can see that “Search” has an alias. Other command aliases are included. add To install, update For upgrade, far off And rm To uninstall, ls For the list, and formation for settings.
As you might expect, you can now run. Search for winget vscode. and the same output appears as if you had run Wingt search vscode.
Note: The results displayed when searching the Windows Package Manager Community Repository are ordered on a “best match” basis. WinGet evaluates names, identifiers, monikers, and tags. They are also more comprehensive than “show” where WinGet is trying to find a perfect match to use for the install.
Install/upgrade flow enhancements.
Some packages require an explicit argument to upgrade. This was causing the winglet to fail if a user ran away. Install winget And the package was already installed on the machine. We’ve added some extras to detect if a package is already installed and switch to the upgrade flow. If you don’t want the upgrade, you can pass. –No upgrade.. This is most commonly encountered in cutting scenarios. We’ve also noticed that many packages can upgrade themselves, so our default behavior is to allow them to do so. If you run winget upgrade –all And if one or more of these packages are encountered, they will be dropped. If you want to add them, just add them. –include-clear.
WinGet now supports installing packages inside a .zip archive. This feature builds on existing support for portable packages, and existing installer support for MSIX, MSI, and EXE-based installers. Our initial support includes either an installer, or (one or more) portable package(s). We’ve kept issues and PRs (Pull Requests) open on GitHub and added the “.zip” label to them. Once this release hits the majority of supported Windows systems, we will begin validating existing PRs and accepting new ones.
Wait, there’s more. (I couldn’t help myself) Sometimes when you’re scripting, or debugging things, you need a prompt. It can be quite frustrating to show some text in a terminal window and then have it disappear before you’ve read everything. Just add. —wait.