Welcome!

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

SignUp Now!

Problem with Updating

Jay Sage

Jay Sage

Jun
1,092
48
When the updater closes Take Command and its TCC tabs, the update program is closed as well. The only way I can update is to manually download the program and run it from Windows.
 
My procedure is to start the update process and before responding to "Download and run the installer?", close all instances of EXEs which the updater must update. That's usually just TCC and TCMD because other things (notably Everything) are typically not running.
 
I can do those things, but it wasn't necessary before this version. In some builds it has worked OK, but it has stopped working again.

I don't know if it's a ConPTY thing, but this seems to be another one of those things that stopped working in the latest version. On the other hand, Rex has slowly and surely fixed (almost all) the problems. In particular, the returns from XDIR and @GETDATE are now working.
 
Jay Sage said:
When the updater closes Take Command and its TCC tabs, the update program is closed as well. The only way I can update is to manually download the program and run it from Windows.
Click to expand...

I don't understand your issue - when the updater (TCUPDATER.EXE) is run from TCMD or TCC, it checks the server to see if a newer version is available. If it is and you choose to download it, TCUPDATER downloads the new installer and launches it. TCUPDATER then exits, because there isn't any reason for it to hang around.

So the updater doesn't close TCMD or TCC, the installer does (so it can overwrite them). And TCUPDATER is already long gone by then.
 
rconn said:
So the updater doesn't close TCMD or TCC, the installer does (so it can overwrite them). And TCUPDATER is already long gone by then.
Click to expand...

OK. Then to be more precise, when TCMD, TCC, etc. are closed by whatever is closing them, the installer is also closed, aborting the process.

I'm doing the install now for build 40. I am up to the screen that says "Preparing to Install" and asks to automatically close the listed applications: several TCCs, Take Command, and Everything. I click "Next". All those apps close, and so does the installer. No update performed.

So now I open the Windows File Explorer, find the tcmd.exe that was downloaded to my "downloads" directory, and launch it. Now it asks only to uninstall Everything, which it does successfully, and the installation proceeds.
 
Jay Sage said:
OK. Then to be more precise, when TCMD, TCC, etc. are closed by whatever is closing them, the installer is also closed, aborting the process.
Click to expand...

I left TCC running in WT when I updated. I told the installer to close it. It did and the installation continued.
 
I run this now before updating. Solved the problem of not being able to close instances.
taskkill /F /IM everything64.exe /T
taskkill /F /IM ShrAlias.exe /T
sc stop "Everything"
 
For the update to build 42, I planned to try something different (start the update from a standalone TCC) and encountered again a problem that others have also reported: tasks started from a TCC tab in TCMD are closed when TCMD is closed.

I launched a standalone TCC using: start /elevated /pgm C:\Windows\System32\conhost.exe %tcmdpgmdir\tcc.exe. Then I closed TCMD by clicking on the 'X' in the upper right corner. That closed not only the TCMD session but also the standalone TCC. That does not happen without the "elevated" option.

From the non-elevated TCC, I was able to do the update, and it successfully closed the TCC and Everything tasks.
 
I just tried the same test in build 42, and the elevated TCC session launched from TCMD is terminated when TCMD is terminated by any means ("exit" from TCC or clicking any of the 'x' buttons). It is not terminated if a different TCC tab in TCMD is terminated.
 
I can reproduce something like that (with no particular reference to updating).

In an elevated TCMD with only one TCC tab, issue start /elevated [path_to]tcc.exe (use /PGM if quotes are needed). At this point, EXIT in the TCMD tab will cause TCMD to wait for the STARTed TCC ... and X-ing TCMD will take the STARTed TCC with it.

All of that changes if "/elevated" is removed from that command (even though the STARTed TCC will be elevated anyway). Without "/elevated" in that command line, the tabbed TCC can exit, takingTCMD along with it, and not affecting the started TCC. And TCMD can be X-ed without affecting the STARTed TCC.
 
You must log in or register to reply here.
Back
Top