Windows Package Manager 1.12.250-preview

[florelis]

This is a preview build of WinGet for those interested in trying out upcoming features and fixes. While it has had some use and should be free of major issues, it may have bugs or usability problems. If you find any, please help us out by filing an issue.

New in v1.12

• MCP server available; run winget mcp for assistance on configuring your client.
• App Installer now uses WinUI 3. The package dependency on WinUI 2 has been replaced by a dependency on the Windows App Runtime 1.8.
• Manifest schema and validation updated to v1.12. This version update adds "Font" as an InstallerType and NestedInstallerType.

Bug Fixes

• Manifest validation no longer fails using UTF-8 BOM encoding when the schema header is on the first line

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

What's Changed

• Add the ARP correlation entry to the context for portable installs by @JohnMcPMS in Add the ARP correlation entry to the context for portable installs #5707
• Fix two unrelated version issues by @JohnMcPMS in Fix two unrelated version issues #5719

Full Changelog: v1.12.240-preview...v1.12.250-preview

---

This discussion was created from the release Windows Package Manager 1.12.250-preview.

[Infinitay]

Could I kindly get clarification on whether or not the changes made by #5707 are retroactive, or does it only apply to apps installed after the fact? The reason I am asking is because I thought this PR would change some issues I've been having finding packages via --id and specifically --exact, but it still seems to fail to find it when I specify --exact. After taking a look at the PR again and reading

We were not recording ARP changes for portable installs, which prevented the product code from being in the tracking database, which led to inconclusive correlation results for packages with shared normalized name+publisher.

and how the changes were made to the installer, I realized that perhaps the changes only affect future installs and not anything that had been installed prior to this preview version.

EDIT: I believe I answered my own question without realizing it. It does seem to only apply to apps installed. I tested it later and that also seems to confirm it only affects future installs on this preview or future version. I explained what I did in my comment edit on a related issue. My apologies.

[JohnMcPMS]

You are correct that it will only apply to future installs (or future re-installs).