I would suggest the Open Forum. But as long as it's even vaguely Take Command-related, nobody's going to get huffy with you for posting here.

Maybe an obvious question, but if you type BREAK at the command line, does it say that break handling is on or off?

Oh, I see. I believe you can change that setting through Windows Terminal:

Why do you think that? I have Windows Terminal installed on both my home and work machines, but mostly run TCC in Take Command, or occasionally in a plain old console window.

Actually, I think the stuff Jay is asking about lives in the registry, not the .INI file. Maybe under HKCU\SOFTWARE\JP SOFTWARE\Take Command xx.yy — note that these keys do include the major and minor version numbers. I have not tested this myself! — but it might be possible to export the old...

To answer the question at the end of your post, PLUGIN /I will list all currently loaded plugins. The lines beginning with "Name:" give the internal name for each plugin.

If I detach a tab window via the WINDOW DETACH command, I cannot re-attach it to Take Command: it doesn't show up in the "Attach Tabs" dialog. Tabs detached through the GUI — by right-clicking, going through the Tabs menu, etc. — don't have this issue. Not a serious issue, but I'm curious...

To unload a plugin, use PLUGIN /U with the plugin's internal name, not its filename. So: plugin /u 4utils

Are you asking me why Vincent doesn't use PATH /N? Force of habit, maybe. Or to save vertical space in his posts.

CreateToolhelp32Snapshot() ?

Just to clarify: Are you saying that you have changed COMSPEC to point to TCC? Or are you merely observing that when you are running TCC, COMSPEC points to TCC? And that WinMerge inherits the troublesome value from TCC?

Well, the Start/Run dialog checks it, anyway.

I do see the console window briefly. It doesn't bother me, but your mileage may vary.

You can also start /unelevated /tab

I have a plugin that does this — though I no longer remember why — and I can confirm that START /UNELEVATED causes OpenProcessToken(GetCurrentProcess(),...) to fail. Does this constitute an actual problem? I really don't know.