TCMD 36.00.34 UI not starting on Win 11 ARM

[TimButterfield]

I have two Windows 11 Pro VMs running under Parallels on my MacBook Pro. In one VM, ver 36 starts and runs TCMD as expected. In the second VM, it does not. All Windows updates are current in both VMs.

In the second VM, TCMD installed without any issues. TCC starts as expected. It is only the installed TCMD.exe that does not start. Whether selecting it from the start menu, double-clicking the desktop icon, double-clicking TCMD.exe in Windows Explorer or even using the START command from v36 TCC, it always processes for a few seconds and stops without ever displaying a UI. I have not found any crash files in neither the install folder, the temp folder, nor in AppData\Local\JPSoft. Is there another location I should check?

Here is some output from TCC:

C:\JPSoft\TCMD36>timer on & start /WAIT tcmd.exe & timer off
Timer 1 on: 18:15:26
Timer 1 off: 18:15:28  Elapsed: 0:00:02.444

C:\JPSoft\TCMD36>ver

TCC  36.00.34 x64   Windows 11 [Version 10.0.26200.8246]

 

[rconn]

You could look in the Windows Event Log. If it's crashing in Windows code or injected code, TCMD won't get the exception and so won't write the error log file.

You can also try starting TCMD with the "/..." option, which will print debug messages showing where in the startup process it is.

Unfortunately, that is not an environment that I can replicate or test in.

 

[TimButterfield]

I'm willing to test whatever is needed especially as VM snapshots allow for rollbacks.

I ran this command: start /wait %@truename[TCMD.exe] /N /NT /...

Here is the Event Viewer log entry:

Log Name:      Application
Source:        Application Error
Date:          4/22/2026 7:49:52 PM
Event ID:      1000
Task Category: Application Crashing Events
Level:         Error
Keywords:     
User:          VM-WIN11\timothybutterfield
Computer:      VM-WIN11
Description:
Faulting application name: TCMD.exe, version: 36.0.34.0, time stamp: 0x69e8d2c3
Faulting module name: MSVCP140.dll, version: 14.30.30704.0, time stamp: 0x615a931a
Exception code: 0xc000041d
Fault offset: 0x0000000000074674
Faulting process id: 0x1094
Faulting application start time: 0x1DCD2B2974B95E6
Faulting application path: C:\JPSoft\TCMD36\TCMD.exe
Faulting module path: C:\WINDOWS\SYSTEM32\MSVCP140.dll
Report Id: 5bb977a6-f156-4f21-8c4a-4ac2f09f1ed4
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
    <EventID>1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2026-04-22T23:49:52.8467250Z" />
    <EventRecordID>3688</EventRecordID>
    <Correlation />
    <Execution ProcessID="8788" ThreadID="9676" />
    <Channel>Application</Channel>
    <Computer>VM-WIN11</Computer>
    <Security UserID="S-1-5-21-817108822-369499775-2773655269-1000" />
  </System>
  <EventData>
    <Data Name="AppName">TCMD.exe</Data>
    <Data Name="AppVersion">36.0.34.0</Data>
    <Data Name="AppTimeStamp">69e8d2c3</Data>
    <Data Name="ModuleName">MSVCP140.dll</Data>
    <Data Name="ModuleVersion">14.30.30704.0</Data>
    <Data Name="ModuleTimeStamp">615a931a</Data>
    <Data Name="ExceptionCode">c000041d</Data>
    <Data Name="FaultingOffset">0000000000074674</Data>
    <Data Name="ProcessId">0x1094</Data>
    <Data Name="ProcessCreationTime">0x1dcd2b2974b95e6</Data>
    <Data Name="AppPath">C:\JPSoft\TCMD36\TCMD.exe</Data>
    <Data Name="ModulePath">C:\WINDOWS\SYSTEM32\MSVCP140.dll</Data>
    <Data Name="IntegratorReportId">5bb977a6-f156-4f21-8c4a-4ac2f09f1ed4</Data>
    <Data Name="PackageFullName">
    </Data>
    <Data Name="PackageRelativeAppId">
    </Data>
  </EventData>
</Event>

The last debug message dialog was this one:

If there were a debug build, I could put that TCMD.exe in the folder and provide additional logging to help determine what is happening. It would also be nice if something like the /... could output to STDOUT/STDERR.

 

[rconn]

MSVCP140.dll is not used by TCMD.EXE (or any of its dll's).

The TCMD debug message indicate that your crash is in the Afx RTL code, so a debug build may not be of much use.

I just had one other user report a similar error, which he said went away when he installed in the default directory. And then it also worked in the non-default directory. Which didn't make much sense.

If there were a debug build, I could put that TCMD.exe in the folder and provide additional logging to help determine what is happening. It would also be nice if something like the /... could output to STDOUT/STDERR.

TCMD doesn't have a STDOUT or STDERR.