Microsoft 11856 Published by

Microsoft has released Windows Package Manager 1.11.400, the release candidate of WinGet 1.11, incorporating several enhancements to optimize package management. The tasks involve incorporating DSCV3 user-settings resources, resolving issues with debug builds using VCPKG, and facilitating the export of package-related DSCV3 resources. The package also includes a vcpkg overlay for cpprestsdk and libyaml, which helps with preview DSC while it's still being tested and turns on developer mode. The package additionally comprises a Microsoft.Windows.Settings module designed for the activation of developer mode. The package includes fixes for problems with connecting to the catalog, system crashes, and improvements to DSC command descriptions, libyaml vcpkg port versions, and store endpoint certificates. The package additionally encompasses support for DSCv3 within configured PowerShell modules, along with updates to the release notes.



Windows Package Manager 1.11.400

This is the release candidate of WinGet v1.11 for those interested in trying out upcoming features and fixes.

If you find bugs or usability problems, please help us out by  filing an issue.

New in v1.11

  • Dropped support for running on 32-bit ARM
  • Support for  Microsoft Desired State Configuration (DSC) v3.
  • Support for exporting the configuration of the current device. This includes Windows Settings, packages from configured WinGet sources, and package settings from DSC v3 enabled packages.

Experimental Features

  • Experimental support for Fonts

Experimental support for FontsThe following snippet enables experimental support for fonts via winget settings. The winget font list command will list installed font families and the number of installed font faces.
{
  "$schema" "https://aka.ms/winget-settings.schema.json",
  "experimentalFeatures": {
    "fonts": true
  }
}
What's Changed

New Contributors

Full Changelog v1.10.390...v1.11.400

Release Windows Package Manager 1.11.400 · microsoft/winget-cli