Skip to content

Releases: microsoft/winget-cli

Windows Package Manager v0.3.11102 Preview

22 Apr 14:17
7c88074
Compare
Choose a tag to compare

This release includes the first stable release for the import command.

The Group Policy .admx and .adml files are also included in this release.

New Features

#220 Export/Import apps list - Import is now a default feature

Note

Binaries removed. We have discontinued support for versions of Windows 10 prior to version 1809.

Windows Package Manager v0.2.10971 Preview

15 Apr 00:47
82f994d
Compare
Choose a tag to compare

This release includes the initial implementations for group policy, user vs. machine scope, and search against a REST source.

Group Policy will be implemented via ADMX Ingestion. The .admx and .adml files will be provided in the next release of the Windows Package Manager preview.

Some packages support one or more installation scopes. Settings and a command line argument have been added to specify either "User" or "Machine" for manifests with the proper values and configuration. Additional details available in the PR #819 Settings and command line argument for specifying scope.

Third party repositories will be enabled via a REST API. This release includes the second round of implementation work which includes the ability to search for packages against a REST based source. A reference implementation will be provided in a different open-source repository in the coming months.

New Features

#154 Support for Group Policy Management
#149 User vs. System installation (non MSIX)
#118 Added Experimental support for Repository REST API

Note

Binaries removed. We have discontinued support for versions of Windows 10 prior to version 1809.

Windows Package Manager v0.2.10771 Preview

25 Mar 17:26
6e8a844
Compare
Choose a tag to compare

This release includes a few new features as well as some improvements and bug fixes.

The most noteworthy new experimental feature is winget import. You can pass a properly formatted JSON file using import, and the Windows Package Manager will install multiple packages with one command. Note: some packages trigger a reset in the shell or terminal so you will see an incorrect failure notification. In the event one of these packages is included in an import, the import command will not finish unless it is the last package installed.

Known packages are:

  • Microsoft.PowerShell
  • Microsoft.PowerShell-Preview
  • Microsoft.WindowsTerminal
  • Microsoft.WindowsTerminalPreview

Users can now opt-out of Windows Package Manager telemetry using winget settings. The Windows telemetry settings still take precedence if they are disabled.

The Windows Package Manager validation command has been updated to support the new v1.0 manifest schemas.

Some packages return a non-zero success code after the package has been installed. Once the v1.0 manifest schemas are in place, these non-zero success codes can be added to manifests and client will no longer report an install failure if one is returned.

New Features

#137 Support non-zero exit codes as success (requires manifest version 1.0)
#220 Added Experimental support to import multiple packages from a file
#279 Opt-Out of Telemetry
#740 Support for manifest v1.0 schema validation

Bug Fixes

#794 The Experimental Upgrade command now correctly selects the latest version of a package

Note

Binaries removed. We have discontinued support for versions of Windows 10 prior to version 1809.

Windows Package Manager v0.2.10191 Preview

28 Jan 19:36
c6091d3
Compare
Choose a tag to compare

This release includes the experimental uninstall command. Any application in Add/Remove Programs can be uninstalled. The experimental list feature also needs to be enabled to use winget uninstall.

Some workflow improvements were also made to this version to improve install success rates.

New Features

#121 Added Experimental support to uninstall an installed App

Improvements

#648 Workflow improvements to increase winget command success rate

Note

Binaries removed. We have discontinued support for versions of Windows 10 prior to version 1809.

Windows Package Manager v0.2.3162 Preview

02 Dec 00:02
bfbe3e6
Compare
Choose a tag to compare

This release improves the experimental list and upgrade commands by showing Add/Remove Programs (ARP) entries.

The default location for installer logs was moved to the same location as winget logs, thus allowing them to be collected by Feedback Hub. If you encounter a bug, just submit feedback [Windows]+[f] and the logs will be sent for us to be able to review what went wrong.

Trusted sources (like the Microsoft Community Package Manager Repository) will have downloaded files set to Zone 2. Other sources will have be set to Zone 3, and the file will be run through all local Anti-virus (AV) software by attachment execution services.

edit:

Here is what we do when downloading and executing an installer:

  1. Always set "Mark of the Web" with ZoneIdentifier URLZONE_INTERNET(3) when downloading the installer.
  2. Verify the installer SHA256
  • If the hash does not match: Leave "Mark of the Web" at URLZONE_INTERNET(3)
  • If the hash matches:
    • If the installer is from a trusted source, modify "Mark of the Web" to ZoneIdentifier URLZONE_TRUSTED(2)
    • If the installer is from an untrusted source, call Attachment Execution Service to trigger anti virus and determine ZoneIdentifier

Note

Binaries removed. We have discontinued support for versions of Windows 10 prior to version 1809.

Windows Package Manager v0.2.2941 Preview

29 Oct 21:06
7ee6784
Compare
Choose a tag to compare

The reference to the JSON schema has been added to the default schema (for new installs only). You can add the following line to your settings file after the first open curly brace "{"

"$schema": "https://aka.ms/winget-settings.schema.json",

If you are using Visual Studio Code, you will see support for the JSON settings. We also fixed a bug affecting the layout of extended characters.

We're working on list and upgrade. They are available as experimental features, but they are not complete. List will display MSIX Apps regardless of how they were installed on the system. Upgrade has meta-data dependencies in the manifest. Without "PackageFamilyName" and "ProductCode" in the manifest, no upgrades will show as available.

Once list is complete, it will show all applications installed on your system. It may also help determine the proper values to add for "PackageFamilyName" and "ProductCode".

We have also added the file "Microsoft.DesktopAppInstaller.SHA256.txt" to this release. It contains the SHA256 for the appxbundle in this release. We are doing this as an example of how we might support #568 "Include checksums in the GitHub releases".

New Features

#119 Added Experimental support for List Installed Apps
#120 Added Experimental support to Upgrade an Installed App

Bugs

#562 Fix alignment of table output with extended characters

Note

Binaries removed. We have discontinued support for versions of Windows 10 prior to version 1809.

Windows Package Manager v0.2.2521 Preview

14 Sep 20:57
Compare
Choose a tag to compare

Experimental support for a curated list of store apps for developers.

New Features

#535 Replace yaml-cpp with libyaml
#544 Add pre-indexed Microsoft Store source

winget features will show the status of the Microsoft Store Support.
winget settings will launch the settings file in your default JSON editor.

Add the following code block to your settings file and the store source will be added

{
    "experimentalFeatures": {
        "experimentalMSStore": true
    }
}

Windows Package Manager v0.1.42241 Preview

20 Aug 23:04
f52472a
Compare
Choose a tag to compare

In this release, you get PowerShell [tab] autocomplete.
When multiple sources are present, search will look across them. (This is in anticipation of support for store apps.)

New Feature

#146 Autocomplete [tab] winget commands in PowerShell

You will need to modify your PowerShell $PROFILE to get this to work following these instructions.

Windows Package Manager v0.1.42101 Preview

29 Jul 17:27
ccc2861
Compare
Choose a tag to compare

This update will allow you to:
winget install git or winget install powershell

The default behavior for the commands above requires a case insensitive match with a package by Id, Name, or Moniker. If you specify which field with an argument, you can make it even more specific. You can use the show command to play around with it as it uses the same semantics to find a package without the need to cancel the install.

We've also added a feature toggle mechanism so you can enable or disable experimental features.
winget features will provide a list of features and their status

The first bit of work towards installing apps from the Microsoft Store has started.

Features

#460 Feature toggle
#493 Implement store app installation from manifest

Bug Fixes

#292 winget should install an app if there is an exact match (eg 'git')
#481 Further source integrity checks
#488 Enable Control Flow Guard
#482 Block elevated process from overriding hash mismatch
#492 Change show and install to use a narrower search

Windows Package Manager v0.1.41821 Preview

10 Jul 01:11
2ae5b9c
Compare
Choose a tag to compare

This update includes a new configuration mechanism, a few bug fixes, and some security improvements. We've also started making improvements for non-ASCII characters in paths.

A special shout out to @philipcraig, @edjroot, @bnt0, @danielchalmers, @superusercode, @doppelc, @sachinjoseph, @ivan-kulikov-dev, @chausner, @jsoref, @DurableMicron, @Olifant1990, @MarcusP-P, @himejisyana, & @dyl10s (in order of appearance).

Features

Settings command #396

winget settings

Bug Fixes

Program names seem to be case sensitive #252
Interactive installation parameter does not work #365