\uD83E\uDD14 Problem
Terminal Many terminal apps adopt utilize the Windows-native Console Host (conhost.exe) executable for implementation.
Under Windows 10, the conhost.exe exhibits a bug that limits ACLI Shell functionality.
In this environment, conhost.exe incorrectly interprets a critical VT100 control sequence as a VT52 sequence, which breaks the ACLI Shell interactive renderer. As a result, terminal apps that rely on conhost.exe executable under Windows 10 fail to function as designed.
The issue is rectified in the conhost.exe implementation shipped with Windows 11 as well as when running apps in Windows Terminal and other VT100-compliant terminal emulators (e.g., ConEmu, CMDER, Alacritty, and WezTerm) in capable of running on Windows 10.
\uD83C\uDF31 Solution
...
Windows terminal compatibility
Windows Version | Terminal App | ACLI Version | DescriptionSolution |
|---|---|---|---|
Windows 10 | In ACLI 10.6, set the WT_SESSION variable | Setting WT_session variable enables non-Windows terminal emulators on Windows 10 for ACLI v10.6 and earlier. | |
Windows 10 | ACLI v11 | The WT_SESSION variable is not required, when using one of these terminals:
| |
Windows 11 | ACLI v11 | No constraints on the choice of terminal, including the legacy Windows console (conhost.exe). |
ACLI v10.6 and earlier
How to fix the conhost.exe interpreting of VT100 control sequence
...
Console Host ( | 10.6.0 and earlier | Do not use! | |
Windows 10 | Windows Terminal | 10.6.0 and earlier | No special setup required |
Windows 10 | Any other VT100-compliant terminal (WezTerm, Alacritty, ConEmu, CMDER, etc) | 10.6.0 and earlier | Manually set |
Windows 10 | Windows Terminal, WezTerm, Alacritty, ConEmu, CMDER | 11.0.0 and later | No special setup required |
Windows 10 | Any VT100-compliant terminal not listed above | 11.0.0 and later | Manually set |
Windows 11 | Any terminal | 11.0.0 and later | No special setup required |
Applying the WT_SESSION workaround when indicated by the above table:
Open the environment variables settings on your system.
Create a new environment variable named
WT_SESSIONand set its value to any non-empty string (e.g.,1).Save the changes, and restart your terminal application.
Launch the ACLI shell.
...
To ensure the best experience with the ACLI shell, it is recommended to use a fully VT100-compliant terminal emulator or upgrade to Windows 11 or to use Microsoft’s Windows Terminal.
ACLI 11.0.0
How to fix the conhost.exe interpreting of VT100 control sequence
...
Other terminal applications
The supported terminal emulators on Windows 10 are:
...
Depending on your requirements and specific cases, additional environment variables for Shell configuration are available and described in the Environment Variables Table.
Environment variable | Description |
|---|---|
| Value is one of The shell automatically sets the glyph set to |
| Value is one of the themes available in the shell (or a custom theme). NOTE
|
| It allows you to specify where to store the shell cache files. |
| It allows you to specify where to store the shell config files. |
| This variable is useful, if you do not have full unicode support in the terminal:
|
| Set the value to Set the value to |
| It sends the debug to a log rather than a terminal. This environment variable is recommended if you use the debug variable The value for this variable is the path to the log file where the debug and trace information is to be sent: an empty string value uses the default path |
\uD83D\uDCCE Related articles
...