[Feature Request] Add info for the Winget package.

Open Beginner friendly

#8,025 opened on Dec 25, 2025 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 68/100

Issue type: Documentation
Clarity: Mostly clear
Activity status: Stale
Domain: documentation, release

Research direction

Locate the release notes and README.md sections that describe available installation methods, then compare their existing NuGet wording with the requested Winget package information. Done means the relevant documentation consistently mentions the Microsoft.DirectX.ShaderCompiler Winget package and preserves the package links and release-specific wording.

Written by the indexing model from the issue text.

Description

enhancement

Is your feature request related to a problem? Please describe.
I've added a Winget package for DirectX Shader Compiler (https://github.com/microsoft/winget-pkgs/pull/325910, and since Winget is also a Microsoft tool (like what Nuget is), I presume that info on that package should be added to the listed available installation methods in this repo.

Describe the solution you'd like
Presumably that mentions of the Winget installation method gets listed in the Releases notes, like what the Nuget methods are.

For the newest version at the time of writing, this would likely mean replacing:
"This DX compiler release is also available as a NuGet package Microsoft.Direct3D.DXC."

With:
"This DX compiler release is also available as a NuGet package Microsoft.Direct3D.DXC, and as a Winget package Microsoft.DirectX.ShaderCompiler."

Describe alternatives you've considered
That mentions of Winget, Nuget, binary, and other (if any) installation methods get added to the README.md.

Winget packages are unfortunately not inherently auto-updated when new binaries are released on GitHub, but there's at least a few people on the Winget-pkgs repo to ask for help on adding it to their auto-update bots or about other ways of auto-updating.

Dominant language: C++
Stars: 3.7k
Forks: 900
Avg merge: 2d 14h
Merged PRs (30d): 39

Contributor guide

Open the contributing guide

First steps

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

Similar issues

[Bug] NULL pointer dereference in llm_running_callback (NGZA-AX-LLM #3) Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

AXERA-TECH/ax-llm#77 · Opened Sep 22, 2026
resume() sends a second HTTP response (400) after a successful resume Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

games-on-whales/wolf#509 · Opened Sep 21, 2026
pn7160: reader goes permanently deaf — post-read IRQ-low check fails reads that succeeded Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

esphome/esphome#19452 · Opened Sep 21, 2026
Eval bug: Ministral-3 tool-calls during reasoning are not processed Open

bug-unconfirmed

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

ggml-org/llama.cpp#29248 · Opened Sep 21, 2026
run_tests.py fails on windows, but running tests individually works Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

NVIDIA/cuda-samples#453 · Opened Sep 21, 2026

More C++ issues