Encoding Parameter Error in Get-Content

[us254]

Describe the Bug

Describe the Bug:
When using the Get-Content cmdlet in PowerShell and specifying the -Encoding parameter as 'Byte', it results in the following error:

Get-Content: Cannot process argument transformation on parameter 'Encoding'. 'Byte' is not a supported encoding name.

The main problems I see:

1. Passing 'Byte' as the encoding to Get-Content, which is not a valid encoding name.
2. Get-Content is having an issue processing the encoding argument provided.

To fix it:

1. Remove the -Encoding parameter if it's not needed.

2. Use a valid encoding name like ASCII, UTF8, Unicode, etc. For example:

   Get-Content -Path file.txt -Encoding UTF8
   
   

How can this issue be reproduced?

Prepare the Environment:

Ensure you have a Windows 11 operating system or a version after 1809 (Windows 10 or later).

Create or Identify a PowerShell Script:

Find or create a PowerShell script or code snippet that contains the following line with an invalid encoding parameter:
Get-Content -Path file.txt -Encoding Byte

Replace file.txt with the actual path to a text file if needed.

Run the PowerShell Script:

Execute the PowerShell script that contains the problematic line.

Observe the Error:

Expected behavior?

When running the PowerShell script with the Get-Content cmdlet and specifying the -Encoding Byte parameter, I expected the script to read the content of the specified file (file.txt) using the specified encoding without any errors. Specifically, I expected PowerShell to recognize the Byte encoding and read the file's content as intended.

Operating System

Windows 11

Operating System Version

10.0.22621 N/A Build 22621

Screenshots

No response

Logs

No response

Additional Info

No response

[LeDragoX]

I'm still trying to understand where did this issue happened, because there's only a single file which is using Get-Content function, and isn't even with the -Encoding parameter, but just to be sure, I'll use it in this file:

Win-Debloat-Tools/src/scripts/other-scripts/Git-GnupgSshKeysSetup.ps1

Line 184 in a7c2dfe

Get-Content "$GnuPGPath/$($GnuPGFileName)_public.gpg"