11---
22description : Describes new features that are included in Windows PowerShell 5.1.
33Locale : en-US
4- ms.date : 10/23/2023
4+ ms.date : 04/01/2025
55online version : https://learn.microsoft.com/powershell/module/about_windows_powershell_5.1?view=powershell-5.1&WT.mc_id=ps-gethelp
66schema : 2.0.0
7- title : about_Windows_Powershell_5 .1
7+ title : about_Windows_PowerShell_5 .1
88---
99
1010# about_Windows_PowerShell_5.1
@@ -24,7 +24,7 @@ snap-ins, scripts, functions, and profiles that were designed for Windows
2424PowerShell 4.0, Windows PowerShell 3.0, and Windows PowerShell 2.0 generally
2525work in Windows PowerShell 5.1 without changes.
2626
27- - New cmdlets: local users and groups; Get-ComputerInfo
27+ - New cmdlets: local users and groups; ` Get-ComputerInfo `
2828- PowerShellGet improvements include enforcing signed modules, and installing
2929 JEA modules
3030- PackageManagement added support for Containers, CBS Setup, EXE-based setup,
@@ -37,11 +37,6 @@ work in Windows PowerShell 5.1 without changes.
3737Windows PowerShell 5.1 is installed by default on Windows Server version 2016
3838and higher and Windows client version 10 and higher.
3939
40- To install Windows PowerShell 5.1 on older versions of Windows, see
41- [ Install and Configure WMF 5.1] [ 09 ] . Be sure to read the download details, and
42- meet all system requirements, before you install Windows Management Framework
43- 5.1.
44-
4540You can also read about changes to Windows PowerShell 5.1 in
4641[ What's New in Windows PowerShell] [ 08 ] .
4742
@@ -57,7 +52,7 @@ denote varying feature sets and platform compatibility.
5752 and modules targeting versions of PowerShell running on reduced footprint
5853 editions of Windows such as Nano Server and Windows IoT.
5954
60- ** Learn more about using PowerShell Editions**
55+ Learn more about using PowerShell Editions
6156
6257- [ Determine running edition of PowerShell using $PSVersionTable] [ 04 ]
6358- [ Filter Get-Module results by CompatiblePSEditions using PSEdition parameter] [ 05 ]
@@ -77,7 +72,7 @@ distribute the set of folders along with corresponding catalog file
7772representing those folders. This information is useful to validate whether any
7873changes have been made to the folders since catalog creation time.
7974
80- ```
75+ ``` Syntax
8176New-FileCatalog [-CatalogFilePath] <string> [[-Path] <string[]>]
8277 [-CatalogVersion <int>] [-WhatIf] [-Confirm] [<CommonParameters>]
8378```
@@ -86,14 +81,14 @@ Catalog versions 1 and 2 are supported. Version 1 uses the SHA1 hashing
8681algorithm to create file hashes; version 2 uses SHA256. You should use catalog
8782version 2.
8883
89- To verify the integrity of catalog file (Pester.cat in above example), sign it
90- using [ Set-AuthenticodeSignature] [ 07 ] cmdlet.
84+ To verify the integrity of catalog file (` Pester.cat ` in above example), sign
85+ it using [ Set-AuthenticodeSignature] [ 07 ] cmdlet.
9186
9287#### Test-FileCatalog
9388
9489` Test-FileCatalog ` validates the catalog representing a set of folders.
9590
96- ```
91+ ``` Syntax
9792Test-FileCatalog [-Detailed] [-FilesToSkip <String[]>]
9893 [-CatalogFilePath] <String> [[-Path] <String[]>]
9994 [-WhatIf] [-Confirm] [<CommonParameters>]
@@ -113,12 +108,12 @@ Starting with WMF 5.1, PowerShell provides control over the file that's used
113108to cache data about a module, such as the commands it exports.
114109
115110By default, this cache is stored in the file
116- ` ${Env :LOCALAPPDATA}\Microsoft\Windows\PowerShell\ModuleAnalysisCache ` . The
111+ ` ${env :LOCALAPPDATA}\Microsoft\Windows\PowerShell\ModuleAnalysisCache ` . The
117112cache is typically read at startup while searching for a command and is written
118113on a background thread sometime after a module is imported.
119114
120115To change the default location of the cache, set the
121- ` $Env :PSModuleAnalysisCachePath ` environment variable before starting
116+ ` $env :PSModuleAnalysisCachePath ` environment variable before starting
122117PowerShell. Changes to this environment variable only affect child processes.
123118The value should name a full path (including filename) that PowerShell has
124119permission to create and write files. To disable the file cache, set this value
@@ -160,20 +155,15 @@ In WMF 5.1:
160155- You can use [ ModuleSpecification Constructor (Hashtable)] [ 01 ] . This hash
161156 table has the same format as ` Get-Module -FullyQualifiedName ` .
162157
163- ** Example:** ` using module @{ModuleName = 'PSReadLine'; RequiredVersion = '1.1'} `
158+ Example: ` using module @{ModuleName = 'PSReadLine'; RequiredVersion = '1.1'} `
164159
165160- If there are multiple versions of the module, PowerShell uses the ** same
166161 resolution logic** as ` Import-Module ` and doesn't return an error.
167162
168163### Improvements to Pester
169164
170- In WMF 5.1, the version of Pester that ships with PowerShell has been updated
171- from 3.3.5 to 3.4.0. You can review the changes in versions 3.3.5 to 3.4.0 by
172- inspecting the [ CHANGELOG] [ 11 ] in the GitHub repository.
173-
174- ## KEYWORDS
175-
176- What's New in Windows PowerShell 5.1
165+ WMF 5.1 ships with Pester v3.4.0. For more information about this version, see
166+ the [ CHANGELOG] [ 11 ] in the GitHub repository.
177167
178168<!-- link references -->
179169[ 01 ] : /dotnet/api/microsoft.powershell.commands.modulespecification.-ctor
@@ -184,6 +174,5 @@ What's New in Windows PowerShell 5.1
184174[ 06 ] : /powershell/module/microsoft.powershell.security/get-authenticodesignature
185175[ 07 ] : /powershell/module/microsoft.powershell.security/set-authenticodesignature
186176[ 08 ] : /powershell/scripting/windows-powershell/whats-new/what-s-new-in-windows-powershell-50
187- [ 09 ] : /powershell/scripting/wmf/setup/install-configure
188177[ 10 ] : /previous-versions/windows/powershell-scripting/hh847877(v=wps.640)
189178[ 11 ] : https://github.com/pester/Pester/blob/main/docs/CHANGELOG.md
0 commit comments