TCC no longer runs after installing TC 17

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
Apr 30, 2009
17
0
#1
I just installed Take Command 17.00.53 x64 and now TCC no longer runs. Before installing TC 17 I had a copy of TC 16 installed and it ran perfectly. After the TC 17 installation TCC just won't run in either version.

I've uninstalled both versions and reinstalled just TC 17. No luck.
I tried installing just the 32-bit version of TC 17. No luck.

When I try to open TCC directly from the installation directory I see a brief flash of a command window and then it vanishes.

The OS is Windows 8.1 x 64 and is fully patched.

Edit: I completely uninstalled TC, deleted the AppData folders for all versions of TC and rebooted.

Now, with no additional tabs defined, TC opens briefly and then closes.

Any ideas?
 
Last edited:
Apr 30, 2009
17
0
#3
When running tcc.exe from a Windows command prompt I get nothing. I've been poking at this since I posted the original message and, while using the Sysinternals Process Monitor utility I can see buffer overflow errors and then a call to \Windows\system32\WerFault.exe.

I've attached the output from Process Monitor as a zipped CSV file. Please let me know if you need further information. I use TCMD every day and with it not working things take much longer than normal to accomplish.
 

Attachments

Apr 30, 2009
17
0
#5
No. One of the steps I took in trying to diagnose the problem was to delete all the JP Software directories under %APPDATA%
 

rconn

Administrator
Staff member
May 14, 2008
10,164
86
#7
If TCC is crashing, it will create a .GPF file (usually in the same directory as TCMD.INI or TCSTART -- that will vary depending on the version of Windows you're running). If you don't get a GPF file, then the crash is likely in a plugin or possibly a third-party app that's injecting something into TCC (like a screen manager or an antivirus app).
 
Apr 30, 2009
17
0
#8
I'll try that and look for the .GPF file tomorrow. I'm away from the computer for the rest of the day (Eastern Time).
 
Apr 30, 2009
17
0
#10
I have a zero byte TCMD.INI in %APPDATA%\Local\JPSoft and nothing else. I'm have no plugins installed. TCC /I results in no change in behavior and I have no GPT file anywhere that I can find. I'm going to try a minimal startup and see if that helps.
 
Last edited:
Apr 30, 2009
17
0
#11
After using msconfig to perform a "diagnostic startup" with just the basic Windows devices and services running TCMD x64 starts but generates an error: Access is denied. "AttachConsole". I tried deleting TCMD.INI and that stopped the error message from displaying but TCMD x64 and TCC still open briefly and then vanish.

This is an error I've reported before and the advice has always been to run the 32-bit version of TCMD. I installed the 32-bit TCMD and it works.

After a reboot with all normal startup applications and services running the 32-bit TCMD is still working and the 64-bit version still crashes on startup with no GPT file generated.

The problem seems to lie in the difference between the 64-bit TCC and the 32-bit version.
 
Last edited:
#12
I have a zero byte TCMD.INI in %APPDATA%\Local\JPSoft and nothing else. I'm have no plugins installed. TCC /I results in no change in behavior and I have no GPT file anywhere that I can find. I'm going to try a minimal startup and see if that helps.
It's actually a GPF - not a GPT file....
 

rconn

Administrator
Staff member
May 14, 2008
10,164
86
#13
Since you don't have a GPF file, and since it's only crashing in x64, it's highly likely that the cause is a third-party app injecting (buggy) code into TCC's address space. What does Process Monitor show for the dll's loaded in TCC's session?

If you're willing to test further, I can send you a debug TCC that will display its load progress (though if it is indeed a third-party app causing the problem there won't be much I can do about it).
 
Apr 30, 2009
17
0
#14
I'm willing to test. This is an issue that has hit me, at irregular intervals, for years. Case in point: TC 16 x64 worked for a year without issue. After installing TC 17 x64 both TC 16 and 17 stop running. No other system changes were made at the time.

I'll run a Process Monitor session with a minimal system start when I get to work.
 
C

cbeckstein

Guest
#15
Any progress with this?

I have the exact same problem as Magus with TCMD V17 - on 3 different machines all of them running WIndows 8.1 Pro 64bit
 

rconn

Administrator
Staff member
May 14, 2008
10,164
86
#16
For those people with problems starting Take Command (not TCC) v17, you can download a test build at:

https://jpsoft.com/downloads/beta/tcmd.exe (32-bit)
https://jpsoft.com/downloads/beta/tcmdx64.exe (64-bit)

These builds pop up some message boxes at startup; please let me know the text in the message boxes you see & how far it gets. (If you don't see any, then the problem is with the Windows loader or a third-party injected dll.)
 

rconn

Administrator
Staff member
May 14, 2008
10,164
86
#17
For those people with problems starting TCC (not Take Command) v17, you can download a test build at:

https://jpsoft.com/downloads/beta/tcc.exe (32-bit)
https://jpsoft.com/downloads/beta/tccx64.exe (64-bit)

These builds pop up some message boxes at startup; please let me know the text in the message boxes you see & how far it gets. (If you don't see any, then the problem is with the Windows loader or a third-party injected dll.)
 
C

cbeckstein

Guest
#18
For those people with problems starting Take Command (not TCC) v17, you can download a test build at:

https://jpsoft.com/downloads/beta/tcmd.exe (32-bit)
https://jpsoft.com/downloads/beta/tcmdx64.exe (64-bit)

These builds pop up some message boxes at startup; please let me know the text in the message boxes you see & how far it gets. (If you don't see any, then the problem is with the Windows loader or a third-party injected dll.)
just reinstalled the 64bit Version cited above along with my V17 license:

the following happens:

succsessive popups CTExplore 0-3
then popups for Initinstance 0-11
TCMD window opens
then popups for Initinstance 12-14
then Windows error popup: TCC no longer working (i click close program)
click on the last Initinstance 14 popup closes TCMD window
 
C

cbeckstein

Guest
#19
For those people with problems starting TCC (not Take Command) v17, you can download a test build at:

https://jpsoft.com/downloads/beta/tcc.exe (32-bit)
https://jpsoft.com/downloads/beta/tccx64.exe (64-bit)

These builds pop up some message boxes at startup; please let me know the text in the message boxes you see & how far it gets. (If you don't see any, then the problem is with the Windows loader or a third-party injected dll.)
now the same with the test TCC 64 bit version (with above 64bit test version of TCMD installed before):

if i double click on the TCC64.exe cited above it tells me that TCC cannot be started because Takecmd.DLL would be missing oin this computer

If i start the tcc.exe in c:\Program files}jpsoft\tcmd64 from within a cmd shell, the same windows error popup like for TCMD64 before closing its windows shows up: "TCC nl longer working" and closing this popup terminates tcc.exe as well

as written before: Windows 8.1 Pro 64 bit, German edition, all security updates installed
 

rconn

Administrator
Staff member
May 14, 2008
10,164
86
#20
now the same with the test TCC 64 bit version (with above 64bit test version of TCMD installed before):

if i double click on the TCC64.exe cited above it tells me that TCC cannot be started because Takecmd.DLL would be missing oin this computer

If i start the tcc.exe in c:\Program files}jpsoft\tcmd64 from within a cmd shell, the same windows error popup like for TCMD64 before closing its windows shows up: "TCC nl longer working" and closing this popup terminates tcc.exe as well
Is takecmd.dll actually missing? What are the files in your TCMD installation directory?

(TCMD.EXE also uses takecmd.dll, so if it were really missing then nothing should be working.)
 
C

cbeckstein

Guest
#21
Is takecmd.dll actually missing? What are the files in your TCMD installation directory?

(TCMD.EXE also uses takecmd.dll, so if it were really missing then nothing should be working.)
no it is not missing...
sits right there in C:\Program Files\JPSoft\TCMD17x64
with a date of 2 days ago (resulting from installing the test tcmd64.exe you linked in the post above)

this is the contents of the install directory:

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle Rechte vorbehalten.
Clink v0.4.3 [git:258fc3] Copyright (c) 2014 Martin Ridgers
http://mridgers.github.io/clink


C:\WINDOWS\system32>c:

C:\WINDOWS\system32>cd C:\Program Files\JPSoft\TCMD17x64

C:\Program Files\JPSoft\TCMD17x64>dir
Datenträger in Laufwerk C: ist System
Volumeseriennummer: 7CF8-67BE

Verzeichnis von C:\Program Files\JPSoft\TCMD17x64

04.02.2015 11:13 <DIR> .
04.02.2015 11:13 <DIR> ..
22.02.2006 22:40 34.304 BorlndMM.dll
02.02.2015 15:24 1.734.216 English.dll
02.02.2015 15:24 688.200 EnglishD.dll
02.02.2015 15:24 75.336 Everything64.dll
02.02.2015 15:24 1.761.352 French.dll
02.02.2015 15:24 693.832 FrenchD.dll
02.02.2015 15:24 1.751.112 German.dll
02.02.2015 15:24 693.832 GermanD.dll
02.02.2015 05:20 5.494.344 ide.exe
26.05.2014 09:58 2.100.736 ipworks9.dll
26.05.2014 12:30 1.013.760 ipworksssh9.dll
26.05.2014 11:30 2.228.736 ipworksssl9.dll
26.05.2014 13:16 338.944 ipworksssnmp9.dll
26.05.2014 12:56 1.243.648 ipworkszip9.dll
05.10.2014 15:16 1.212.224 IsLicense50.dll
02.02.2015 15:24 1.749.064 Italian.dll
02.02.2015 15:24 689.736 ItalianD.dll
06.11.2014 18:45 8.589 license.txt
02.02.2015 15:24 485.376 Lua52.dll
02.02.2015 15:24 487.496 onig.dll
06.11.2014 18:44 7.384 readme.txt
04.02.2015 11:13 1.452 regid.2002-09.com.jpsoft_Take Command x64 17.0.swidtag
02.02.2015 15:24 1.798.216 Russian.dll
02.02.2015 15:24 691.272 RussianD.dll
05.11.2014 16:15 1.051.720 SciLexer.dll
02.02.2015 05:17 90.184 ShrAlias.exe
02.02.2015 15:24 1.758.280 Spanish.dll
02.02.2015 15:24 695.368 SpanishD.dll
24.01.2000 12:01 453.632 stdvcl40.dll
04.02.2015 11:13 <DIR> Styles
02.02.2015 15:24 2.390.088 takecmd.dll
02.02.2015 05:57 214.600 tcc.exe
09.01.2013 19:13 1.002 tccbatch.btm
03.04.2013 15:12 1.170 tcchere.btm
09.01.2013 19:13 1.272 tcctabhere.btm
01.02.2015 05:23 4.123.420 tcmd.chm
02.02.2015 15:21 5.986.376 tcmd.exe
09.01.2013 19:09 1.113 tcmdbatch.btm
03.04.2013 15:17 1.204 tcmdhere.btm
22.08.2013 17:01 9.004.648 textpipeengine.dll
02.02.2015 05:22 128.072 TPipe.exe
02.02.2015 15:25 593.992 updater.exe
04.02.2015 11:13 410 updater.ini
20.09.2014 01:46 496.493 v.chm
05.10.2014 04:00 2.890.312 v.exe
20.09.2014 01:46 824.392 VESP.dll
20.09.2014 01:46 820.808 VFRA.dll
20.09.2014 01:46 817.224 VITA.dll
20.09.2014 01:46 802.376 VRUS.dll
02.02.2015 15:24 302.664 WiFiMan.dll
49 Datei(en), 60.433.981 Bytes
3 Verzeichnis(se), 26.808.864.768 Bytes frei

C:\Program Files\JPSoft\TCMD17x64>
 

rconn

Administrator
Staff member
May 14, 2008
10,164
86
#22
When running tcc.exe from a Windows command prompt I get nothing. I've been poking at this since I posted the original message and, while using the Sysinternals Process Monitor utility I can see buffer overflow errors and then a call to \Windows\system32\WerFault.exe.

I've attached the output from Process Monitor as a zipped CSV file. Please let me know if you need further information. I use TCMD every day and with it not working things take much longer than normal to accomplish.
You have at least two third-party dll's being injected into TCC's process space:

a2hooks64 (Emisoft Anti-Malware)
sysfer.dll (Symantec)

Try disabling those and see if TCC starts successfully.
 

rconn

Administrator
Staff member
May 14, 2008
10,164
86
#23
no it is not missing...
sits right there in C:\Program Files\JPSoft\TCMD17x64
with a date of 2 days ago (resulting from installing the test tcmd64.exe you linked in the post above)
Then I suspect (as with Magus) that it's almost certainly a third-party app injecting code. The TCC code is never being executed (as evidenced by the lack of any popup status messages, and the lack of a .GPF file).

If you can run Process Monitor on your system while loading TCC it should allow us to identify the offending dll.