Windows Package Manager 1.7.3452-preview

This is the sixth development build after the Windows Package Manager 1.6 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.

    "experimentalFeatures": {
	  "directMSI": true,
          "windowsFeature": true,
          "configuration03": true,
          "reboot": true,
    },

Windows Package Manager also 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. To install the latest version of the PowerShell module, run the following command in PowerShell 7+.

Install-Module -Name Microsoft.WinGet.Client

The PowerShell module requires App Installer (winget) to be installed. The Repair-WinGetPackageManager cmdlet (work in progress) is designed to install or repair App Installer.

What's Changed

• Minor updates to App Installer

Windows Package Manager 1.7.3172-preview

This is the fifth development build after the Windows Package Manager 1.6 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. This preview release includes performance improvements as well as fixes for enabling Windows Features when running in packaged context. There are new experimental features for allowing winget to kick of a reboot if one is required and support for the new v0.3 configuration schema.

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.

    "experimentalFeatures": {
	  "directMSI": true,
          "windowsFeature": true,
          "configuration03": true,
          "reboot": true,
    },

Windows Package Manager also 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. To install the latest version of the PowerShell module, run the following command in PowerShell 7+.

Install-Module -Name Microsoft.WinGet.Client

The PowerShell module requires App Installer (winget) to be installed. The Repair-WinGetPackageManager cmdlet (work in progress) is designed to install or repair App Installer.

What's Changed

• Make manifest retrieval choice more dynamic by @JohnMcPMS in #3738
• Allow --accept-source-agreements with local manifests by @Trenly in #3573
• Invoke ShellExecute on dism.exe for enabling Windows Features by @ryfu-msft in #3659
• Allow --include-unknown with install by @Trenly in #3752
• Broadcast WM_SETTINGCHANGE on change of path by @Trenly in #3751
• Add resume command and support saving the argument state. by @ryfu-msft in #3508
• Allow higher versions to satisfy the VCLibs dependency in Repair by @JohnMcPMS in #3763
• Use package version as potential last update timestamp by @JohnMcPMS in #3759
• Add missing condition for using toolset v143 when building JsonCppLib for arm by @florelis in #3773
• Move SQLite base code by @JohnMcPMS in #3790
• Fix non-test hook code for Windows Feature by @JohnMcPMS in #3789
• Skip dependency evaluation with --skip-dependencies by @mdanish-kh in #3784
• Download and install Workflow patches for skip dependencies by @yao-msft in #3794
• Add experimental feature for initiating reboot for single package installs by @ryfu-msft in #3631
• Microsoft.WinGet.Client Any CPU by @msftrubengu in #3622
• Inform user if a module requires elevation by @msftrubengu in #3758
• Add missing manifest fields by @hackean-msft in #3757
• Configuration Schema 0.3 by @JohnMcPMS in #3779
• Extend Configuration COM API for export by @florelis in #3787
• Fix binskim issues by @ryfu-msft in #3815
• Performance improvements by @JohnMcPMS in #3808
• Fix OOP config helper by @JohnMcPMS in #3873
• Revert manifest schemas to json draft-07 by @ryfu-msft in #3875
• Allow Microsoft.WinGet.Client to run in any PowerShell session running as system by @msftrubengu in #3816
• Fix signaling the app shutdown event running as admin by @msftrubengu in #3874

Full Changelog: v1.7.2782-preview...v1.7.3172-preview

Windows Package Manager 1.6.3421

This release is the sixth stable release of Windows Package Manager 1.6 for Windows 10 (1809+) and Windows 11. Experimental features have been disabled in this release.

The winget configure command is now a stable feature and can be used to automatically handle the setup and configuration requirements for an ideal development environment on your Windows machine. Applying a WinGet configuration file helps with installing and managing software packages, applications, programming languages, frameworks, tools, or settings necessary for a project.

Support for package dependencies is also included in this stable release. You can also use the winget download command to download a package installer to your local machine.

What's Changed

• Minor updates to App Installer.

Full Changelog: v1.6.3133...v1.6.3421

Windows Package Manager 1.6.3133

This release is the fifth stable release of Windows Package Manager 1.6 for Windows 10 (1809+) and Windows 11. Experimental features have been disabled in this release.

The winget configure command is now a stable feature and can be used to automatically handle the setup and configuration requirements for an ideal development environment on your Windows machine. Applying a WinGet configuration file helps with installing and managing software packages, applications, programming languages, frameworks, tools, or settings necessary for a project.

Support for package dependencies is also included in this stable release. You can also use the winget download command to download a package installer to your local machine.

What's Changed

• Add missing condition for using toolset v143 when building JsonCppLib for arm by @florelis in #3773
• Performance improvements by @JohnMcPMS in #3867
• Make manifest retrieval choice more dynamic by @JohnMcPMS in #3738
• Allow --accept-source-agreements with local manifests by @Trenly in #3753
• Broadcast WM_SETTINGCHANGE on change of path by @JohnMcPMS in #3751
• Allow higher version to satisfy the dependency by @JohnMcPMS in #3763
• Use package version as potential last update timestamp by @JohnMcPMS in #3759
• Microsoft.WinGet.Client Any CPU by @msftrubengu in #3622

Full Changelog: v1.6.2771...v1.6.3133

Windows Package Manager 1.7.2782-preview

This is the fourth development build after the Windows Package Manager 1.6 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.

    "experimentalFeatures": {
	  "directMSI": true
          "windowsFeature": true
    },

Windows Package Manager also 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

The PowerShell module requires App Installer (winget) to be installed. The Repair-WinGetPackageManager cmdlet (work in progress) is designed to install or repair App Installer.

What's Changed

• Platform source should not be blocked by policy check by @yao-msft in #3725
• Update docs for upgrade command by @KK-Designs in #3639
• Honor 429 Retry-After by @msftrubengu in #3718

New Contributors

• @KK-Designs made their first contribution in #3639

Full Changelog: v1.7.2722-preview...v1.7.2782-preview

Windows Package Manager 1.6.2771

This release is the fourth stable release of Windows Package Manager 1.6 for Windows 10 (1809+) and Windows 11. Experimental features have been disabled in this release.

The winget configure command is now a stable feature and can be used to automatically handle the setup and configuration requirements for an ideal development environment on your Windows machine. Applying a WinGet configuration file helps with installing and managing software packages, applications, programming languages, frameworks, tools, or settings necessary for a project.

Support for package dependencies is also included in this stable release. You can also use the winget download command to download a package installer to your local machine.

What's Changed

• Platform source should not be blocked by policy check by @yao-msft in #3725
• Honor 429 Retry-After by @msftrubengu in #3718

Full Changelog: v1.6.2721...v1.6.2771

Windows Package Manager 1.7.2722-preview

This is the third development build after the Windows Package Manager 1.6 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.

    "experimentalFeatures": {
	  "directMSI": true
          "windowsFeature": true
    },

Windows Package Manager also 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

The PowerShell module requires App Installer (winget) to be installed. The Repair-WinGetPackageManager cmdlet (work in progress) is designed to install or repair App Installer.

What's Changed

• Enable COM API access to correlate with the tracking database only by @JohnMcPMS in #3703
• Use correct caller name in Com startup telemetry event by @yao-msft in #3711

Full Changelog: v1.7.2711-preview...v1.7.2722-preview

Windows Package Manager 1.6.2721

This release is the third stable release of Windows Package Manager 1.6 for Windows 10 (1809+) and Windows 11. Experimental features have been disabled in this release.

The winget configure command is now a stable feature and can be used to automatically handle the setup and configuration requirements for an ideal development environment on your Windows machine. Applying a WinGet configuration file helps with installing and managing software packages, applications, programming languages, frameworks, tools, or settings necessary for a project.

Support for package dependencies is also included in this stable release. You can also use the winget download command to download a package installer to your local machine.

What's Changed

• Enable COM API access to correlate with the tracking database only by @JohnMcPMS in #3703
• Use correct caller name in Com startup telemetry event by @yao-msft in #3711

Full Changelog: v1.6.2701...v1.6.2721

Windows Package Manager 1.7.2711-preview

This is the second development build after the Windows Package Manager 1.6 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.

    "experimentalFeatures": {
	  "directMSI": true
          "windowsFeature": true
    },

Windows Package Manager also 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

The PowerShell module requires App Installer (winget) to be installed. The Repair-WinGetPackageManager cmdlet (work in progress) is designed to install or repair App Installer.

What's Changed

• Update SECURITY.md from 0.0.2 to 0.0.9 by @Aaron-Junker in #3600
• Microsoft.WinGet.Configuration E2E Pester tests by @msftrubengu in #3605
• SourceAutoUpdateInterval - Group Policy Description update. by @Madhusudhan-MSFT in #3621
• Make windows feature experimental by @ryfu-msft in #3620
• Rework the error list and add a command to get error information by @JohnMcPMS in #3615
• Add new cmdlets and cancellation support for Microsoft.WinGet.Configuration by @msftrubengu in #3614
• Make DSC resource name check case insentive by @msftrubengu in #3632
• Add try/catch when reading upgrade codes by @JohnMcPMS in #3637
• Add norestart to msi uninstall args by @yao-msft in #3638
• Read registry value data on demand by @JohnMcPMS in #3642
• Change alternate url by @JohnMcPMS in #3646
• Set default user agent for http range requests by @yao-msft in #3645
• Remove Invoke-CommandInDesktopPackage use by @JohnMcPMS in #3658
• Improve packaged source updating by @JohnMcPMS in #3657
• Add a bit of randomness to the wait time after source update failure by @JohnMcPMS in #3661
• Reduce the size of the index by @JohnMcPMS in #3666
• Log Com invocation startup telemetry and delay auto update time when invoked from explorer by @yao-msft in #3665
• Enable COM API access to correlate with the tracking database only by @JohnMcPMS in #3670
• Fix localized strings output by @mdanish-kh in #3673
• Improve the version header detection and logging by @JohnMcPMS in #3680
• Revert 3670 by @JohnMcPMS in #3700

New Contributors

• @Aaron-Junker made their first contribution in #3600

Full Changelog: v1.7.2491-preview...v1.7.2711-preview

Windows Package Manager 1.6.2701

This release is the second stable release of Windows Package Manager 1.6 for Windows 10 (1809+) and Windows 11. Experimental features have been disabled in this release.

The winget configure command is now a stable feature and can be used to automatically handle the setup and configuration requirements for an ideal development environment on your Windows machine. Applying a WinGet configuration file helps with installing and managing software packages, applications, programming languages, frameworks, tools, or settings necessary for a project.

Support for package dependencies is also included in this stable release. You can also use the winget download command to download a package installer to your local machine.

What's Changed

• Set default user agent for http range requests by @yao-msft in #3645
• Change alternate url by @JohnMcPMS in #3646
• Improve packaged source updating by @JohnMcPMS in #3657
• Add a bit of randomness to the wait time after source update failure by @JohnMcPMS in #3661
• Log Com invocation startup telemetry and delay auto update time when invoked from explorer by @yaomsftin #3665
• Fix localized strings output by @mdanish-kh in #3673
• Improve the version header detection and logging by @JohnMcPMS in #3680

Full Changelog: release-v1.6.2631...release-v1.6.2701