microsoft / microsoft/winget-cli
--module-path does not work with DSC Schema V3
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Relevant area(s)
WinGet CLI
Relevant command(s)
winget configure
Brief description of your issue
When using Schema v3, I specified --module-path to find the DSCv2 modules in the default WinGet folder. Even after doing this, the modules were not able to be found by dsc.exe
Steps to reproduce
Create a V3 Schema configuration that references V2 resources within the WinGet default configuration modules folder. Invoke winget configure test with --module-path
Expected behavior
The modules would be found in the provided path
Actual behavior
Microsoft.WinGet.DSC/WinGetPackage [install-vs-code]
The configuration unit failed while attempting to test the current system state.
2025-08-28T22:51:42.974021Z INFO dsc::util: 393: Trace-level is Trace
2025-08-28T22:51:42.974055Z DEBUG dsc: 44: Running DSC version: 3.1.1
2025-08-28T22:51:42.974076Z DEBUG dsc_lib::discovery::command_discovery: 472: Searching for resources: ["Microsoft.WinGet.DSC/WinGetPackage"]…
<See the log file for additional details>
vscode/VSCodeExtension [redhat-vscode]
The configuration unit failed while attempting to test the current system state.
2025-08-28T22:52:15.182083Z INFO dsc::util: 393: Trace-level is Trace
2025-08-28T22:52:15.182118Z DEBUG dsc: 44: Running DSC version: 3.1.1
2025-08-28T22:52:15.182139Z DEBUG dsc_lib::discovery::command_discovery: 472: Searching for resources: ["vscode/VSCodeExtension"]…
<See the log file for additional details>
Environment
PS C:\Users\kaleb> winget --info
Windows Package Manager v1.11.430
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.26100.4946
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.26.430.0
Contributor 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.
Research direction
Start by reproducing the Schema V3 configuration with winget configure test and --module-path, using the WinGet default configuration modules folder and the reported V2 resources. Trace the WinGet CLI configure entry point through its interaction with dsc.exe; done means resources such as Microsoft.WinGet.DSC/WinGetPackage and vscode/VSCodeExtension are discovered from the supplied path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100