dsccommunity / dsccommunity/ComputerManagementDsc

WindowsCapability: Specified Windows Capability not found

Open
#454 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PowerShell
Stars
338
Forks
80
PR merge metrics
No merged PRs in 30d

Description

Problem description

When trying to run winget configure test configuration.yaml (contents of the yaml file below) using the WindowsCapability resource, I get an error:

  The configuration unit failed while attempting to test the current system state.
Specified Windows Capability 'OpenSSH.Server~~~~0.0.1.0' not found. (Parameter 'Name')
<See the log file for additional details>
Some of the configuration units failed while testing their state.

I've tried it with both OpenSSH.Server and OpenSSH.Client as specified in the wiki example but I had no luck, the log file is not created either

Verbose logs
No logs were created
DSC configuration
# yaml-language-server: $schema=https://aka.ms/configuration-dsc-schema/0.2
properties:
  configurationVersion: "0.2.0"
  resources:
    - resource: ComputerManagementDsc/WindowsCapability
      settings:
        Name: OpenSSH.Server~~~~0.0.1.0
        LogPath: C:\Temp\Logfile.log
Suggested solution

Not sure what is the fix

Operating system the target node is running
OsName               : Microsoft Windows 11 Home
OsOperatingSystemSKU : WindowsHome
OsArchitecture       : 64-bit
WindowsVersion       : 2009
WindowsBuildLabEx    : 26100.1.amd64fre.ge_release.240331-1435
OsLanguage           : en-US
OsMuiLanguages       : {en-US, en-GB, ja-JP, ko-KR…}
PowerShell version and build the target node is running
Name                           Value
----                           -----
PSVersion                      7.5.2
PSEdition                      Core
GitCommitId                    7.5.2
OS                             Microsoft Windows 10.0.26100
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0
ComputerManagementDsc version
Unsure, ran using winget

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing winget configure test configuration.yaml with the provided WindowsCapability YAML on the reported Windows 11 and PowerShell versions. Inspect the WindowsCapability resource behavior, the wiki example, and the ComputerManagementDsc version used by winget, then check why the capability name is rejected and why no log is created. Done means the supported configuration either works with the documented example or the incompatibility and required correction are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.