Skip to content

docs: Mention PS 5.1 bug where Get-ChildItem ignores -Depth parameter when used with -Include #11804

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Feb 18, 2025
Merged

docs: Mention PS 5.1 bug where Get-ChildItem ignores -Depth parameter when used with -Include #11804

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b397415
docs: Mention Windows PowerShell 5 bug where Get-ChildItem ignore -De…
deadlydog Feb 14, 2025
d073584
Minor edit
sdwheeler Feb 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions reference/5.1/Microsoft.PowerShell.Management/Get-ChildItem.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -520,6 +520,10 @@ For example, `-Depth 2` includes the **Path** parameter's directory, first level
and second level of subdirectories. By default directory names and filenames are included in the
output.

> [!NOTE]
> The **Depth** parameter has no effect when used with the **Include** parameter. To work around
> this issue, use the **Filter** parameter instead. This is fixed in PowerShell 6 and higher.

> [!NOTE]
> On a Windows computer from PowerShell or **cmd.exe**, you can display a graphical view of a
> directory structure with the **tree.com** command.
Expand Down Expand Up @@ -802,6 +806,10 @@ after the inclusions, which can affect the final output.
> The **Include** and **Exclude** parameters have no effect when used with the **LiteralPath**
> parameter. This is fixed in PowerShell 7.

> [!NOTE]
> The **Depth** parameter has no effect when used with the **Include** parameter. To work around
> this issue, use the **Filter** parameter instead. This is fixed in PowerShell 6.

```yaml
Type: System.String[]
Parameter Sets: (All)
Expand Down