Fixed 20.10 strangeness with external commands

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
May 26, 2008
Since installing version 20.10, I get strange results with external commands in both TCC and PowerShell, but only when they are attached to TCMD.

In TCC, when I run an external command, the next command prompt is displayed before the output from said external command.

In PowerShell, it actually displays an error about the external command failing to run and a handle being invalid, but the output is still shown. Like TCC, the next command prompt is displayed too early. A bit hard to describe. See attached screen shots.

Did not see this effect before installing 20.10.32.





Staff member
May 14, 2008
Not reproducible here, and it's hard to see how TCMD could be involved unless you got a chip from Intel that disabled all of the hardware protection.

The only thing that TCMD could do (peripherally) to affect a console app is if you have ANSI support enabled (configure TakeCommand / Tabs / ANSI colors). In that case it injects a dll into the console app to allow ANSI escape sequences. (This has not changed in 20.10.) If you have that option enabled, try turning it off and see if that affects the output.
May 26, 2008
Not anything that I'm aware of.

It happens on both my work and home systems.

Work: Windows 10 Enterprise x64 14393.321
Home: Windows 10 Pro x64 14986.1001