Running dsc3 throws sequence contains no elements

Brief description of your issue

Knowing that dsc3 is in experimental support phase, I was looking to get a working example. Unfortuntately, I'm stuck on the following step. These are what I'm following. In the settings.json I have the following:

{
    "$schema": "https://aka.ms/winget-settings.schema.json",
    "experimentalFeatures": {
        "configureSelfElevate": true,
        "dsc3": true
    }
}

I'm running version: v1.11.190-preview. I'm feeding the following example.winget.dsc.resource.yaml file:

$schema: https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2023/08/config/document.json
metadata:
  winget:
    processor: dscv3
resources:
  - name: Registry
    type: Microsoft.Windows/Registry
    metadata: 
      description: Registry
    properties:
      keyPath: HKCU\1\2\3

This throws the following error message: 0x80131509 : unknown error. Looking further in the log file:

2025-04-01 07:31:49.007 [CONF] System.InvalidOperationException: Sequence contains no elements
   at System.Linq.ThrowHelper.ThrowNoElementsException()
   at System.Linq.Enumerable.First[TSource](IEnumerable`1 source)
   at Microsoft.Management.Configuration.Processor.DSCv3.Helpers.ProcessorSettings.FindDscExecutablePath()
   at Microsoft.Management.Configuration.Processor.DSCv3.Helpers.ProcessorSettings.get_EffectiveDscExecutablePath()
   at Microsoft.Management.Configuration.Processor.DSCv3.Helpers.ProcessorSettings.ToString()
   at Microsoft.Management.Configuration.Processor.DSCv3ConfigurationSetProcessorFactory.CreateSetProcessorInternal(ConfigurationSet set, Boolean isLimitMode)
   at Microsoft.Management.Configuration.Processor.Factory.ConfigurationSetProcessorFactoryBase.CreateSetProcessor(ConfigurationSet incomingSet)
2025-04-01 07:31:49.026 [CONF] [FAIL] Microsoft.Management.Configuration.dll!00007FFB4FB6B31E: LogHr(1) tid(28bc0) 80131509

Steps to reproduce

Described in the description.

Expected behavior

The configuration document should be applied.

Actual behavior

Error occurs

Environment

Windows Package Manager (Preview) v1.11.190-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.26100.2033
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.26.190.0

Winget Directories
-----------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Diag…
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\sett…
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads
Configuration Modules              %LOCALAPPDATA%\Microsoft\WinGet\Configuration\Modules

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled
ProxyCommandLineOptions                   Disabled
DefaultProxy                              Disabled

Reproduce the issue with the shown settings.json and example.winget.dsc.resource.yaml, then start at ProcessorSettings.FindDscExecutablePath() in the logged DSCv3 stack trace. Investigate why the executable lookup has no elements; done means the configuration document applies without the Sequence contains no elements error.