WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface).
MIT License
Bot releases are hidden (Show)
Published by ryfu-msft over 1 year ago
This release is the second stable release of Windows Package Manager 1.4 for Windows 10 (1809+) and Windows 11.
This release contains a minor servicing fix related to refreshing store source certificates. The Microsoft.WinGet.Client PowerShell module has been published to the PowerShell Gallery and will no longer be included in releases.
m_summary
in the global globals for telemetry by @florelis in https://github.com/microsoft/winget-cli/pull/2820
ms-windows-store
link not rendered in md by @iamCristYe in https://github.com/microsoft/winget-cli/pull/2403
RequireExplicitUpgrade
manifest element by @florelis in https://github.com/microsoft/winget-cli/pull/1795
UpgradeCode
for matching MSI apps by @florelis in https://github.com/microsoft/winget-cli/pull/2418
$schema
to cgmanifest.json
by @JamieMagee in https://github.com/microsoft/winget-cli/pull/2487
source ls
alias for source list
by @florelis in https://github.com/microsoft/winget-cli/pull/2736
pin
command by @florelis in https://github.com/microsoft/winget-cli/pull/2733
--force
by @Trenly in https://github.com/microsoft/winget-cli/pull/2622
Workflow.cpp
into multiple files by @florelis in https://github.com/microsoft/winget-cli/pull/2773
Full Changelog: https://github.com/microsoft/winget-cli/compare/v.1.3.1611...v1.4.11071
Published by ryfu-msft over 1 year ago
This is the fourth development build after the Windows Package Manager 1.4 build for Windows 10 (1809+) and Windows 11. This build will be released to Windows Insider Dev builds and Windows Package Manager Insiders.
Experimental features are enabled in this release. Run winget features
to see which experimental features are enabled or disabled. Add the following to your settings (winget settings
) file to enable the experimental features including package pinning, and WinGet configuration:
"experimentalFeatures": {
"pinning": true,
"dependencies": true,
"directMSI": true,
"uninstallPreviousArgument": true,
"configuration": true,
"windowsFeature": true,
},
Windows Package Manager now includes Winget configuration, which automatically handles the setup and configuration requirements for an ideal development environment on your Windows machine. WinGet configuration file helps with installing and managing software packages, applications, programming languages, frameworks, tools, or settings necessary for a project.
Check out our session at Microsoft Build to learn how to get your machine to a ready-to-code state.
A prerelease version of the Microsoft.WinGet.Client PowerShell module has been published to the PowerShell Gallery and will no longer be included as a release asset. To install the latest version of the PowerShell module, run the following command in PowerShell 7+.
Install-Module -Name Microsoft.WinGet.Client
Additional fixes are also included in this release to address minor issues with pinning, COM apis, and PowerShell module behavior.
upgrade --include-pinned
by @florelis in https://github.com/microsoft/winget-cli/pull/3173
Full Changelog: https://github.com/microsoft/winget-cli/compare/v1.5.1081-preview...v1.5.1361-preview
Published by ryfu-msft over 1 year ago
This is the third development build after the Windows Package Manager 1.4 build for Windows 10 (1809+) and Windows 11. This build will be released to Windows Insider Dev builds and Windows Package Manager Insiders.
Experimental features are enabled in this release. The experimental feature for enabling Windows Features is now supported and included in this release. You can now specify the Windows feature name (i.e. netfx3) you want to enable in the WindowsFeature field in your installer manifest.
Run winget features
to see which experimental features are enabled or disabled.
Add the following to your settings (winget settings
) file to enable the experimental features including package pinning:
"experimentalFeatures": {
"pinning": true,
"dependencies": true,
"directMSI": true,
"uninstallPreviousArgument": true,
"windowsFeature": true,
},
This release makes improvements to the overall user experience of WinGet with improvements to package correlation, COM APIs, logging/output, and Portable installation. This release also includes an early preview of our Microsoft.WinGet.Client PowerShell module. Information about getting started and usage can be found here.
No installed package matching the input criteria was found
in upgrade flow by @Trenly in https://github.com/microsoft/winget-cli/pull/2877
Full Changelog: https://github.com/microsoft/winget-cli/compare/v1.5.441-preview...v1.5.1081-preview
Published by ryfu-msft over 1 year ago
This is the second development build after the Windows Package Manager 1.4 build for Windows 10 (1809+) and Windows 11. This build will be released to Windows Insider Dev builds and Windows Package Manager Insiders.
Experimental features are enabled in this release. The experimental feature for package pinning is now supported and included in this release.
Run winget features
to see which experimental features are enabled or disabled.
Add the following to your settings (winget settings
) file to enable the experimental features including package pinning:
"experimentalFeatures": {
"pinning": true,
"dependencies": true,
"directMSI": true,
"uninstallPreviousArgument": true,
},
This release includes an early preview of our Microsoft.WinGet.Client PowerShell module. Improvements to the PowerShell module have been made in this release to enhance the output of the cmdlets. Information about getting started and usage can be found here.
Full Changelog: https://github.com/microsoft/winget-cli/compare/v1.5.101-preview...v1.5.441-preview
Published by ryfu-msft almost 2 years ago
This release is the first stable release of Windows Package Manager 1.4 for Windows 10 (1809+) and Windows 11.
This release also includes a preview of our Microsoft.WinGet.Client PowerShell module. Information about getting started and usage can be found here.
Note: The Windows Package Manager Community Repository does not accept zip applications. They will not be accepted until after 1.4 is Generally Available and has been rolled out to the majority of Windows systems via the automatic upgrade from the Microsoft Store. Users may test with local manifests.
m_summary
in the global globals for telemetry by @florelis in https://github.com/microsoft/winget-cli/pull/2820
ms-windows-store
link not rendered in md by @iamCristYe in https://github.com/microsoft/winget-cli/pull/2403
RequireExplicitUpgrade
manifest element by @florelis in https://github.com/microsoft/winget-cli/pull/1795
UpgradeCode
for matching MSI apps by @florelis in https://github.com/microsoft/winget-cli/pull/2418
$schema
to cgmanifest.json
by @JamieMagee in https://github.com/microsoft/winget-cli/pull/2487
source ls
alias for source list
by @florelis in https://github.com/microsoft/winget-cli/pull/2736
pin
command by @florelis in https://github.com/microsoft/winget-cli/pull/2733
--force
by @Trenly in https://github.com/microsoft/winget-cli/pull/2622
Workflow.cpp
into multiple files by @florelis in https://github.com/microsoft/winget-cli/pull/2773
Full Changelog: https://github.com/microsoft/winget-cli/compare/v.1.3.1611...v1.4.10173
Published by ryfu-msft almost 2 years ago
This is the first development build after the Windows Package Manager 1.4 build for Windows 10 (1809+) and Windows 11.
Experimental features are enabled in this release. The experimental feature for package pinning is visible but not yet functional. The implementation for the package pinning feature will be included in a future release preview. This build will be released to Windows Insider Dev builds, and Windows Package Manager Insiders.
Full Changelog: https://github.com/microsoft/winget-cli/compare/v1.4.10052...v1.5.101-preview
Published by ryfu-msft almost 2 years ago
This release represents our second Windows Package Manager 1.4 release candidate build for Windows 10 (1809+), and Windows 11. Experimental features have been disabled in this release. This release also includes our Microsoft.WinGet.Client PowerShell module. Information about getting started and usage can be found here.
Note: The Windows Package Manager Community Repository does not accept zip applications. They will not be accepted until after 1.4 is Generally Available and has been rolled out to the majority of Windows systems via the automatic upgrade from the Microsoft Store. Users may test with local manifests.
m_summary
in the global globals for telemetry by @florelis in https://github.com/microsoft/winget-cli/pull/2820
ms-windows-store
link not rendered in md by @iamCristYe in https://github.com/microsoft/winget-cli/pull/2403
RequireExplicitUpgrade
manifest element by @florelis in https://github.com/microsoft/winget-cli/pull/1795
UpgradeCode
for matching MSI apps by @florelis in https://github.com/microsoft/winget-cli/pull/2418
$schema
to cgmanifest.json
by @JamieMagee in https://github.com/microsoft/winget-cli/pull/2487
source ls
alias for source list
by @florelis in https://github.com/microsoft/winget-cli/pull/2736
pin
command by @florelis in https://github.com/microsoft/winget-cli/pull/2733
--force
by @Trenly in https://github.com/microsoft/winget-cli/pull/2622
Workflow.cpp
into multiple files by @florelis in https://github.com/microsoft/winget-cli/pull/2773
Full Changelog: https://github.com/microsoft/winget-cli/compare/v.1.3.1611...v1.4.10052
Published by ryfu-msft almost 2 years ago
This release represents our first Windows Package Manager 1.4 release candidate build for Windows 10 (1809+), and Windows 11. Experimental features have been disabled in this release. This release also includes our Microsoft.WinGet.Client PowerShell module. Information about getting started and usage can be found here.
Note: The Windows Package Manager Community Repository does not accept zip applications. They will not be accepted until after 1.4 is Generally Available and has been rolled out to the majority of Windows systems via the automatic upgrade from the Microsoft Store. Users may test with local manifests.
ms-windows-store
link not rendered in md by @iamCristYe in https://github.com/microsoft/winget-cli/pull/2403
RequireExplicitUpgrade
manifest element by @florelis in https://github.com/microsoft/winget-cli/pull/1795
UpgradeCode
for matching MSI apps by @florelis in https://github.com/microsoft/winget-cli/pull/2418
$schema
to cgmanifest.json
by @JamieMagee in https://github.com/microsoft/winget-cli/pull/2487
source ls
alias for source list
by @florelis in https://github.com/microsoft/winget-cli/pull/2736
pin
command by @florelis in https://github.com/microsoft/winget-cli/pull/2733
--force
by @Trenly in https://github.com/microsoft/winget-cli/pull/2622
Workflow.cpp
into multiple files by @florelis in https://github.com/microsoft/winget-cli/pull/2773
Full Changelog: https://github.com/microsoft/winget-cli/compare/v.1.3.1611...v1.4.3531
Published by ryfu-msft almost 2 years ago
This is the third development build after the Windows Package Manager 1.3 build for Windows 10 (1809+) and Windows 11.
Experimental features are enabled in this release. The experimental support for installing from a zip file (including portable packages) is included in this release. Another helpful troubleshooting feature is "--open-logs". This build will be released to Windows Insider Dev builds, and Windows Package Manager Insiders.
Run winget features
to see which experimental features are enabled or disabled.
Add the following to your settings (winget settings
) file to enable support for testing .zip manifests:
"experimentalFeatures": {"zipInstall": true}
Add the following to your settings (winget settings
) file to enable support for opening the log directory:
"experimentalFeatures":{"openLogsArgument":true}
With this experimental feature enabled you can append "--open-logs" to any command and the logs directory will open after the command completes.
UpgradeCode
for matching MSI apps by @lechacon in https://github.com/microsoft/winget-cli/pull/2418
$schema
to cgmanifest.json
by @JamieMagee in https://github.com/microsoft/winget-cli/pull/2487
Full Changelog: https://github.com/microsoft/winget-cli/compare/v1.4.2161-preview...v1.4.3132-preview
Published by ryfu-msft about 2 years ago
This is the second stable release of the Windows Package Manager 1.3.
This release is just for the sake of transparency for Windows Package Manager users. This ensures that the GitHub release is aligned with any changes related to AppInstaller. The changes associated with this release only affect AppInstaller. No additional features or bug fixes related to winget were included.
Experimental features are disabled in this release.
Published by ryfu-msft about 2 years ago
This is the second development build after the Windows Package Manager 1.3 build for Windows 10 (1809+) and Windows 11.
Experimental features are enabled in this release. The experimental support for installing from a zip file (except portable packages) is included in this release. This build will be released to Windows Insider Dev builds, and Windows Package Manager Insiders.
Run winget features
to see which experimental features are enabled or disabled.
Add the following to your settings (winget settings
) file to enable support for testing .zip manifests:
"experimentalFeatures": {"zipInstall": true}
Note: The Windows Package Manager Community Repository does not accept zip applications. They will not be accepted until after 1.4 is Generally Available and has been rolled out to the majority of Windows systems via the automatic upgrade from the Microsoft Store. Users may test with local manifests.
We've also made progress towards native PowerShell cmdlets. These will work with PowerShell 6 and PowerShell 7. We're still working on the hurdles associated with PowerShell 5.1. We're planning to have a downloadable module for import in a future release. Join the PowerShell discussions if you're interested.
ms-windows-store
link not rendered in md by @iamCristYe in https://github.com/microsoft/winget-cli/pull/2403
RequireExplicitUpgrade
manifest element by @lechacon in https://github.com/microsoft/winget-cli/pull/1795
Full Changelog: https://github.com/microsoft/winget-cli/compare/release-v1.3.1872...release-v1.4.2161-preview
Published by ryfu-msft about 2 years ago
This release is the first stable release of Windows Package Manager 1.3.
This release represents our fourth Windows Package Manager 1.3 release candidate build for Windows 10 (1809+), and Windows 11.
This release addresses several bugs related to installing a portable package such as incorrectly displaying a file overwrite warning message, failing to create a symlink if developer mode is not enabled or not running in admin, and not preserving scope when upgrading.
Experimental features have been disabled in this release. We will follow this release with another Pre-release "developer" build at GitHub so users can continue with experimental features available.
>Note: The Windows Package Manager Community Repository does not accept portable applications. They will not be accepted until after 1.3 is Generally Available and has been rolled out to the majority of Windows systems via the automatic upgrade from the Microsoft Store. Users may test with local manifests.
Support for installation of portable/standalone apps #182
Add a notes/info field to manifests. #607
Add an optional URL to Expected Return Codes #1889
Manifest Field for User Manual / Documentation #1984
Add alternative version number field to manifest to make correlation with entries in Add/Remove programs more reliable #980
Setting for always using verbose logs #1940
winget --info should print the system architecture #1925
An even better progress bar #2055
Remove scope filter from being applied to portables #2383
Check for symlink creation privilege for portable install #2369
Fix file overwrite warning displayed on clean first install #2375
Mitigate crash that can occur when installed version is null #2278
Searching for dotnet package #2218
Allow winget to install MS Store packages without account just like the MS Store #1585
--include-unknown not functioning as expected #1939
Includes a fix for an App Installer bug that was causing crashes due to null pointer reads
--include-unknown
message by @felipecrs in https://github.com/microsoft/winget-cli/pull/1946
winget --info
. by @jedieaston in https://github.com/microsoft/winget-cli/pull/1937
upgrade --all
by @jedieaston in https://github.com/microsoft/winget-cli/pull/1866
upgrade
. by @jedieaston in https://github.com/microsoft/winget-cli/pull/1874
Full Changelog: https://github.com/microsoft/winget-cli/compare/release-v1.2.10271...release-v1.3.2091
Published by ryfu-msft about 2 years ago
This is the first development build after the Windows Package Manager 1.3 build for Windows 10 (1809+) and Windows 11.
Experimental features are enabled in this release. The experimental support for installing from a zip file (except portable packages) is included in this release. This build will be released to Windows Insider Dev builds, and Windows Package Manager Insiders.
Note: The Windows Package Manager Community Repository does not accept zip applications. They will not be accepted until after 1.4 is Generally Available and has been rolled out to the majority of Windows systems via the automatic upgrade from the Microsoft Store. Users may test with local manifests.
Full Changelog: https://github.com/microsoft/winget-cli/compare/release-v1.3.1872...release-v1.4.2011-preview
Published by ryfu-msft over 2 years ago
This release represents our third Windows Package Manager 1.3 release candidate build for Windows 10 (1809+), and Windows 11.
This release modifies the package manifest of AppInstaller to enable the UnvirtualizedResources capability and disables virtualizing all resources in order to support the installation of portable packages.
Experimental features have been disabled in this release. We will follow this release with another Pre-release "developer" build at GitHub so users can continue with experimental features available.
Note: The Windows Package Manager Community Repository does not accept portable applications. They will not be accepted until after 1.3 is Generally Available and has been rolled out to the majority of Windows systems via the automatic upgrade from the Microsoft Store. Users may test with local manifests.
Support for installation of portable/standalone apps #182
Add a notes/info field to manifests. #607
Add an optional URL to Expected Return Codes #1889
Manifest Field for User Manual / Documentation #1984
Add alternative version number field to manifest to make correlation with entries in Add/Remove programs more reliable #980
Setting for always using verbose logs #1940
winget --info should print the system architecture #1925
An even better progress bar #2055
Mitigate crash that can occur when installed version is null #2278
Searching for dotnet package #2218
Allow winget to install MS Store packages without account just like the MS Store #1585
--include-unknown not functioning as expected #1939
Includes a fix for an App Installer bug that was causing crashes due to null pointer reads
--include-unknown
message by @felipecrs in https://github.com/microsoft/winget-cli/pull/1946
winget --info
. by @jedieaston in https://github.com/microsoft/winget-cli/pull/1937
upgrade --all
by @jedieaston in https://github.com/microsoft/winget-cli/pull/1866
upgrade
. by @jedieaston in https://github.com/microsoft/winget-cli/pull/1874
Full Changelog: https://github.com/microsoft/winget-cli/compare/release-v1.2.10271...release-v1.3.1872
Published by ryfu-msft over 2 years ago
This release represents our second Windows Package Manager 1.3 release candidate build for Windows 10 (1809+), and Windows 11.
This release includes a bug fix for mitigating a crash that occurred when using the list command #2273
Experimental features have been disabled in this release. We will follow this release with another Pre-release "developer" build at GitHub so users can continue with experimental features available.
Note: The Windows Package Manager Community Repository does not accept portable applications. They will not be accepted until after 1.3 is Generally Available and has been rolled out to the majority of Windows systems via the automatic upgrade from the Microsoft Store. Users may test with local manifests.
Support for installation of portable/standalone apps #182
Add a notes/info field to manifests. #607
Add an optional URL to Expected Return Codes #1889
Manifest Field for User Manual / Documentation #1984
Add alternative version number field to manifest to make correlation with entries in Add/Remove programs more reliable #980
Setting for always using verbose logs #1940
winget --info should print the system architecture #1925
An even better progress bar #2055
Mitigate crash that can occur when installed version is null #2278
Searching for dotnet package #2218
Allow winget to install MS Store packages without account just like the MS Store #1585
--include-unknown not functioning as expected #1939
Includes a fix for an App Installer bug that was causing crashes due to null pointer reads
--include-unknown
message by @felipecrs in https://github.com/microsoft/winget-cli/pull/1946
winget --info
. by @jedieaston in https://github.com/microsoft/winget-cli/pull/1937
upgrade --all
by @jedieaston in https://github.com/microsoft/winget-cli/pull/1866
upgrade
. by @jedieaston in https://github.com/microsoft/winget-cli/pull/1874
Full Changelog: https://github.com/microsoft/winget-cli/compare/release-v1.2.10271...release-v1.3.1741
Published by ryfu-msft over 2 years ago
This release represents our Windows Package Manager 1.3 release candidate build for Windows 10 (1809+), and Windows 11.
Experimental features have been disabled in this release. We will follow this release with another Pre-release "developer" build at GitHub so users can continue with experimental features available.
Note: The Windows Package Manager Community Repository does not accept portable applications. They will not be accepted until after 1.3 is Generally Available and has been rolled out to the majority of Windows systems via the automatic upgrade from the Microsoft Store. Users may test with local manifests.
Support for installation of portable/standalone apps #182
Add a notes/info field to manifests. #607
Add an optional URL to Expected Return Codes #1889
Manifest Field for User Manual / Documentation #1984
Add alternative version number field to manifest to make correlation with entries in Add/Remove programs more reliable #980
Setting for always using verbose logs #1940
winget --info should print the system architecture #1925
An even better progress bar #2055
Searching for dotnet package #2218
Allow winget to install MS Store packages without account just like the MS Store #1585
--include-unknown not functioning as expected #1939
Includes a fix for an App Installer bug that was causing crashes due to null pointer reads
--include-unknown
message by @felipecrs in https://github.com/microsoft/winget-cli/pull/1946
winget --info
. by @jedieaston in https://github.com/microsoft/winget-cli/pull/1937
upgrade --all
by @jedieaston in https://github.com/microsoft/winget-cli/pull/1866
upgrade
. by @jedieaston in https://github.com/microsoft/winget-cli/pull/1874
Full Changelog: https://github.com/microsoft/winget-cli/compare/release-v1.2.10271...rc-v1.3.1681
Published by ryfu-msft over 2 years ago
This is the fifth development build after the Windows Package Manager 1.2 build for Windows 10 (1809+) and Windows 11.
Experimental features are enabled in this release.
Note: The Windows Package Manager Community Repository does not accept portable applications. They will not be accepted until after 1.3 is Generally Available and has been rolled out to the majority of Windows systems via the automatic upgrade from the Microsoft Store. Users may test with local manifests. You may need to manually clean up Windows Apps & Features if you install on the main OS rather than a Windows Sandbox.
Includes a fix for an App Installer bug that was causing crashes due to null pointer reads
Published by denelon over 2 years ago
This is the fourth development build after the Windows Package Manager 1.2 build for Windows 10 (1809+) and Windows 11.
Experimental features are enabled in this release.
Support for installation of portable/standalone apps is now a stable feature in this preview.
Note: The Windows Package Manager Community Repository does not accept portable applications. They will not be accepted until after 1.3 is Generally Available and has been rolled out to the majority of Windows systems via the automatic upgrade from the Microsoft Store. Users may test with local manifests. You may need to manually clean up Windows Apps & Features if you install on the main OS rather than a Windows Sandbox.
Support for installation of portable/standalone apps #182
Add a notes/info field to manifests. #607
Add an optional URL to Expected Return Codes #1889
Manifest Field for User Manual / Documentation #1984
Add alternative version number field to manifest to make correlation with entries in Add/Remove programs more reliable #980
Searching for dotnet package #2218
Full Changelog: https://github.com/microsoft/winget-cli/compare/v1.3.431...v.1.3.1611
Published by denelon over 2 years ago
This is the third development build after the Windows Package Manager 1.2 build for Windows 10 (1809+) and Windows 11.
Experimental features are enabled in this release. The experimental support for portable applications now includes support for upgrade and uninstall (for portable packages).
Note: The Windows Package Manager Community Repository does not accept portable applications. They will not be accepted until after 1.3 is Generally Available and has been rolled out to the majority of Windows systems via the automatic upgrade from the Microsoft Store. Users may test with local manifests. You may need to manually clean up Windows Apps & Features if you install on the main OS rather than a Windows Sandbox.
Full Changelog: https://github.com/microsoft/winget-cli/compare/v1.3.1251-preview...v1.3.1391-preview
Published by denelon over 2 years ago
This is the second development build after the Windows Package Manager 1.2 build for Windows 10 (1809+) and Windows 11.
Experimental features are enabled in this release. This build will be released to Windows Insider Dev builds, and Windows Package Manager Insiders. We're going to get another preview build at GitHub to include upgrade and uninstall for portable packages.
The most notable new experimental feature is support for installing portable applications.
Note: The upgrade and uninstall behaviors have not been implemented. The community repository does not accept portable applications either. Users may test with local manifests but will need to manually clean up entries in Windows Apps & Features if this is used to install a portable application.
The COM API has also been extended to support for uninstall.
Note: This is part of the work that is a prerequisite to having native PowerShell support. The cmdlets will be able to leverage the COM API to get rich objects out.
We've started working on an "In-proc" COM NuGet package that will be leveraged by Intune and other MDM solutions to support remote system context execution. This will not be considered GA and supported until it reaches version 1.0.
--include-unknown
message by @felipecrs in https://github.com/microsoft/winget-cli/pull/1946
winget --info
. by @jedieaston in https://github.com/microsoft/winget-cli/pull/1937
Full Changelog: https://github.com/microsoft/winget-cli/compare/v1.3.431...v1.3.1251-preview