Windows Package Manager 1.11.510

[florelis]

This is a servicing update for the Windows Package Manager 1.11 release build for Windows 10 (1809+), and Windows 11.

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 Fonts

The 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
  }
}

Servicing updates

• Updated certificate pinning for MS Store to use partial chains and new certificates.

What's Changed

• Update detours vcpkg to use prior version (CP to 1.11) by @JohnMcPMS in Update detours vcpkg to use prior version (CP to 1.11) #5608
• Improve COM static store usage (port to 1.11) by @JohnMcPMS in Improve COM static store usage (port to 1.11) #5685
• MS Store cert pinning updates (1.11) by @JohnMcPMS in MS Store cert pinning updates (1.11) #5735

Full Changelog: v1.11.430...v1.11.510

---

This discussion was created from the release Windows Package Manager 1.11.510.

[Almighty188]

Microsoft Store did the update but it seems like it is still keeping the older version and not deleting it.

Here is what is strange, winget -v shows it has the latest version v1.11.510 but UniGetUI (formerly WingetUI) keeps thinking I have a older version v1.10.340....

I also have two 0 byte sized winget.exe files...

How would I fix this or is it supposed to have two versions?

[florelis]

Here is what is strange, winget -v shows it has the latest version v1.11.510 but UniGetUI (formerly WingetUI) keeps thinking I have a older version v1.10.340....

UniGetUI is showing the Microsoft.WinGet.Client PowerShell module, not the Microsoft.DesktopAppInstaller MSIX that contains winget.exe

I also have two 0 byte sized winget.exe files...

Those are App Execution Aliases, which are basically pointers to the actual file in C:\Program Files\WindowsApps

Microsoft Store did the update but it seems like it is still keeping the older version and not deleting it.

The files in C:\Program Files\WindowsApps are managed by the app deployment stack. The previous version (1.26.430) should get cleaned up eventually. It may still be there because some file is still in use, or because that version is still registered for a different user, or it's simply in the queue, or probably other reasons I'm not aware of.

[Almighty188]

Thanks, where is the PowerShell module actually located and is it even needed, so basically Powershell has it's own winget? I always thought the system would only have one winget.

[florelis]

The PS module gives you cmdlets that are easier to use for automation than the raw output from winget.exe because they return actual objects. For example, instead of winget search foo you can do Find-WinGetPackage foo

PS modules are installed to {Documents folder}\PowerShell\Modules (replace PowerShell for WindowsPowerShell if using Windows PowerShell instead of PowerShell Core; replace the Documents folder for the Program Files folder if you install the module for all users)

[Almighty188]

@florelis - Thanks. Does the PS Module actually automatically update itself or when a new version of PowerShell such as v7.5.3 comes out?

[florelis]

I believe PS modules do not automatically update and you need to use Update-Module explicitly

[osamaaljawaan-maker]

Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle