Skip to content

Conflicting DISM Wildcard Behavior and Documentation #4004

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
3 tasks done
tablackburn opened this issue May 22, 2025 · 2 comments
Open
3 tasks done

Conflicting DISM Wildcard Behavior and Documentation #4004

tablackburn opened this issue May 22, 2025 · 2 comments
Labels
issue-doc-bug Something is out of date, unclear, confusing, or broken in the article. Blocks customer success. needs-triage Waiting - Needs triage

Comments

@tablackburn
Copy link

Prerequisites

  • Existing Issue: Search the existing issues for this repository. If there is an issue that fits your needs do not file a new one. Subscribe, react, or comment on that issue instead.
  • Descriptive Title: Write the title for this issue as a short synopsis. If possible, provide context. For example, "Typo in Get-Foo cmdlet" instead of "Typo."
  • Verify Version: If there is a mismatch between documentation and the behavior on your system, ensure that the version you are using is the same as the documentation. Check this box if they match or the issue you are reporting is not version specific.

Links

Summary

The Get-WindowsCapability documentation states that the -Name parameter does not accept wildcards, but the cmdlet does accept wildcards for the -Name parameter.

Expected

PS C:\> Get-WindowsCapability -Online -Name '*rsat*' | Format-Table -AutoSize

No results, or an error/warning

Actual

PS C:\> Get-WindowsCapability -Online -Name '*rsat*' | Format-Table -AutoSize

Name                                                          State DisplayName
----                                                          ----- -----------
Rsat.ActiveDirectory.DS-LDS.Tools~~~~0.0.1.0             NotPresent RSAT: Active Directory Domain Services and Lightwe…
Rsat.AzureStack.HCI.Management.Tools~~~~0.0.1.0          NotPresent RSAT: PowerShell module for Azure Stack HCI

I suspect this is also true of other DISM cmdlets, although I haven't done a thorough investigation.

Details

No response

Suggested Fix

I believe the documentation is automatically generated, so the source code probably just needs to be updated to signify that the parameter accepts wildcards.

@tablackburn tablackburn added issue-doc-bug Something is out of date, unclear, confusing, or broken in the article. Blocks customer success. needs-triage Waiting - Needs triage labels May 22, 2025
@sdwheeler
Copy link
Collaborator

This repository is for PowerShell core documentation. Source for that article is located at https://github.com/MicrosoftDocs/windows-powershell-docs/blob/main/docset/winserver2025-ps/Dism/Get-WindowsCapability.md.

@sdwheeler sdwheeler transferred this issue from MicrosoftDocs/PowerShell-Docs May 23, 2025
@sdwheeler sdwheeler added issue-doc-bug Something is out of date, unclear, confusing, or broken in the article. Blocks customer success. needs-triage Waiting - Needs triage labels May 23, 2025
@sdwheeler
Copy link
Collaborator

I transferred this issue to the proper repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue-doc-bug Something is out of date, unclear, confusing, or broken in the article. Blocks customer success. needs-triage Waiting - Needs triage
Projects
None yet
Development

No branches or pull requests

2 participants