Update release notes and other docs for PS7.6-p5 release

reference/7.4/PSReadLine/About/about_PSReadLine_Functions.md

@@ -3,7 +3,7 @@ description: >
     This article documents the functions provided by PSReadLine. These functions
     can be bound to keystrokes for easy access and invocation.
 Locale: en-US
-ms.date: 03/03/2025
+ms.date: 10/01/2025
 online version: https://learn.microsoft.com/powershell/module/psreadline/about/about_psreadline_functions?view=powershell-7.4&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about_PSReadLine_Functions
@@ -1179,9 +1179,13 @@ Similarly, you can use this with other operations, like `<Delete>` or
 
 ### InvokePrompt
 
-Erases the current prompt and calls the prompt function to redisplay the
-prompt. Useful for custom key handlers that change state. For example, change
-the current directory.
+Attempt to erase the current prompt and call the prompt function to redisplay
+the prompt. Useful for custom key handlers that change state. For example,
+change the current directory. This method can't overwrite a prompt that has
+left the screen buffer.
+
+Calls to InvokePrompt with no Y position argument immediately return if the
+prompt can't be overwritten. This change was made in PSReadLine v2.4.3-beta3.
 
 - Function is unbound.
 

reference/7.5/PSReadLine/About/about_PSReadLine_Functions.md

@@ -3,7 +3,7 @@ description: >
     This article documents the functions provided by PSReadLine. These functions
     can be bound to keystrokes for easy access and invocation.
 Locale: en-US
-ms.date: 03/03/2025
+ms.date: 10/01/2025
 online version: https://learn.microsoft.com/powershell/module/psreadline/about/about_psreadline_functions?view=powershell-7.5&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about_PSReadLine_Functions
@@ -1179,9 +1179,13 @@ Similarly, you can use this with other operations, like `<Delete>` or
 
 ### InvokePrompt
 
-Erases the current prompt and calls the prompt function to redisplay the
-prompt. Useful for custom key handlers that change state. For example, change
-the current directory.
+Attempt to erase the current prompt and call the prompt function to redisplay
+the prompt. Useful for custom key handlers that change state. For example,
+change the current directory. This method can't overwrite a prompt that has
+left the screen buffer.
+
+Calls to InvokePrompt with no Y position argument immediately return if the
+prompt can't be overwritten. This change was made in PSReadLine v2.4.3-beta3.
 
 - Function is unbound.
 

reference/7.6/Microsoft.PowerShell.Core/About/about_Arrays.md

@@ -1,7 +1,7 @@
 ---
 description: Describes arrays, which are data structures designed to store collections of items.
 Locale: en-US
-ms.date: 01/03/2025
+ms.date: 10/01/2025
 no-loc: [Count, Length, LongLength, Rank, ForEach, Clear, Default, First, Last, SkipUntil, Until, Split, Tuple]
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_arrays?view=powershell-7.6&WT.mc_id=ps-gethelp
 schema: 2.0.0
@@ -515,6 +515,13 @@ ForEach(string methodName)
 ForEach(string methodName, object[] arguments)
 ```
 
+PowerShell 7.6-preview.5 added `PSForEach()` as an alias for the `ForEach()`
+method and `PSWhere()` as an alias for the `Where()` method. Use these aliases
+to avoid conflicts with `ForEach()` and `Where()` that might be defined on the
+base class of the object. For example, the `System.Collections.Generic.List<T>`
+class defines its own `ForEach()` method. Use `PSForEach()` to avoid calling
+the base class method.
+
 #### ForEach(scriptblock expression)
 
 #### ForEach(scriptblock expression, object[] arguments)
@@ -671,6 +678,13 @@ hi
 there
 ```
 
+PowerShell 7.6-preview.5 added `PSForEach()` as an alias for the `ForEach()`
+method and `PSWhere()` as an alias for the `Where()` method. Use these aliases
+to avoid conflicts with `ForEach()` and `Where()` that might be defined on the
+base class of the object. For example, the `System.Collections.Generic.List<T>`
+class defines its own `ForEach()` method. Use `PSForEach()` to avoid calling
+the base class method.
+
 #### Default
 
 The `Default` mode filters items using the `Expression` scriptblock.

reference/7.6/Microsoft.PowerShell.Core/About/about_Environment_Variables.md

@@ -1,7 +1,7 @@
 ---
 description: Describes how to access and manage environment variables in PowerShell.
 Locale: en-US
-ms.date: 08/27/2025
+ms.date: 10/01/2025
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_environment_variables?view=powershell-7.6&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about_Environment_Variables
@@ -20,6 +20,7 @@ programs. PowerShell creates the following environment variables:
 - `POWERSHELL_TELEMETRY_OPTOUT`
 - `POWERSHELL_DISTRIBUTION_CHANNEL`
 - `POWERSHELL_UPDATECHECK`
+- `POWERSHELL_DIAGNOSTICS_OPTOUT`
 - `PSExecutionPolicyPreference`
 - `PSModulePath`
 - `PSModuleAnalysisCachePath`
@@ -413,6 +414,21 @@ The environment variables that store preferences include:
   PowerShell process. See the previous sections for information about creating
   persistent environment variables.
 
+- `POWERSHELL_DIAGNOSTICS_OPTOUT`
+
+  This environment variable was added in PowerShell 7.6-preview.5. By default,
+  PowerShell creates a named pipe that is uses for Interprocess Communication
+  (IPC), such as `Enter-PSHostProcess`. PowerShell creates the named pipe at
+  startup so that it's available for use when needed.
+
+  On non-Windows platforms, named pipes are implemented as files in the `/tmp`
+  folder. If PowerShell crashes, these files may not be deleted. Over time,
+  these files can accumulate.
+
+  Beginning in PowerShell 7.6, `POWERSHELL_DIAGNOSTICS_OPTOUT` is set to
+  `false`. To turn off the creation of the named pipe, set the environment
+  variable to `true`, `yes`, or `1`.
+
 - `PSExecutionPolicyPreference`
 
   Stores the execution policy set for the current session. This environment

reference/7.6/Microsoft.PowerShell.Core/About/about_Intrinsic_Members.md

@@ -1,7 +1,7 @@
 ---
 description: Describes automatic members in all PowerShell objects
 Locale: en-US
-ms.date: 01/03/2025
+ms.date: 10/01/2025
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_Intrinsic_Members?view=powershell-7.6&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about_Intrinsic_Members
@@ -165,6 +165,13 @@ The `ForEach()` and `Where()` methods are available to all PowerShell objects.
 However, they're most useful when working with collections. For more
 information on how to use these methods, see [about_Arrays][01].
 
+PowerShell 7.6-preview.5 added `PSForEach()` as an alias for the `ForEach()`
+method and `PSWhere()` as an alias for the `Where()` method. Use these aliases
+to avoid conflicts with `ForEach()` and `Where()` that might be defined on the
+base class of the object. For example, the `System.Collections.Generic.List<T>`
+class defines its own `ForEach()` method. Use `PSForEach()` to avoid calling
+the base class method.
+
 ## Properties
 
 Not all scalar type have **Count** or **Length** properties in the base type.

reference/7.6/Microsoft.PowerShell.Core/Register-ArgumentCompleter.md

@@ -19,15 +19,21 @@ Registers a custom argument completer.
 ### NativeSet
 
 ```
-Register-ArgumentCompleter -CommandName <String[]> -ScriptBlock <ScriptBlock> [-Native]
+Register-ArgumentCompleter -CommandName <string[]> -ScriptBlock <scriptblock> [-Native]
  [<CommonParameters>]
 ```
 
 ### PowerShellSet
 
 ```
-Register-ArgumentCompleter [-CommandName <String[]>] -ParameterName <String>
- -ScriptBlock <ScriptBlock> [<CommonParameters>]
+Register-ArgumentCompleter -ParameterName <string> -ScriptBlock <scriptblock>
+ [-CommandName <string[]>] [<CommonParameters>]
+```
+
+### NativeFallbackSet
+
+```
+Register-ArgumentCompleter -ScriptBlock <scriptblock> [-NativeFallback] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
@@ -220,6 +226,30 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -NativeFallback
+
+When you use this parameter, PowerShell registers a cover-all argument completer for native
+commands. When a native command doesn't have a specific completer for it, it uses the cover-all
+completer. A cover-all completer allows a module like Microsoft.PowerShell.UnixTabCompletion to be
+registered to provide tab completion for many native commands on Linux and macOS systems.
+
+> [!NOTE]
+> You can only register one cover-all completer.
+
+This parameter was added in PowerShell 7.6-preview.5.
+
+```yaml
+Type: System.Management.Automation.SwitchParameter
+Parameter Sets: NativeFallbackSet
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -ParameterName
 
 Specifies the name of the parameter the argument completer applies to. The type for specified

reference/7.6/PSDiagnostics/Disable-PSTrace.md

@@ -2,7 +2,7 @@
 external help file: PSDiagnostics-help.xml
 Locale: en-US
 Module Name: PSDiagnostics
-ms.date: 12/12/2022
+ms.date: 10/01/2025
 online version: https://learn.microsoft.com/powershell/module/psdiagnostics/disable-pstrace?view=powershell-7.6&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: Disable-PSTrace
@@ -11,7 +11,7 @@ title: Disable-PSTrace
 # Disable-PSTrace
 
 ## SYNOPSIS
-Disables the Microsoft-Windows-PowerShell event provider logs.
+Disables the PowerShellCore event provider logs.
 
 ## SYNTAX
 
@@ -23,16 +23,20 @@ Disable-PSTrace [-AnalyticOnly] [<CommonParameters>]
 
 > **This cmdlet is only available on the Windows platform.**
 
-This cmdlet disables the Operational and Analytic event logs of the Microsoft-Windows-PowerShell
+This cmdlet disables the Operational and Analytic event logs of the PowerShellCore
 event provider.
 
 You must run this cmdlet from an elevated PowerShell session.
 
+> [!NOTE]
+> Prior to PowerShell 7.6, this command only disabled logging for the Microsoft-Windows-PowerShell
+> event provider.
+
 ## EXAMPLES
 
 ### Example 1: Disable the Analytic event log for PowerShell
 
-The following example disables only the Analytic event log of the Microsoft-Windows-PowerShell
+The following example disables only the Analytic event log of the PowerShellCore
 provider.
 
 ```powershell
@@ -43,8 +47,8 @@ Disable-PSTrace -AnalyticOnly
 
 ### -AnalyticOnly
 
-When this parameter is used, the cmdlet disables the Analytic event log of the
-Microsoft-Windows-PowerShell provider. The Operational event log is not changed.
+When this parameter is used, the cmdlet disables the Analytic event log of the PowerShellCore
+provider. The Operational event log is not changed.
 
 ```yaml
 Type: System.Management.Automation.SwitchParameter

reference/7.6/PSDiagnostics/Enable-PSTrace.md

@@ -2,7 +2,7 @@
 external help file: PSDiagnostics-help.xml
 Locale: en-US
 Module Name: PSDiagnostics
-ms.date: 12/12/2022
+ms.date: 10/01/2025
 online version: https://learn.microsoft.com/powershell/module/psdiagnostics/enable-pstrace?view=powershell-7.6&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: Enable-PSTrace
@@ -11,7 +11,7 @@ title: Enable-PSTrace
 # Enable-PSTrace
 
 ## SYNOPSIS
-Enables the Microsoft-Windows-PowerShell event provider logs.
+Enables the PowerShellCore event provider logs.
 
 ## SYNTAX
 
@@ -23,16 +23,20 @@ Enable-PSTrace [-Force] [-AnalyticOnly] [<CommonParameters>]
 
 > **This cmdlet is only available on the Windows platform.**
 
-This cmdlet enables the Operational and Analytic event logs of the Microsoft-Windows-PowerShell
+This cmdlet enables the Operational and Analytic event logs of the PowerShellCore
 event provider.
 
 You must run this cmdlet from an elevated PowerShell session.
 
+> [!NOTE]
+> Prior to PowerShell 7.6, this command only enabled logging for the Microsoft-Windows-PowerShell
+> event provider.
+
 ## EXAMPLES
 
 ### Example 1: Enable the Analytic event log for PowerShell
 
-The following example enables only the Analytic event log of the Microsoft-Windows-PowerShell
+The following example enables only the Analytic event log of the PowerShellCore
 provider.
 
 ```powershell
@@ -44,7 +48,7 @@ Enable-PSTrace -AnalyticOnly
 ### -AnalyticOnly
 
 When this parameter is used, the cmdlet enables the Analytic event log of the
-Microsoft-Windows-PowerShell provider. The Operational event log is not changed.
+PowerShellCore provider. The Operational event log is not changed.
 
 ```yaml
 Type: System.Management.Automation.SwitchParameter

reference/7.6/PSReadLine/About/about_PSReadLine_Functions.md

@@ -3,7 +3,7 @@ description: >
     This article documents the functions provided by PSReadLine. These functions
     can be bound to keystrokes for easy access and invocation.
 Locale: en-US
-ms.date: 03/03/2025
+ms.date: 10/01/2025
 online version: https://learn.microsoft.com/powershell/module/psreadline/about/about_psreadline_functions?view=powershell-7.6&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about_PSReadLine_Functions
@@ -1179,9 +1179,13 @@ Similarly, you can use this with other operations, like `<Delete>` or
 
 ### InvokePrompt
 
-Erases the current prompt and calls the prompt function to redisplay the
-prompt. Useful for custom key handlers that change state. For example, change
-the current directory.
+Attempt to erase the current prompt and call the prompt function to redisplay
+the prompt. Useful for custom key handlers that change state. For example,
+change the current directory. This method can't overwrite a prompt that has
+left the screen buffer.
+
+Calls to InvokePrompt with no Y position argument immediately return if the
+prompt can't be overwritten. This change was made in PSReadLine v2.4.3-beta3.
 
 - Function is unbound.
 

reference/docs-conceptual/install/Installing-PowerShell-on-Windows.md

@@ -1,6 +1,6 @@
 ---
 description: Information about installing PowerShell on Windows
-ms.date: 10/09/2025
+ms.date: 10/01/2025
 title: Installing PowerShell on Windows
 ---
 # Installing PowerShell on Windows
@@ -42,7 +42,7 @@ winget search Microsoft.PowerShell
 Name               Id                           Version Source
 ---------------------------------------------------------------
 PowerShell         Microsoft.PowerShell         7.5.3.0 winget
-PowerShell Preview Microsoft.PowerShell.Preview 7.6.0.4 winget
+PowerShell Preview Microsoft.PowerShell.Preview 7.6.0.5 winget
 ```
 
 Install PowerShell or PowerShell Preview using the `id` parameter

reference/docs-conceptual/install/install-rhel.md

@@ -1,6 +1,6 @@
 ---
 description: Information about installing PowerShell on Red Hat Enterprise Linux (RHEL)
-ms.date: 07/03/2025
+ms.date: 10/01/2025
 title: Installing PowerShell on Red Hat Enterprise Linux (RHEL)
 ---
 # Installing PowerShell on Red Hat Enterprise Linux (RHEL)
@@ -29,7 +29,7 @@ known as _PMC_.
 Installing PowerShell from PMC is the preferred method of installation.
 
 > [!NOTE]
-> This script only works for supported versions of RHEL.
+> This script only works for supported versions of RHEL that are published to PMC.
 
 ```sh
 ###################################
@@ -62,7 +62,8 @@ sudo dnf install powershell -y
 ## Installation via direct download
 
 PowerShell 7.2 introduced a universal package that makes installation easier. Download the universal
-package from the [releases][02] page onto your RHEL machine.
+package from the [releases][02] page onto your RHEL machine. Use this method to install PowerShell
+on systems running RHEL 10.
 
 The link to the current version is:
 

reference/docs-conceptual/security/security-features.md

@@ -111,7 +111,7 @@ security.
 > [!IMPORTANT]
 > You must use a secure transport layer to ensure secure data transfer over PSRP.
 
-Beginning in PowerShell v7.6-preview5, the key exchange was deprecated. The version of PSRP was
+Beginning in PowerShell v7.6-preview.5, the key exchange was deprecated. The version of PSRP was
 incremented to v2.4 and includes the following changes:
 
 - The following PSRP messages are deprecated when both client and server are v2.4 or higher: