Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

TCMD.exe ver 36.0.29 and Windows 11 Pro 23H2 build 22631.6199

G

georgearoush

Aug
39
0
About 1 hour ago, I just bought TC ver 36.0.29 (I was on TC 22 running on Windows 10).

I cannot start TCMD on my Windows 11 Pro 23H2 build 22631.6199. How do I go about debugging this issue?

TCC, Everything64, Everything64, eViewer, FSearch, etc. all start.
 
Does TCMD do anything at all? Do you see any window(s)? Does an icon appear on the taskbar?

Try starting TCMD with the /N option (which tells it not to load TCMD.INI).

You can start TCMD in debugging mode like this:

Code: 
tcmd.exe /...

That will display a series of messageboxes detailing the start process.

You should also check that you don't have something either blocking TCMD from starting (like an AntiVirus app), or an app that is injecting (bad) code into TCMD and crashing it at startup. (If it's crashing you should see something in the Windows Event Log.)
 
I don't have AnitVirus app, if another app injecting code into TCMD, how would I find that out and wouldn't that be the case for the other TC programs?

Here is the output of running "tcmd.exe /..." (I might have type some place but that's the complete list (why isn't there a way to log this into a log file?)):
TCMD: GetCommandLine()=tcmd.exe /...
TCMD: RegisterApplicationRestart & jump list
TCMD: OLE & COM initialization
TCMD: InitializeTCExplorer
TCMD: Checking for custom TCDM.ini
TCMD: Inializing macro recorder
TCMD: Parsing startup command line
TCMD: Create main MDI Frame window

Here is what I see in Event Viewer each time when I start TCMD:
Error #1:
And here is the error in Event Viewer:
Faulting application name: TCMD.exe, version: 36.0.29.0, time stamp: 0x69e17c0e
Faulting module name: MSVCP140.dll, version: 14.36.32532.0, time stamp: 0x04a30cf0
Exception code: 0xc0000005

Error #2:
Faulting application name: TCMD.exe, version: 36.0.29.0, time stamp: 0x69e17c0e
Faulting module name: MSVCP140.dll, version: 14.36.32532.0, time stamp: 0x04a30cf0
Exception code: 0xc000041d
 
Btw, this is a newly created Windows 11 VM. So far, I only have basic apps installed, such as 7-Zip, Notepad++, to name some.
 
Hello, any update on this issue? What data can I share to help debug it?

As a side note, I have no issue running TCMD 22 on this same VM.
 
Yes, I did starting TCMD with /N. It didn't make any difference. I see the same error in the Event Viewer. I would be happy if you want to provide me with a debug build to run on this VM to sort out this issue.
 
I need more information.
  • What language are you using? (I need to know what resource dll's are in use.)
  • When you say you don't have an AV app, do you mean you're also not running Windows Defender (which is an AV app, and which injects code into TCMD)?
  • What type of VM is this (i.e., Hyper-V or a third-party VM)?
  • Are you running any type of screen manager?
  • How are you starting TCMD - from the desktop icon or from the command line? Or some other way?
I am 99% certain that something is injecting code, because of the reference to MSVCP140.dll, which nothing in TCMD uses.
 
This is very interesting! I prepared answers to your question and about to click on "Post reply" but I decided to try something out.

I installed TC under D:\APPS\TCMD36. Just now, I made a copy of everything from D:\APPS\TCMD36 to C:\TCMD36 (notice the driver letter change and the path) and than double clicked on "tcmd.exe" -- it works! I went back to D:\APPS\TCMD36 and double clicked on "tcmd.exe" and that too now works. I cannot explain this, but a while back, I had a similar issue with another application, it would not run off D:\APPS\<app-name> and I had to always run it off C:\<app-name>. In TC case, I am glad I can now run it off D:\APPS\
 
You must log in or register to reply here.
Back
Top