Skip to content

Conflicting DISM Wildcard Behavior and Documentation #4004

Open
@tablackburn

Description

@tablackburn

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    issue-doc-bugSomething is out of date, unclear, confusing, or broken in the article. Blocks customer success.needs-triageWaiting - Needs triage

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions