V 32.10 ide.exe & tcmd.exe only start very randomly

[KevinK]

I'd appreciate some assistance on this please.
(Moved from original 'add-on'.)

V 32.10 ide.exe & tcmd.exe only start very randomly, (sometimes as bad as 1 in 10 attempts)

tcc.exe starts every time.

I have worked with IT , and they have ruled out, by temporarily disabling, all of their security systems and anti-virus.

To aid in testing, I installed V31.01 from the web site.
V32.10 is also freshly installed.

V31.01 does not exhibit the symptoms, V32.10 does.
In theory this locks it to V32.10

Windows 10 Enterprise 22H2
OS Build 19045.4651
Windows Feature Experience Pack 1000.19060.1000.0

 

[rconn]

Look in your Windows event log and see if there's any useful information there.

 

[KevinK]

Here is some of the crash report:
Sig[0].Name=Application Name
Sig[0].Value=ide.exe
Sig[1].Name=Application Version
Sig[1].Value=32.10.21.0
Sig[2].Name=Application Timestamp
Sig[2].Value=661d5d59
Sig[3].Name=Fault Module Name
Sig[3].Value=ntdll.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.19041.4522
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=8a1bb6f3
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00000000000a2847

 

[rconn]

It's crashing in a Windows DLL.

If the crash occurred in the TCMD code (or anything controlled by the TCMD exception handler) it would either self-correct (and you wouldn't see anything) or in the worst case it would generate an exception log file. The exception file would be here:

C:\ProgramData\JP Software\\Take Command 32\\TCMD.exception.log

If you have an exception log file, please send it to [email protected]. If you don't, then the most likely cause (90%+) is a third-party app injecting (faulty) code into TCMD at startup. This is fairly common with AV / anti-malware and screen managers, among others.

You can use the TCMD debug startup option to see if TCMD is even being executed. Start TCMD.EXE like this (from a command prompt):

TCMD.EXE /...

That will pop up message boxes showing the initialization progress. If you don't see anything, then the TCMD code is never even being executed (which points to a Windows or third-party issue). If you do see some messages, let me know how far it gets and that will narrow down the potential issues.