diff --git a/reference/5.1/Microsoft.PowerShell.Core/About/about_Module_Manifests.md b/reference/5.1/Microsoft.PowerShell.Core/About/about_Module_Manifests.md index e50f9b04ec72..8a19a11a1bc8 100644 --- a/reference/5.1/Microsoft.PowerShell.Core/About/about_Module_Manifests.md +++ b/reference/5.1/Microsoft.PowerShell.Core/About/about_Module_Manifests.md @@ -1,7 +1,13 @@ --- description: Describes the settings and practices for writing module manifest files. Locale: en-US -ms.date: 09/04/2025 +ms.date: 01/28/2026 +no-loc: +- Windows PowerShell 5.1 Workflow +- PowerShell Gallery +- Author +- Copyright +- Description online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_module_manifests?view=powershell-5.1&WT.mc_id=ps-gethelp schema: 2.0.0 title: about_Module_Manifests @@ -112,8 +118,8 @@ followed by a matrix that lists: - **Input type**: The object type that you can specify for this setting in the manifest. -- **Required**: If this value is `Yes`, the setting is required both to import - the module and to publish it to the PowerShell Gallery. If it's `No`, it's +- **Required**: If this value is "Yes", the setting is required both to import + the module and to publish it to the PowerShell Gallery. If it's "No", it's required for neither. If it's `PowerShell Gallery`, it's only required for publishing to the PowerShell Gallery. - **Value if unset**: The value this setting has when imported and not diff --git a/reference/5.1/Microsoft.PowerShell.Management/New-Item.md b/reference/5.1/Microsoft.PowerShell.Management/New-Item.md index fbb77aab8195..eba38f1c88cd 100644 --- a/reference/5.1/Microsoft.PowerShell.Management/New-Item.md +++ b/reference/5.1/Microsoft.PowerShell.Management/New-Item.md @@ -1,8 +1,10 @@ --- external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml Locale: en-US +no-loc: +- Target Module Name: Microsoft.PowerShell.Management -ms.date: 02/23/2024 +ms.date: 01/28/2026 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.management/new-item?view=powershell-5.1&WT.mc_id=ps-gethelp schema: 2.0.0 aliases: diff --git a/reference/5.1/Microsoft.PowerShell.Management/Remove-Item.md b/reference/5.1/Microsoft.PowerShell.Management/Remove-Item.md index 37c848c1d16a..95bd63405b58 100644 --- a/reference/5.1/Microsoft.PowerShell.Management/Remove-Item.md +++ b/reference/5.1/Microsoft.PowerShell.Management/Remove-Item.md @@ -2,7 +2,7 @@ external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Management -ms.date: 02/14/2023 +ms.date: 01/28/2026 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.management/remove-item?view=powershell-5.1&WT.mc_id=ps-gethelp schema: 2.0.0 aliases: @@ -130,7 +130,18 @@ cmdlet interprets the subject of the search to be a file that has no child items fails. > [!NOTE] -> This behavior was fixed in Windows versions 1909 and up. +> Starting in Windows version 1909, specifying the file type in the **Path** parameter when using +> the **Recurse** parameter does recursively discover child items with the given file extension. +> +> In Windows version 1909 and later, the following statements will discover and remove the same +> files: +> +> ```powershell +> # Works in all versions of Windows: +> Get-ChildItem -Path * -Include *.csv -Recurse | Remove-Item +> # Only correctly finds and removes nested CSV files in Windows 1909 and later: +> Get-ChildItem -Path *.csv -Recurse | Remove-Item +> ``` ### Example 5: Delete subkeys recursively diff --git a/reference/7.4/Microsoft.PowerShell.Core/About/about_Module_Manifests.md b/reference/7.4/Microsoft.PowerShell.Core/About/about_Module_Manifests.md index afb418ecce63..0699f584b851 100644 --- a/reference/7.4/Microsoft.PowerShell.Core/About/about_Module_Manifests.md +++ b/reference/7.4/Microsoft.PowerShell.Core/About/about_Module_Manifests.md @@ -1,7 +1,13 @@ --- description: Describes the settings and practices for writing module manifest files. Locale: en-US -ms.date: 09/04/2025 +ms.date: 01/28/2026 +no-loc: +- Windows PowerShell 5.1 Workflow +- PowerShell Gallery +- Author +- Copyright +- Description online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_module_manifests?view=powershell-7.4&WT.mc_id=ps-gethelp schema: 2.0.0 title: about_Module_Manifests @@ -112,8 +118,8 @@ followed by a matrix that lists: - **Input type**: The object type that you can specify for this setting in the manifest. -- **Required**: If this value is `Yes`, the setting is required both to import - the module and to publish it to the PowerShell Gallery. If it's `No`, it's +- **Required**: If this value is "Yes", the setting is required both to import + the module and to publish it to the PowerShell Gallery. If it's "No", it's required for neither. If it's `PowerShell Gallery`, it's only required for publishing to the PowerShell Gallery. - **Value if unset**: The value this setting has when imported and not diff --git a/reference/7.4/Microsoft.PowerShell.Management/New-Item.md b/reference/7.4/Microsoft.PowerShell.Management/New-Item.md index e938ff3a7216..caf1d1926654 100644 --- a/reference/7.4/Microsoft.PowerShell.Management/New-Item.md +++ b/reference/7.4/Microsoft.PowerShell.Management/New-Item.md @@ -1,8 +1,10 @@ --- external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml Locale: en-US +no-loc: +- Target Module Name: Microsoft.PowerShell.Management -ms.date: 02/23/2024 +ms.date: 01/28/2026 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.management/new-item?view=powershell-7.4&WT.mc_id=ps-gethelp schema: 2.0.0 aliases: @@ -176,7 +178,7 @@ to verify the paths of the newly created files. ### Example 7: Create a symbolic link to a file or folder -This example creates a symbolic link to the Notice.txt file in the current folder. +This example creates a symbolic link to the `Notice.txt` file in the current folder. ```powershell $link = New-Item -ItemType SymbolicLink -Path .\link -Target .\Notice.txt diff --git a/reference/7.4/Microsoft.PowerShell.Management/Remove-Item.md b/reference/7.4/Microsoft.PowerShell.Management/Remove-Item.md index 7c234dc2b079..81a2f4302450 100644 --- a/reference/7.4/Microsoft.PowerShell.Management/Remove-Item.md +++ b/reference/7.4/Microsoft.PowerShell.Management/Remove-Item.md @@ -2,7 +2,7 @@ external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Management -ms.date: 02/14/2023 +ms.date: 01/28/2026 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.management/remove-item?view=powershell-7.4&WT.mc_id=ps-gethelp schema: 2.0.0 aliases: @@ -128,7 +128,18 @@ cmdlet interprets the subject of the search to be a file that has no child items fails. > [!NOTE] -> This behavior was fixed in Windows versions 1909 and up. +> Starting in Windows version 1909, specifying the file type in the **Path** parameter when using +> the **Recurse** parameter does recursively discover child items with the given file extension. +> +> In Windows version 1909 and later, the following statements will discover and remove the same +> files: +> +> ```powershell +> # Works in all versions of Windows: +> Get-ChildItem -Path * -Include *.csv -Recurse | Remove-Item +> # Only correctly finds and removes nested CSV files in Windows 1909 and later: +> Get-ChildItem -Path *.csv -Recurse | Remove-Item +> ``` ### Example 5: Delete subkeys recursively diff --git a/reference/7.5/Microsoft.PowerShell.Core/About/about_Module_Manifests.md b/reference/7.5/Microsoft.PowerShell.Core/About/about_Module_Manifests.md index 687286857b06..67a45d4c6cda 100644 --- a/reference/7.5/Microsoft.PowerShell.Core/About/about_Module_Manifests.md +++ b/reference/7.5/Microsoft.PowerShell.Core/About/about_Module_Manifests.md @@ -1,7 +1,13 @@ --- description: Describes the settings and practices for writing module manifest files. Locale: en-US -ms.date: 09/04/2025 +ms.date: 01/28/2026 +no-loc: +- Windows PowerShell 5.1 Workflow +- PowerShell Gallery +- Author +- Copyright +- Description online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_module_manifests?view=powershell-7.5&WT.mc_id=ps-gethelp schema: 2.0.0 title: about_Module_Manifests @@ -112,8 +118,8 @@ followed by a matrix that lists: - **Input type**: The object type that you can specify for this setting in the manifest. -- **Required**: If this value is `Yes`, the setting is required both to import - the module and to publish it to the PowerShell Gallery. If it's `No`, it's +- **Required**: If this value is "Yes", the setting is required both to import + the module and to publish it to the PowerShell Gallery. If it's "No", it's required for neither. If it's `PowerShell Gallery`, it's only required for publishing to the PowerShell Gallery. - **Value if unset**: The value this setting has when imported and not diff --git a/reference/7.5/Microsoft.PowerShell.Management/New-Item.md b/reference/7.5/Microsoft.PowerShell.Management/New-Item.md index 01047f04ccce..2d14c2cdf366 100644 --- a/reference/7.5/Microsoft.PowerShell.Management/New-Item.md +++ b/reference/7.5/Microsoft.PowerShell.Management/New-Item.md @@ -1,8 +1,10 @@ --- external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml Locale: en-US +no-loc: +- Target Module Name: Microsoft.PowerShell.Management -ms.date: 02/23/2024 +ms.date: 01/28/2026 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.management/new-item?view=powershell-7.5&WT.mc_id=ps-gethelp schema: 2.0.0 aliases: diff --git a/reference/7.5/Microsoft.PowerShell.Management/Remove-Item.md b/reference/7.5/Microsoft.PowerShell.Management/Remove-Item.md index 88f3cb7df400..9f460df0a757 100644 --- a/reference/7.5/Microsoft.PowerShell.Management/Remove-Item.md +++ b/reference/7.5/Microsoft.PowerShell.Management/Remove-Item.md @@ -2,7 +2,7 @@ external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Management -ms.date: 02/14/2023 +ms.date: 01/28/2026 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.management/remove-item?view=powershell-7.5&WT.mc_id=ps-gethelp schema: 2.0.0 aliases: @@ -128,7 +128,18 @@ cmdlet interprets the subject of the search to be a file that has no child items fails. > [!NOTE] -> This behavior was fixed in Windows versions 1909 and up. +> Starting in Windows version 1909, specifying the file type in the **Path** parameter when using +> the **Recurse** parameter does recursively discover child items with the given file extension. +> +> In Windows version 1909 and later, the following statements will discover and remove the same +> files: +> +> ```powershell +> # Works in all versions of Windows: +> Get-ChildItem -Path * -Include *.csv -Recurse | Remove-Item +> # Only correctly finds and removes nested CSV files in Windows 1909 and later: +> Get-ChildItem -Path *.csv -Recurse | Remove-Item +> ``` ### Example 5: Delete subkeys recursively diff --git a/reference/7.6/Microsoft.PowerShell.Core/About/about_Module_Manifests.md b/reference/7.6/Microsoft.PowerShell.Core/About/about_Module_Manifests.md index 39688a9499f2..c7f2be58e63b 100644 --- a/reference/7.6/Microsoft.PowerShell.Core/About/about_Module_Manifests.md +++ b/reference/7.6/Microsoft.PowerShell.Core/About/about_Module_Manifests.md @@ -1,7 +1,13 @@ --- description: Describes the settings and practices for writing module manifest files. Locale: en-US -ms.date: 09/04/2025 +ms.date: 01/28/2026 +no-loc: +- Windows PowerShell 5.1 Workflow +- PowerShell Gallery +- Author +- Copyright +- Description online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_module_manifests?view=powershell-7.6&WT.mc_id=ps-gethelp schema: 2.0.0 title: about_Module_Manifests @@ -112,8 +118,8 @@ followed by a matrix that lists: - **Input type**: The object type that you can specify for this setting in the manifest. -- **Required**: If this value is `Yes`, the setting is required both to import - the module and to publish it to the PowerShell Gallery. If it's `No`, it's +- **Required**: If this value is "Yes", the setting is required both to import + the module and to publish it to the PowerShell Gallery. If it's "No", it's required for neither. If it's `PowerShell Gallery`, it's only required for publishing to the PowerShell Gallery. - **Value if unset**: The value this setting has when imported and not diff --git a/reference/7.6/Microsoft.PowerShell.Management/New-Item.md b/reference/7.6/Microsoft.PowerShell.Management/New-Item.md index 7362cf4bfc66..d01c969acfc7 100644 --- a/reference/7.6/Microsoft.PowerShell.Management/New-Item.md +++ b/reference/7.6/Microsoft.PowerShell.Management/New-Item.md @@ -1,8 +1,10 @@ --- external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml Locale: en-US +no-loc: +- Target Module Name: Microsoft.PowerShell.Management -ms.date: 02/23/2024 +ms.date: 01/28/2026 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.management/new-item?view=powershell-7.6&WT.mc_id=ps-gethelp schema: 2.0.0 aliases: diff --git a/reference/7.6/Microsoft.PowerShell.Management/Remove-Item.md b/reference/7.6/Microsoft.PowerShell.Management/Remove-Item.md index 5aeacc12b179..6e233fd54a8c 100644 --- a/reference/7.6/Microsoft.PowerShell.Management/Remove-Item.md +++ b/reference/7.6/Microsoft.PowerShell.Management/Remove-Item.md @@ -2,7 +2,7 @@ external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Management -ms.date: 02/14/2023 +ms.date: 01/28/2026 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.management/remove-item?view=powershell-7.6&WT.mc_id=ps-gethelp schema: 2.0.0 aliases: @@ -128,7 +128,18 @@ cmdlet interprets the subject of the search to be a file that has no child items fails. > [!NOTE] -> This behavior was fixed in Windows versions 1909 and up. +> Starting in Windows version 1909, specifying the file type in the **Path** parameter when using +> the **Recurse** parameter does recursively discover child items with the given file extension. +> +> In Windows version 1909 and later, the following statements will discover and remove the same +> files: +> +> ```powershell +> # Works in all versions of Windows: +> Get-ChildItem -Path * -Include *.csv -Recurse | Remove-Item +> # Only correctly finds and removes nested CSV files in Windows 1909 and later: +> Get-ChildItem -Path *.csv -Recurse | Remove-Item +> ``` ### Example 5: Delete subkeys recursively