For years I have set COMSPEC to CMD.exe in 4start.bat, because there are many sub-processes in our environment that are incompatible with TCC when they spawn.
After upgrading from v20 to v28 there is a new problem. Sometimes COMSPEC gets reset to TCC and those subprocesses fail.
This was mentioned in this thread, but never resolved: COMSPEC constantly reset to TCC.EXE
In the v22 release notes: "TCC will reset COMSPEC to TCC.EXE after a WM_SETTINGCHANGE", which seems to be the crux...
Read more
After upgrading from v20 to v28 there is a new problem. Sometimes COMSPEC gets reset to TCC and those subprocesses fail.
This was mentioned in this thread, but never resolved: COMSPEC constantly reset to TCC.EXE
In the v22 release notes: "TCC will reset COMSPEC to TCC.EXE after a WM_SETTINGCHANGE", which seems to be the crux...
Read more