Skip to content

4/15/2025 PM Publish #12008

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
Apr 15, 2025
Merged

4/15/2025 PM Publish #12008

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1cac3f7
Fix typo (#12006)
sdwheeler Apr 15, 2025
36a2e21
`Get-Process` fixes and refresh (#12007)
surfingoldelephant Apr 15, 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
334 changes: 178 additions & 156 deletions reference/5.1/Microsoft.PowerShell.Management/Get-Process.md
View file
Open in desktop

Large diffs are not rendered by default.

6 changes: 3 additions & 3 deletions reference/5.1/Microsoft.PowerShell.Security/Set-ExecutionPolicy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
external help file: Microsoft.PowerShell.Security.dll-Help.xml
Locale: en-US
Module Name: Microsoft.PowerShell.Security
ms.date: 03/04/2024
ms.date: 04/15/2025
online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.security/set-executionpolicy?view=powershell-5.1&WT.mc_id=ps-gethelp
schema: 2.0.0
title: Set-ExecutionPolicy
Expand Down Expand Up @@ -140,7 +140,7 @@ The effective execution policy for the user becomes `AllSigned`.

### Example 5: Remove the execution policy for the current user

This example shows how use the `Undefined` execution policy to remove an execution policy for a
This example shows how to use the `Undefined` execution policy to remove an execution policy for a
specified scope.

```powershell
Expand Down Expand Up @@ -231,7 +231,7 @@ policy. The policy is set for the default scope, `LocalMachine`.
The `Get-ExecutionPolicy` cmdlet shows that `RemoteSigned` is the effective execution policy for
the current PowerShell session.

The `Start-ActivityTracker.ps1 script is executed from the current directory. The script is blocked
The `Start-ActivityTracker.ps1` script is executed from the current directory. The script is blocked
by `RemoteSigned` because the script isn't digitally signed.

For this example, the script's code was reviewed and verified as safe to run. The `Unblock-File`
Expand Down
295 changes: 169 additions & 126 deletions reference/7.4/Microsoft.PowerShell.Management/Get-Process.md
View file
Open in desktop

Large diffs are not rendered by default.

9 changes: 5 additions & 4 deletions reference/7.4/Microsoft.PowerShell.Security/Set-ExecutionPolicy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
external help file: Microsoft.PowerShell.Security.dll-Help.xml
Locale: en-US
Module Name: Microsoft.PowerShell.Security
ms.date: 03/04/2024
ms.date: 04/15/2025
online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.security/set-executionpolicy?view=powershell-7.4&WT.mc_id=ps-gethelp
schema: 2.0.0
title: Set-ExecutionPolicy
Expand All @@ -25,7 +25,8 @@ Set-ExecutionPolicy [-ExecutionPolicy] <ExecutionPolicy> [[-Scope] <ExecutionPol
## DESCRIPTION

The `Set-ExecutionPolicy` cmdlet changes PowerShell execution policies for Windows computers. For
more information, see [about_Execution_Policies](../Microsoft.PowerShell.Core/about/about_Execution_Policies.md).
more information, see
[about_Execution_Policies](../Microsoft.PowerShell.Core/about/about_Execution_Policies.md).

Beginning in PowerShell 6.0 for non-Windows computers, the default execution policy is
`Unrestricted` and can't be changed. The `Set-ExecutionPolicy` cmdlet is available, but PowerShell
Expand Down Expand Up @@ -144,7 +145,7 @@ The effective execution policy for the user becomes `AllSigned`.

### Example 5: Remove the execution policy for the current user

This example shows how use the `Undefined` execution policy to remove an execution policy for a
This example shows how to use the `Undefined` execution policy to remove an execution policy for a
specified scope.

```powershell
Expand Down Expand Up @@ -235,7 +236,7 @@ policy. The policy is set for the default scope, `LocalMachine`.
The `Get-ExecutionPolicy` cmdlet shows that `RemoteSigned` is the effective execution policy for
the current PowerShell session.

The `Start-ActivityTracker.ps1 script is executed from the current directory. The script is blocked
The `Start-ActivityTracker.ps1` script is executed from the current directory. The script is blocked
by `RemoteSigned` because the script isn't digitally signed.

For this example, the script's code was reviewed and verified as safe to run. The `Unblock-File`
Expand Down
294 changes: 168 additions & 126 deletions reference/7.5/Microsoft.PowerShell.Management/Get-Process.md
View file
Open in desktop

Large diffs are not rendered by default.

4 changes: 2 additions & 2 deletions reference/7.5/Microsoft.PowerShell.Security/Set-ExecutionPolicy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
external help file: Microsoft.PowerShell.Security.dll-Help.xml
Locale: en-US
Module Name: Microsoft.PowerShell.Security
ms.date: 03/04/2024
ms.date: 04/15/2025
online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.security/set-executionpolicy?view=powershell-7.5&WT.mc_id=ps-gethelp
schema: 2.0.0
title: Set-ExecutionPolicy
Expand Down Expand Up @@ -145,7 +145,7 @@ The effective execution policy for the user becomes `AllSigned`.

### Example 5: Remove the execution policy for the current user

This example shows how use the `Undefined` execution policy to remove an execution policy for a
This example shows how to use the `Undefined` execution policy to remove an execution policy for a
specified scope.

```powershell
Expand Down
294 changes: 168 additions & 126 deletions reference/7.6/Microsoft.PowerShell.Management/Get-Process.md
View file
Open in desktop

Large diffs are not rendered by default.

7 changes: 4 additions & 3 deletions reference/7.6/Microsoft.PowerShell.Security/Set-ExecutionPolicy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
external help file: Microsoft.PowerShell.Security.dll-Help.xml
Locale: en-US
Module Name: Microsoft.PowerShell.Security
ms.date: 03/04/2024
ms.date: 04/15/2025
online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.security/set-executionpolicy?view=powershell-7.6&WT.mc_id=ps-gethelp
schema: 2.0.0
title: Set-ExecutionPolicy
Expand All @@ -25,7 +25,8 @@ Set-ExecutionPolicy [-ExecutionPolicy] <ExecutionPolicy> [[-Scope] <ExecutionPol
## DESCRIPTION

The `Set-ExecutionPolicy` cmdlet changes PowerShell execution policies for Windows computers. For
more information, see [about_Execution_Policies](../Microsoft.PowerShell.Core/about/about_Execution_Policies.md).
more information, see
[about_Execution_Policies](../Microsoft.PowerShell.Core/about/about_Execution_Policies.md).

Beginning in PowerShell 6.0 for non-Windows computers, the default execution policy is
`Unrestricted` and can't be changed. The `Set-ExecutionPolicy` cmdlet is available, but PowerShell
Expand Down Expand Up @@ -144,7 +145,7 @@ The effective execution policy for the user becomes `AllSigned`.

### Example 5: Remove the execution policy for the current user

This example shows how use the `Undefined` execution policy to remove an execution policy for a
This example shows how to use the `Undefined` execution policy to remove an execution policy for a
specified scope.

```powershell
Expand Down