Take Command v33

[Tom Bruce]

The new version installs, but doesn't run.

 

[rconn]

We will need more details. Are you running Take Command or TCC? What version of Windows? Are you running it in a VM? What exactly do you mean by "doesn't run" - do you see anything on the screen? Did you check your AV to see if it was blocking startup?

 

[Tom Bruce]

Of course. I am running the latest version of Windows 11 with all updates installed. I've used Take Command for many years and stay current on upgrades. I purchased the upgrade to v33 today. v32 runs just fine.

I uninstalled, rebooted, and reinstalled v33 with administrator privileges just to make sure that it installed correctly. I've turned off Malwarebytes AV to make sure that it wasn't interfering; and I also added tcmd.exe to the allow list in both Malwarebytes and Windows Firewall.

When I say that it "doesn't run," I mean that when I start the program, there is a slight delay, and then nothing happens at all and there isn't a task in Task Manager such as "tcmd.exe" when v32 is running.

I was hoping that others may have run into this issue.

 

[Tom Bruce]

Of course. I am running the latest version of Windows 11 with all updates installed. I've used Take Command for many years and stay current on upgrades. I purchased the upgrade to v33 today. v32 runs just fine.

I uninstalled, rebooted, and reinstalled v33 with administrator privileges just to make sure that it installed correctly. I've turned off Malwarebytes AV to make sure that it wasn't interfering; and I also added tcmd.exe to the allow list in both Malwarebytes and Windows Firewall.

When I say that it "doesn't run," I mean that when I start the program, there is a slight delay, and then nothing happens at all and there isn't a task in Task Manager such as "tcmd.exe" when v32 is running.

I was hoping that others may have run into this issue.

I solved this, but don't know why it worked. I could run TCC, so I used the option command to apply my registration key. Then Take Command runs.

 

[Joe Caverly]

Same here with v33.

TCMD.EXE does nothing.
internal tasklist t* shows that it is not a running process.

I can run TCC.EXE with no problem.

     _x64: 1
   _admin: 1
_elevated: 1

TCC  33.00.7 x64   Windows 10 [Version 10.0.19045.4894]
BuildNumber  Caption                   CSDVersion  OSArchitecture  Version
19045        Microsoft Windows 10 Pro              64-bit          10.0.19045

22H2

I don't have my registration key yet,
so I cannot test if registering solves the problem.

Joe

 

[vefatica]

I'd expect TCMD to give a trial. Does TCC give the trial message?

 

[Joe Caverly]

C:\...\TCMD33>tcc.exe

TCC  33.00.7 x64   Windows 10 [Version 10.0.19045.4894]
Copyright 2023 JP Software Inc.  All Rights Reserved
Your evaluation period expires in 30 days.
You can buy Take Command, TCC, and CMDebug at https://jpsoft.com

Joe

 

[Torakiki]

Appena installato v33 su Windows 10 x64

tcc.exe funziona perfettamente.
tcmd.exe invece non parte proprio.
Nel registro di Windows trovo:

Nome dell'applicazione che ha generato l'errore: tcmd.exe, versione: 33.0.7.0, timestamp: 0x66e0a66c
Nome del modulo che ha generato l'errore: ntdll.dll, versione: 10.0.19041.4842, timestamp: 0xff17127d
Codice eccezione: 0xc0000409
Errore di offset 0x000000000008cc5f
ID processo che ha generato l'errore: 0x550c
Ora di avvio dell'applicazione che ha generato l'errore: 0x01db0631ac32476d
Percorso dell'applicazione che ha generato l'errore: C:\Program Files\JPSoft\TCMD33\tcmd.exe
Percorso del modulo che ha generato l'errore: C:\Windows\SYSTEM32\ntdll.dll
ID segnalazione: 81e00b60-2479-4c57-8031-65493e88259e
Nome pacchetto completo che ha generato l'errore:
ID applicazione relativa al pacchetto che ha generato l'errore:

 

[Joe Caverly]

Just tried installing TCMD33 into Windows Sandbox.

Same issues.

Joe

 

[Charles G]

Appena installato v33 su Windows 10 x64

tcc.exe funziona perfettamente.
tcmd.exe invece non parte proprio.
Nel registro di Windows trovo:

Nome dell'applicazione che ha generato l'errore: tcmd.exe, versione: 33.0.7.0, timestamp: 0x66e0a66c
Nome del modulo che ha generato l'errore: ntdll.dll, versione: 10.0.19041.4842, timestamp: 0xff17127d
Codice eccezione: 0xc0000409
Errore di offset 0x000000000008cc5f
ID processo che ha generato l'errore: 0x550c
Ora di avvio dell'applicazione che ha generato l'errore: 0x01db0631ac32476d
Percorso dell'applicazione che ha generato l'errore: C:\Program Files\JPSoft\TCMD33\tcmd.exe
Percorso del modulo che ha generato l'errore: C:\Windows\SYSTEM32\ntdll.dll
ID segnalazione: 81e00b60-2479-4c57-8031-65493e88259e
Nome pacchetto completo che ha generato l'errore:
ID applicazione relativa al pacchetto che ha generato l'errore:

Just installed v33 on Windows 10 x64

tcc.exe works perfectly.
tcmd.exe does not start at all.
In the Windows log I find:

Name of the application that generated the error: tcmd.exe, version: 33.0.7.0, timestamp: 0x66e0a66c
Name of the module that generated the error: ntdll.dll, version: 10.0.19041.4842, timestamp: 0xff17127d
Exception code: 0xc0000409
Error offset 0x000000000008cc5f
Faulting process ID: 0x550c
Start time of the application that generated the error: 0x01db0631ac32476d
Path of the application that generated the error: C:\Program Files\JPSoft\TCMD33\tcmd.exe
Path of the module that generated the error: C:\Windows\SYSTEM32\ntdll.dll
Report ID: 81e00b60-2479-4c57-8031-65493e88259e
Faulting full package name:
Faulting application ID:

 

[thorntonpg]

Well I am glad you are having the same problems because nothing here either. It appears briefly in process explorer then exits.

 

[thorntonpg]

That is odd. I just loaded tcc.exe and added the registration key. The windows was truncated so I was working blind but it registered ok. Then I exited tcc and then launched tcmd and it loaded ok.

 

[bmatthew1]

I had the same problems when I upgraded, after installation I opened ide.exe located at C:\Program Files\JPSoft\TCMD33 and entered the registration number there. TCMD works fine now.

 

[rconn]

There is an erratic bug in one of the (undocumented) Windows APIs in the new dark mode code. Try build 33.0.8 (already uploaded to the web site) and let me know if it solves the problem.

 

[hensh]

The latest build corrected the problem on my Windows 11 machine. Thanks.

 

[Joe Caverly]

I can once again do a silent install of Take Command into Windows Sandbox,
with Build 33.0.8.0

Thanks!

Joe

 

[Phileosophos]

FWIW, I had the same problem. The new 33.0.8.0 build fixed the issue for me.

 

[Robert Torzynski]

I upgraded yesterday build 33.0.12. TCC seems to run fine. But TCMD, when I try to run it just transitions into TCC. I suspect this has to do with Windows 11, which insists on running the Antimalware executable, using 250 mb of memory, which can't be disabled. Reading the comments and solutions on this page, I might as well give up. Maybe a future build will solve the issue, but I guess it's a lost cause. Been using this product for many years, wanted to come back. Ah well.

 

[rconn]

I upgraded yesterday build 33.0.12. TCC seems to run fine. But TCMD, when I try to run it just transitions into TCC. I suspect this has to do with Windows 11, which insists on running the Antimalware executable, using 250 mb of memory, which can't be disabled. Reading the comments and solutions on this page, I might as well give up. Maybe a future build will solve the issue, but I guess it's a lost cause. Been using this product for many years, wanted to come back. Ah well.

I am not aware of any issues with the existing build 33.0.12 (running it here on Win 11 without issue).

What exactly do you mean by "it just transitions into TCC"? If TCMD crashes (usually due to faulty third-party code injection), and a TCC tab window was active, v33 will "unhide" that tab window when it discovers it has been orphaned. If you're seeing a TCMD crash, please post the crash info from the event viewer either here or send it to [email protected].