\uD83E\uDD14 Problem
Terminal apps adopt 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 tis environment, conhost.exe incorrectly interprets a critical VT100 control sequence as a VT52 sequence, which breaks the ACLI Shell’s 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 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 Windows 10.
\uD83C\uDF31 Solution
ACLI 11.0.0 and later
Please use one of the following terminal emulators on Windows 10 when using the ACLI Shell:
...
If you know of another VT100-compliant terminal on Windows 10, you can test it using the instructions given below for ACLI 10.6.0 and earlier. If the shell works, please contact us so that we can add official support for that terminal.
ACLI 10.6.0 and earlier
To remedy the issue with Windows 10, the workaround to apply is as follows:
...
| Info |
|---|
We have made changes to the v11 that supports extra terminals (namely: WezTerm, Alacritty, ConEmu, and Cmder) without the need for additional configuration (i.e., |
\uD83D\uDCCE Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|