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.ClientAdditional fixes are also included in this release to address minor issues with pinning, COM apis, and PowerShell module behavior.
What's Changed
- Microsoft.WinGet.Client custom assembly load context by @msftrubengu in #3150
- Mark events as critical for now by @JohnMcPMS in #3171
- Add table with pinned packages when doing
upgrade --include-pinnedby @florelis in #3173 - Fix PSInstalledCatalogPackage being piped to Upgrade-WinGetPackage by @msftrubengu in #3174
- WinGetPackage DSC Resource by @msftrubengu in #2863
- Add argument to list only upgradeable by @Trenly in #3162
- Enable module/resource syntax and improve file error reporting by @JohnMcPMS in #3186
- Start Microsoft.WinGet.Configuration module by @msftrubengu in #3187
- Fix a few issues with the single package targeting commands by @JohnMcPMS in #3196
- Enable building everything needed in PowerShell with static runtime by @JohnMcPMS in #3193
- Fix tags for --count argument by @florelis in #3195
- Repair-WinGetPackage download VCLibs if needed by @msftrubengu in #3180
- Make entitlement best effort by @JohnMcPMS in #3172
- Add manual platform attributes by @JohnMcPMS in #3203
- Initial implementation of Microsoft.WinGet.Configuration cmdlets. by @msftrubengu in #3204
- More PS build fixes by @JohnMcPMS in #3208
- Add configuration alias by @JohnMcPMS in #3225
- Allow prerelease modules for configuration by @msftrubengu in #3217
- Queue write operations for Start-* cmdlets and hook up diagnostics by @msftrubengu in #3222
- Record Product Codes in pinning table by @florelis in #3167
- Allow ${WinGetConfigRoot} variable expansion by @msftrubengu in #3237
- Add Friendlier Messages for Error Codes by @Trenly in #3201
- Add Table of Error Codes to Docs by @Trenly in #3202
- Explicity not support cmdlets in Windows PowerShell by @msftrubengu in #3238
- Configuration Schema 0.2 by @msftrubengu in #3241
- Update PSDesiredStateConfiguration module min version to 2.0.7 by @msftrubengu in #3251
- Microsoft.WinGet.Client throws System.InvalidOperationException: Attempt to update previously set global instance by @msftrubengu in #3253
- Fix packages with dependencies being installed via COM by @JohnMcPMS in #3254
Full Changelog: v1.5.1081-preview...v1.5.1361-preview