Font source policy (EnableFontSource) is missing from the DesktopAppInstaller Policy CSP and its documentation

Open Beginner friendly
#6,692 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
cpp
Domain
documentation

Research direction

Start by comparing the ADMX policy entry for EnableFontSource in doc/admx/DesktopAppInstaller.admx with the DesktopAppInstaller Policy CSP page cited in the issue. Determine whether the CSP should list the policy or note that it is available only through ADMX templates. Done means the documentation clearly explains how administrators can control the font source.

Written by the indexing model from the issue text.

Description

Issue-Docs Needs-Triage
Brief description of your issue

The Group Policy templates in winget-cli releases contain "Enable Windows Package Manager Font Source" (EnableFontSource) from v1.12.340 on (doc/admx/DesktopAppInstaller.admx, added in #5646). The v1.11.430 templates do not have it.

The DesktopAppInstaller Policy CSP page (https://learn.microsoft.com/windows/client-management/mdm/policy-csp-desktopappinstaller, last updated 2026-10-14) lists 15 policies, among them EnableDefaultSource, EnableMicrosoftStoreSource and EnableAllowedSources. It lists no font-source policy. DesktopAppInstaller.admx in C:\Windows\PolicyDefinitions on Windows 11 24H2 (build 26100.9711) and 25H2 (build 26200.8457), file dated 2024-04-01 on both, has the same 15.

On winget 1.29.380, with the default and Store sources disabled by policy and EnableFontSource not set, winget source list still shows winget-font. An administrator who works from the CSP page is not told that a third built-in source stays configured.

Request: add EnableFontSource to the DesktopAppInstaller Policy CSP, or add a note to that page that the font source has its own policy, available only through the ADMX templates.

Dominant language
C++
Stars
26.6k
Forks
1.8k
Avg merge
3d 10h
Merged PRs (30d)
41

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/winget-cli

All issues in microsoft/winget-cli

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.