Microsoft 11933 Published by

Microsoft has released Windows Package Manager 1.12.46, a servicing release of version v1.12 that brings several updates and bug fixes. New features include the availability of an MCP server to help configure clients, support for font installation and uninstallation, and a new winget-fonts source. The App Installer now uses WinUI 3, and the manifest schema and validation have been updated to v1.12. Bug fixes address issues with manifest validation, package removal, source open failure, and App Installer functionality.



Windows Package Manager 1.12.460 released

Microsoft just released Windows Package Manager v1.12.46. It’s not an entirely new feature release; it’s mainly focused on servicing the existing version (v1.12), fixing bugs, and smoothing things out based on feedback.

Screenshot_from_2025_09_27_08_47_11

One neat thing added is support for the MCP server. This lets users run winget mcp to get help configuring their clients directly within Winget's ecosystem. And if you're using App Installer with Winget, there are some good changes too: it now relies on WinUI 3 instead of the older WinUI 2.

In v1.12, the developers have enhanced the manifest schema and its internal validation. As part of that, Font is now recognized as an InstallerType. A new source called winget-fonts has also landed. This means users can actually install or uninstall fonts using Winget commands, treating them just like other applications. It’s a non-experimental feature for both user and machine scopes.

Speaking of fixes, this version tackles several issues from the previous stable release (v1.12). Notables include handling manifest validation better when UTF-8 BOM encoding is involved, stopping packages in the PATH folder from being removed incorrectly during upgrades, and squashing various problems related to App Installer itself.

The big news for many might be font support landing properly; it’s now integrated as a core capability. You can install and uninstall fonts via Winget manifest or package sources just like any other software component. But here's the thing: right now, this feature works best with fonts that are already part of a WinGet Package distribution.

There is an experimental option, though, for font handling; you'd need to update your Winget settings configuration and explicitly enable it if you want to dive into experimental font commands or features. Even so, the standard way to manage fonts is via the existing winget-fonts source.

Also updated were things related to updating from wingget (the legacy name) to Winget, plus several commits specifically focused on getting the Font feature right and stabilized for general use.

Release Windows Package Manager 1.12.460 · microsoft/winget-cli

This is a servicing release of Windows Package Manager v1.12. If you find any bugs or problems, please help us out by filing an issue. New in v1.12 MCP server available; run winget mcp for assista...

Release Windows Package Manager 1.12.460 · microsoft/winget-cli