Select-String as pipeline | corrupted output

[Ricky-Tigg]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.
• Refer to the FAQ.
• Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

1. 'tpmtool /?'or 'TPMTOOL /?'; output truncated:

> tpmtool /? 
Parameters:
 GETDEVICEINFORMATION                     Displays the basic information of the TPM. 
Examples:
 tpmtool getdeviceinformation

2. 'tpmtool /? | Select-String -AllMatches -Pattern 'getdevice' '

Expected behavior

> tpmtool /? | Select-String -AllMatches -Pattern 'getdevice' 
 GETDEVICEINFORMATION                     Displays the basic information of the TPM. 
 tpmtool getdeviceinformation

Non-corrupted original text structure.

### Actual behavior

```console
> tpmtool /? | Select-String -AllMatches -Pattern 'getdevice'
    ←[7mGETDEVICE←[0mINFORMATION                     Displays the basic information of the TPM.
    tpmtool ←[7mgetdevice←[0minformation

Corrupted original text structure.

### Error details

_No response_

### Environment data

```powershell
> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      7.3.6
PSEdition                      Core
GitCommitId                    7.3.6
OS                             Microsoft Windows 10.0.22000
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visuals

No response

[237dmitry]

In my environment (win 11 22H2):

[mklement0]

This is a known bug, and it affects:

• Select-String pipelines with input from native programs (simple repro: cmd /c ver | Select-String ver) whose output prints straight to the display,
• but only on Windows, and there only in regular (conhost.exe) console windows.

See:

• Selective disabling/re-enabling of VT support (ANSI escape sequences) is broken #19425

[Ricky-Tigg]

> Get-ComputerInfo | Select WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer
WindowsProductName WindowsVersion OsHardwareAbstractionLayer                                                            ------------------ -------------- --------------------------                                                            Windows 10 Home    2009           10.0.22000.1696             
------------------ -------------- --------------------------
Windows 10 Home    2009           10.0.22000.1696
> Get-Culture
LCID             Name             DisplayName
----             ----             -----------
1035             fi-FI            Finnish (Finland)
> tpmtool /? | Select-String -AllMatches -Raw -Pattern 'getdevice'
    GETDEVICEINFORMATION                     Displays the basic information of the TPM.
    tpmtool getdeviceinformation

[237dmitry]

and there only in regular (conhost.exe) console windows.

I do not remember when but it was. Maybe up to 7.3.6?

[mklement0]

@237dmitry, that only works with an opt-in (having manually set the VirtualTerminalLevel value in registry key HKEY_CURRENT_USER\Console to 1 in a previous session) - which shouldn't be necessary and indeed wasn't necessary up to v7.2.x; I've updated the linked issue to make that clearer.

[237dmitry]

that only works with an opt-in (having manually set the VirtualTerminalLevel value in registry key HKEY_CURRENT_USER\Console to 1

Yes exactly. Now I remembered. This registry value I actually set.

[Ricky-Tigg]

Another issue, out of scope though; the non-reliability of Get-ComputerInfo that reports Windows 10 Home as OS while installed is Windows 11 Home, upgraded from Windows 10 Home.

[mklement0]

@Ricky-Tigg:

• If you found another issue, I encourage you to create a new bug report.

• As for the issue at hand:

  • If you agree that your issue is a variation of Selective disabling/re-enabling of VT support (ANSI escape sequences) is broken #19425, I encourage you to close this issue.
  • If not, please elaborate on what additional symptoms you've found / problems you suspect.