Updates from: 08/03/2021 03:10:51
Service Microsoft Docs article Related commit history on GitHub Change details
Microsoft.PowerShell.Utility Invoke Webrequest (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Utility/Invoke-WebRequest.md
external help file: Microsoft.PowerShell.Commands.Utility.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Utility Previously updated : 04/05/2021 Last updated : 08/02/2021 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.utility/invoke-webrequest?view=powershell-5.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: Invoke-WebRequest
This cmdlet was introduced in Windows PowerShell 3.0.
> By default, script code in the web page may be run when the page is being parsed to populate the > `ParsedHtml` property. Use the `-UseBasicParsing` switch to suppress this.
+> [!IMPORTANT]
+> The examples in this article reference hosts in the `constoso.com` domain. This is a fictitious
+> domain used by Microsoft for examples. The examples are designed to show how to use the cmdlets.
+> However, since the `contoso.com` sites do not exist, the examples do not work. Adapt the examples
+> to hosts in your environment.
+ ## Examples ### Example 1: Send a web request
Microsoft.PowerShell.Utility Invoke Webrequest (7.0) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Utility/Invoke-WebRequest.md
external help file: Microsoft.PowerShell.Commands.Utility.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Utility Previously updated : 04/05/2021 Last updated : 08/02/2021 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.utility/invoke-webrequest?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: Invoke-WebRequest
This cmdlet was introduced in PowerShell 3.0.
Beginning in PowerShell 7.0, `Invoke-WebRequest` supports proxy configuration defined by environment variables. See the [Notes](#notes) section of this article.
+> [!IMPORTANT]
+> The examples in this article reference hosts in the `constoso.com` domain. This is a fictitious
+> domain used by Microsoft for examples. The examples are designed to show how to use the cmdlets.
+> However, since the `contoso.com` sites do not exist, the examples do not work. Adapt the examples
+> to hosts in your environment.
+ ## Examples ### Example 1: Send a web request
Microsoft.PowerShell.Management Add Content (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Management/Add-Content.md
pages (like `-Encoding 1251`) or string names of registered code pages (like
[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2). > [!NOTE]
-> **UTF-7*** is no longer recommended to use. In PowerShell 7.1, a warning is written if you
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
> specify `utf7` for the **Encoding** parameter. ```yaml
Microsoft.PowerShell.Management Get Content (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Management/Get-Content.md
pages (like `-Encoding 1251`) or string names of registered code pages (like
[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2). > [!NOTE]
-> **UTF-7*** is no longer recommended to use. In PowerShell 7.1, a warning is written if you
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
> specify `utf7` for the **Encoding** parameter. ```yaml
Microsoft.PowerShell.Management Set Content (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Management/Set-Content.md
pages (like `-Encoding 1251`) or string names of registered code pages (like
[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2). > [!NOTE]
-> **UTF-7*** is no longer recommended to use. In PowerShell 7.1, a warning is written if you
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
> specify `utf7` for the **Encoding** parameter. ```yaml
Microsoft.PowerShell.Utility Export Clixml (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Utility/Export-Clixml.md
pages (like `-Encoding 1251`) or string names of registered code pages (like
[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2). > [!NOTE]
-> **UTF-7*** is no longer recommended to use. In PowerShell 7.1, a warning is written if you
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
> specify `utf7` for the **Encoding** parameter. ```yaml
Microsoft.PowerShell.Utility Export Csv (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Utility/Export-Csv.md
pages (like `-Encoding 1251`) or string names of registered code pages (like
[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2). > [!NOTE]
-> **UTF-7*** is no longer recommended to use. In PowerShell 7.1, a warning is written if you
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
> specify `utf7` for the **Encoding** parameter. ```yaml
Microsoft.PowerShell.Utility Format Hex (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Utility/Format-Hex.md
pages (like `-Encoding 1251`) or string names of registered code pages (like
[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2). > [!NOTE]
-> **UTF-7*** is no longer recommended to use. In PowerShell 7.1, a warning is written if you
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
> specify `utf7` for the **Encoding** parameter. ```yaml
Microsoft.PowerShell.Utility Import Csv (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Utility/Import-Csv.md
pages (like `-Encoding 1251`) or string names of registered code pages (like
[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2). > [!NOTE]
-> **UTF-7*** is no longer recommended to use. In PowerShell 7.1, a warning is written if you
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
> specify `utf7` for the **Encoding** parameter. ```yaml
Microsoft.PowerShell.Utility Invoke Webrequest (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Utility/Invoke-WebRequest.md
external help file: Microsoft.PowerShell.Commands.Utility.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Utility Previously updated : 04/05/2021 Last updated : 08/02/2021 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.utility/invoke-webrequest?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: Invoke-WebRequest
This cmdlet was introduced in PowerShell 3.0.
Beginning in PowerShell 7.0, `Invoke-WebRequest` supports proxy configuration defined by environment variables. See the [Notes](#notes) section of this article.
+> [!IMPORTANT]
+> The examples in this article reference hosts in the `constoso.com` domain. This is a fictitious
+> domain used by Microsoft for examples. The examples are designed to show how to use the cmdlets.
+> However, since the `contoso.com` sites do not exist, the examples do not work. Adapt the examples
+> to hosts in your environment.
+ ## Examples ### Example 1: Send a web request
Microsoft.PowerShell.Utility Out File (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Utility/Out-File.md
pages (like `-Encoding 1251`) or string names of registered code pages (like
[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2). > [!NOTE]
-> **UTF-7*** is no longer recommended to use. In PowerShell 7.1, a warning is written if you
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
> specify `utf7` for the **Encoding** parameter. ```yaml
Microsoft.PowerShell.Utility Select String (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Utility/Select-String.md
pages (like `-Encoding 1251`) or string names of registered code pages (like
[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2). > [!NOTE]
-> **UTF-7*** is no longer recommended to use. In PowerShell 7.1, a warning is written if you
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
> specify `utf7` for the **Encoding** parameter. ```yaml
Microsoft.PowerShell.Management Add Content (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Management/Add-Content.md
pages (like `-Encoding 1251`) or string names of registered code pages (like
[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2). > [!NOTE]
-> **UTF-7*** is no longer recommended to use. In PowerShell 7.1, a warning is written if you
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
> specify `utf7` for the **Encoding** parameter. ```yaml
Microsoft.PowerShell.Management Get Content (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Management/Get-Content.md
pages (like `-Encoding 1251`) or string names of registered code pages (like
[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2). > [!NOTE]
-> **UTF-7*** is no longer recommended to use. In PowerShell 7.1, a warning is written if you
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
> specify `utf7` for the **Encoding** parameter. ```yaml
Microsoft.PowerShell.Management Set Content (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Management/Set-Content.md
pages (like `-Encoding 1251`) or string names of registered code pages (like
[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2). > [!NOTE]
-> **UTF-7*** is no longer recommended to use. In PowerShell 7.1, a warning is written if you
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
> specify `utf7` for the **Encoding** parameter. ```yaml
Microsoft.PowerShell.Utility Export Clixml (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Utility/Export-Clixml.md
pages (like `-Encoding 1251`) or string names of registered code pages (like
[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2). > [!NOTE]
-> **UTF-7*** is no longer recommended to use. In PowerShell 7.1, a warning is written if you
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
> specify `utf7` for the **Encoding** parameter. ```yaml
Microsoft.PowerShell.Utility Export Csv (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Utility/Export-Csv.md
pages (like `-Encoding 1251`) or string names of registered code pages (like
[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2). > [!NOTE]
-> **UTF-7*** is no longer recommended to use. In PowerShell 7.1, a warning is written if you
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
> specify `utf7` for the **Encoding** parameter. ```yaml
Microsoft.PowerShell.Utility Format Hex (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Utility/Format-Hex.md
pages (like `-Encoding 1251`) or string names of registered code pages (like
[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2). > [!NOTE]
-> **UTF-7*** is no longer recommended to use. In PowerShell 7.1, a warning is written if you
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
> specify `utf7` for the **Encoding** parameter. ```yaml
Microsoft.PowerShell.Utility Import Csv (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Utility/Import-Csv.md
pages (like `-Encoding 1251`) or string names of registered code pages (like
[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2). > [!NOTE]
-> **UTF-7*** is no longer recommended to use. In PowerShell 7.1, a warning is written if you
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
> specify `utf7` for the **Encoding** parameter. ```yaml
Microsoft.PowerShell.Utility Invoke Webrequest (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Utility/Invoke-WebRequest.md
external help file: Microsoft.PowerShell.Commands.Utility.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Utility Previously updated : 04/05/2021 Last updated : 08/02/2021 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.utility/invoke-webrequest?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: Invoke-WebRequest
This cmdlet was introduced in PowerShell 3.0.
Beginning in PowerShell 7.0, `Invoke-WebRequest` supports proxy configuration defined by environment variables. See the [Notes](#notes) section of this article.
+> [!IMPORTANT]
+> The examples in this article reference hosts in the `constoso.com` domain. This is a fictitious
+> domain used by Microsoft for examples. The examples are designed to show how to use the cmdlets.
+> However, since the `contoso.com` sites do not exist, the examples do not work. Adapt the examples
+> to hosts in your environment.
+ ## Examples ### Example 1: Send a web request
Microsoft.PowerShell.Utility Out File (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Utility/Out-File.md
pages (like `-Encoding 1251`) or string names of registered code pages (like
[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2). > [!NOTE]
-> **UTF-7*** is no longer recommended to use. In PowerShell 7.1, a warning is written if you
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
> specify `utf7` for the **Encoding** parameter. ```yaml
Microsoft.PowerShell.Utility Select String (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Utility/Select-String.md
pages (like `-Encoding 1251`) or string names of registered code pages (like
[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2). > [!NOTE]
-> **UTF-7*** is no longer recommended to use. In PowerShell 7.1, a warning is written if you
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
> specify `utf7` for the **Encoding** parameter. ```yaml
Microsoft.PowerShell.Utility Tee Object (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Utility/Tee-Object.md
external help file: Microsoft.PowerShell.Commands.Utility.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Utility Previously updated : 06/09/2017 Last updated : 08/02/2021 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.utility/tee-object?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: Tee-Object
Saves command output in a file or variable and also sends it down the pipeline.
### File (Default) ```
-Tee-Object [-InputObject <PSObject>] [-FilePath] <String> [-Append] [<CommonParameters>]
+Tee-Object [-InputObject <PSObject>] [-FilePath] <String> [-Append] [[-Encoding] <Encoding>] [<CommonParameters>]
``` ### LiteralFile ```
-Tee-Object [-InputObject <PSObject>] -LiteralPath <String> [<CommonParameters>]
+Tee-Object [-InputObject <PSObject>] -LiteralPath <String> [[-Encoding] <Encoding>] [<CommonParameters>]
``` ### Variable
Accept pipeline input: False
Accept wildcard characters: True ```
+### -Encoding
+
+Specifies the type of encoding for the target file. The default value is `utf8NoBOM`.
+
+The acceptable values for this parameter are as follows:
+
+- `ascii`: Uses the encoding for the ASCII (7-bit) character set.
+- `bigendianunicode`: Encodes in UTF-16 format using the big-endian byte order.
+- `oem`: Uses the default encoding for MS-DOS and console programs.
+- `unicode`: Encodes in UTF-16 format using the little-endian byte order.
+- `utf7`: Encodes in UTF-7 format.
+- `utf8`: Encodes in UTF-8 format.
+- `utf8BOM`: Encodes in UTF-8 format with Byte Order Mark (BOM)
+- `utf8NoBOM`: Encodes in UTF-8 format without Byte Order Mark (BOM)
+- `utf32`: Encodes in UTF-32 format.
+
+Beginning with PowerShell 6.2, the **Encoding** parameter also allows numeric IDs of registered code
+pages (like `-Encoding 1251`) or string names of registered code pages (like
+`-Encoding "windows-1251"`). For more information, see the .NET documentation for
+[Encoding.CodePage](/dotnet/api/system.text.encoding.codepage?view=netcore-2.2).
+
+This parameter was introduced in PowerShell 7.2.
+
+> [!NOTE]
+> **UTF-7*** is no longer recommended to use. As of PowerShell 7.1, a warning is written if you
+> specify `utf7` for the **Encoding** parameter.
+
+```yaml
+Type: System.Text.Encoding
+Parameter Sets: (All)
+Aliases:
+Accepted values: ASCII, BigEndianUnicode, OEM, Unicode, UTF7, UTF8, UTF8BOM, UTF8NoBOM, UTF32
+
+Required: False
+Position: 1
+Default value: UTF8NoBOM
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+ ### -InputObject Specifies the object to be saved and displayed. Enter a variable that contains the objects or type a
community 2021 Updates https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/docs-conceptual/community/2021-updates.md
--- Title: What's New in PowerShell-Docs for 2021 description: List of changes to the PowerShell documentation for 2021 Previously updated : 07/02/2021 Last updated : 08/02/2021 --- # What's new in PowerShell Docs for 2021
contributions from the community.
Help us make the documentation better for you. Read the [Contributor's Guide][contrib] to learn how to get started.
+## 2021-July
+
+New content
+
+- [about_Functions_Argument_Completion](/powershell/module/microsoft.powershell.core/about/about_functions_argument_completion)
+- [about_Tab_Expansion](/powershell/module/microsoft.powershell.core/about/about_Tab_Expansion)
+
+Content updates
+
+- [about_Functions_Advanced_Parameters](/powershell/module/microsoft.powershell.core/about/about_functions_advanced_parameters) - major updates and links to new articles
+- PowerShell 7.2-preview.8 documentation updates
+
+### Top Community Contributors
+
+GitHub stats
+
+- 51 PRs merged (9 from Community)
+- 56 issues opened (50 from Community)
+- 59 issues closed (52 Community issues closed)
+
+The following people have contributed to PowerShell docs by submitting pull requests or filing
+issues. Thank you!
+
+| GitHub Id | PRs merged | Issues opened |
+| ------------- | :--------: | :-----------: |
+| rkeithhill | 2 | |
+| juvtib | 2 | |
+| SetTrend | 1 | |
+| Rob-S | 1 | |
+| xtqqczze | 1 | |
+| akashdabhi03 | 1 | |
+| kurtmckee | 1 | |
+| clamb123 | | 13 |
+| mklement0 | | 2 |
+| jerryKahnPerl | | 2 |
+ ## 2021-June New content
community Hall Of Fame https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/docs-conceptual/community/hall-of-fame.md
--- Title: Community contributor Hall of Fame description: List of the GitHub users that have the most contributions to the PowerShell-Doc project. Previously updated : 05/03/2021 Last updated : 08/02/2021 --- # Community Contributor Hall of Fame
Pull Requests help us fix those issues and make the documentation better for eve
| Docs PRs Merged | 2015 | 2016 | 2017 | 2018 | 2019 | 2020 | 2021 | Grand Total | | --------------- | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ----------: |
-| Community | 3 | 194 | 446 | 467 | 321 | 162 | 37 | 1630 |
+| Community | 3 | 194 | 446 | 464 | 318 | 161 | 52 | 1638 |
| matt9ucci | | | 157 | 80 | 30 | 1 | 2 | 270 | | nschonni | | | | 14 | 138 | 10 | | 162 |
-| kiazhi | | 25 | 78 | 12 | | | | 115 |
+| kiazhi | | 25 | 79 | 12 | | | | 116 |
| alexandair | | 57 | 7 | 26 | 2 | 1 | | 93 | | doctordns | | 5 | 32 | 20 | 7 | 9 | | 73 |
-| sethvs | | | 1 | 44 | | 20 | | 65 |
+| sethvs | | | 1 | 43 | | 20 | | 64 |
| yecril71pl | | | | | | 21 | | 21 | | Dan1el42 | | 20 | | | | | | 20 | | NReilingh | | 2 | | 13 | 3 | | | 18 | | it-praktyk | | | | 16 | 1 | | | 17 | | vors | | 15 | 1 | | | | | 16 | | markekraus | | | 11 | 5 | | | | 16 |
-| kvprasoon | | 2 | 1 | 7 | 2 | 2 | | 14 |
-| purdo17 | | | | 13 | | | | 13 |
-| skycommand | | | 1 | 3 | 3 | 6 | | 13 |
+| kvprasoon | | 2 | 1 | 7 | 2 | 2 | 2 | 16 |
| k-takai | | | | 5 | 1 | 7 | | 13 |
+| skycommand | | | 1 | 3 | 3 | 6 | | 13 |
+| purdo17 | | | | 13 | | | | 13 |
| PlagueHO | | 10 | | | 1 | | | 11 | | exchange12rocks | | | 7 | 3 | | | 1 | 11 |
GitHub issues help us identify errors and gaps in our documentation.
| Docs Issues Opened | 2015 | 2016 | 2017 | 2018 | 2019 | 2020 | 2021 | Grand Total | | ------------------ | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ----------: |
-| Community | 3 | 54 | 95 | 213 | 575 | 584 | 210 | 1734 |
-| mklement0 | | | 19 | 60 | 56 | 61 | 14 | 210 |
-| iSazonov | | | 1 | 4 | 10 | 8 | 1 | 24 |
+| Community | 3 | 54 | 95 | 212 | 567 | 564 | 236 | 1731 |
+| mklement0 | | | 19 | 60 | 56 | 61 | 16 | 212 |
| jszabo98 | | | | 2 | 15 | 6 | 1 | 24 |
+| iSazonov | | | 1 | 4 | 10 | 8 | 1 | 24 |
| juvtib | | | | | | 15 | 7 | 22 |
-| doctordns | | | 5 | 3 | 5 | 7 | | 20 |
+| doctordns | | | 5 | 3 | 5 | 7 | 1 | 21 |
| KirkMunro | | | | 7 | 7 | 1 | | 15 | | alexandair | | 9 | 4 | 2 | | | | 15 | | vexx32 | | | | 3 | 11 | | | 14 |
+| clamb123 | | | | | | | 14 | 14 |
| vors | 1 | 6 | 2 | 1 | | | | 10 | | JustinGrote | | | | 1 | 3 | 6 | | 10 |
install Installing Powershell Core On Windows https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/docs-conceptual/install/Installing-PowerShell-Core-on-Windows.md
--- Title: Installing PowerShell on Windows description: Information about installing PowerShell on Windows Previously updated : 06/24/2021 Last updated : 08/02/2021 --- # Installing PowerShell on Windows
location and version of PowerShell. These values are located in
| 7.1.x Preview | x64 | `HKLM\Software\Microsoft\PowerShellCore\InstalledVersions\39243d76-adaf-42b1-94fb-16ecf83237c8` | This can be used by administrators and developers to find the path to PowerShell. The `<GUID>`
-values will be the same for all preview and minor version releases. The `<GUID>`
+values are the same for all preview and minor version releases. The `<GUID>`
values are changed for each major release. ## <a id="zip" />Installing the ZIP package
Windows 10 IoT Enterprise comes with Windows PowerShell, which we can use to dep
```powershell Set-Location .\PowerShell-<version>-win-<os-arch>
- # Be sure to use the -PowerShellHome parameter otherwise it'll try to create a new
+ # Be sure to use the -PowerShellHome parameter otherwise it tries to create a new
# endpoint with Windows PowerShell 5.1 .\Install-PowerShellRemoting.ps1 -PowerShellHome .
- # You'll get an error message and will be disconnected from the device because
+ # You get an error message and are disconnected from the device because
# it has to restart WinRM ``` 1. Connect to PowerShell 7 endpoint on device ```powershell
- # Be sure to use the -Configuration parameter. If you omit it, you will connect to Windows PowerShell 5.1
+ # Be sure to use the -Configuration parameter. If you omit it, you connect to Windows PowerShell 5.1
Enter-PSSession -ComputerName <deviceIp> -Credential Administrator -Configuration powershell.<version> ```
_OPENSRC_POWERSHELL_ feature to your image.
> [!NOTE] > For ARM64 architecture, Windows PowerShell is not added when you include _IOT_POWERSHELL_. So the
-> zip based install will not work. You will need to use `Import-PSCoreRelease` command to add it in
+> zip based install does not work. You need to use `Import-PSCoreRelease` command to add it in
> the image. ## Deploying on Nano Server
configure applications on Windows 10 computers. This tool is the client interfac
Package Manager service. > [!NOTE]
-> Windows Package Manager and the `winget` tool are in public preview and may be substantially
-> modified before they are generally available. See the [documentation][winget] for a list of system
-> requirements and install instructions.
+> See the [winget documentation][winget] for a list of system requirements and install instructions.
The following commands can be used to install PowerShell using the published `winget` packages:
The following commands can be used to install PowerShell using the published `wi
Name Id Version --------------------------------------------------------------------------- PowerShell Microsoft.PowerShell 7.1.3
- PowerShell Preview (MSIX) Microsoft.PowerShell-Preview-MSIX 7.0.2
PowerShell-Preview Microsoft.PowerShell-Preview 7.2.0-preview.5 ```
The following commands can be used to install PowerShell using the published `wi
winget install --name PowerShell-Preview --exact ```
-## <a id="msix" />Installing from the Microsoft Store
+## Installing from the Microsoft Store
PowerShell 7.1 has been published to the Microsoft Store. You can find the PowerShell release on the [Microsoft Store](https://www.microsoft.com/store/apps/9MZ1SNWT0N5D) website or in the
Benefits of the Microsoft Store package:
Limitations:
-MSIX packages run in an application sandbox that virtualizes access to some filesystem and registry
-locations.
+Windows Store packages run in an application sandbox that virtualizes access to some filesystem and
+registry locations.
- All registry changes under HKEY_CURRENT_USER are copied on write to a private, per-user, per-app location. Therefore, those values are not available to other applications.
locations.
For more information, see [Understanding how packaged desktop apps run on Windows](/windows/msix/desktop/desktop-to-uwp-behind-the-scenes).
-### Using the MSIX package
-
-> [!NOTE]
-> The preview builds of PowerShell include an MSIX package. The MSIX package is not officially
-> supported. The package is built for testing purposes during the preview period.
-
-To manually install the MSIX package on a Windows 10 client, download the MSIX package from our
-GitHub [releases][releases] page. Scroll down to the **Assets** section of the Release you want to
-install. The Assets section may be collapsed, so you may need to click to expand it.
-
-The MSIX file looks like this - `PowerShell-<version>-win-<os-arch>.msix`
-
-To install the package, you must use the `Add-AppxPackage` cmdlet.
-
-```powershell
-Add-AppxPackage PowerShell-<version>-win-<os-arch>.msix
-```
- ## How to create a remoting endpoint PowerShell supports the PowerShell Remoting Protocol (PSRP) over both WSMan and SSH. For more
information in this article. If you installed via the MSI package, that informat
## Installation support
-Microsoft supports the installation methods in this document. There may be other methods of
-installation available from other sources. While those tools and methods may work, Microsoft cannot
-support those methods.
+Microsoft supports the installation methods in this document. There may be other third-party methods
+of installation available from other sources. While those tools and methods may work, Microsoft
+cannot support those methods.
<!-- link references -->
install Installing Powershell Core On Macos https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/docs-conceptual/install/Installing-PowerShell-Core-on-macOS.md
PowerShell 7.0 or higher require macOS 10.13 and higher. All packages are availa
> > The `/usr/local/microsoft/powershell/6` folder is replaced by `/usr/local/microsoft/powershell/7`. >
-> If you need to run and older version of PowerShell core side-by-side with PowerShell 7.1, install
+> If you need to run an older version of PowerShell core side-by-side with PowerShell 7.1, install
> the version you want using the [binary archive](#binary-archives) method. There are several ways to install PowerShell on macOS. Choose one of the following methods:
learn Everything About Hashtable https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/docs-conceptual/learn/deep-dives/everything-about-hashtable.md
used with member access (`.`) notation. Or, you can use array index (`[]`) notat
### $PSBoundParameters
-[$PSBoundParameters][$PSBoundParameters] is an automatic variable that only exists inside the context of a function.
+[$PSBoundParameters][PSBoundParameters] is an automatic variable that only exists inside the context of a function.
It contains all the parameters that the function was called with. This isn't exactly a hashtable but close enough that you can treat it like one.