DSC v3 Schema doesn't find the default WinGet configuration modules folder

Relevant area(s)

WinGet CLI

Relevant command(s)

winget configure

Brief description of your issue

I converted a configuration file from V2 Schema to V3 Schema. In the V2 schema running winget dsc test <file> worked. After converting the configuration file from V2 Schema to V3 schema, running winget dsc test <file> gave errors.

Steps to reproduce

Create a V3 Schema configuration that references V2 resources within the WinGet default configuration modules folder. Invoke winget configure test .

Expected behavior

The modules would be found in the default WinGet modules 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

Start by reproducing the issue with winget configure test <file> using a V3 Schema configuration that references V2 resources in the default WinGet configuration modules folder. Compare this with winget dsc test <file> and inspect the discovery path shown in the logs. Done means the referenced modules are found and the configuration test completes without resource-discovery errors.