I notice that ASSOC returned a filetype of TCMD.Batch, but the filetype you are using in the second command is tcc.batch.

I'm amazed that that's legal!

I am trying to reproduce this behavior: C:\Test>which 7z 7z is an external : C:\Bin\Util\7z.exe C:\Test>type test1.btm @echo off setlocal set USE_7Z=1 set TO_UNZIP=c:\test\test.7z call test2.btm Foo Bar Fum if %USE_7Z eq 1 ( 7z x -aoa "%TO_UNZIP" ) call test2.btm Foo Bar Fum endlocal...

How are you calling 7z.exe? Are you using the full pathname, or a path search? Or maybe an alias?

Is it only batch files, or is there maybe an alias in there somewhere?

No, I've never tried those. They might be an idea for v2.0. Or then again maybe not, because.... Yes, and I make it available via a variable. Once in Windows Terminal, always in Windows Terminal, but: the handle can change. Tabs can be split off to a new window, or moved from one WT...

Brute force. I scan for new TCC popups and dialogs eight times a second with EnumThreadWindows(). When a new one appears, force it to the front (dialogs sometimes appear under Take Command) and give it focus. If it's offscreen (Console2 does this sometimes), move it where it's visible. When...

Not just OPTION. This appears to be true of any dialog opened by TCC in Windows Terminal: the Open dialog, the Save As dialog, @COLOR[], @GETDATE[] and @GETDATETIME[], probably many others. I believe Rex is automatically re-focusing the console window (or the Take Command window) whenever a...

If you're feeling terse, you can omit the CDD and the second percent sign.

Hunh, so it doesn't. So much for my little theory.

SWAG: The filename completion sees a filename beginning with a dot, and assumes it has a relative pathname?

But only the one under HKEY_LOCAL_MACHINE, not the one under HKEY_CURRENT_USER.

And in answer to the question you did ask: After variable expansion, your command becomes either ECHO OFF or ECHO ON. These two words are handled specially by the ECHO command; see HELP ECHO for details. To work around this ancient misfeature, use a period instead of a space to separate the...

Not an answer to the question which you asked, but... Have you tried %@option[direnv]? P.S. Note that %@option[direnv] returns "Yes" or "No", not "On" or "Off".

FWIW, the exact same thing happens if you disable a command with COMMANDS /D WINDOW, then open the OPTION dialog and click OK. This is nothing to do with SETDOS in particular.