The Curious Case of The NoClose No (via Teamviewer)

English support forum

Moderators: white, Hacker, petermad, Stefan2

Post Reply
User avatar
Phred
Senior Member
Senior Member
Posts: 375
Joined: 2009-06-16, 15:24 UTC
Location: SEAu

The Curious Case of The NoClose No (via Teamviewer)

Post by *Phred »

(I can find no reference to this in the English forums, and it's probably not a bug in Vn10Rcs per se, but it is real.)

I find consistently that when updating/reinstalling TC over a Teamviewer connection that TC fails to install over-the-top with a failure of the NoClose executable.
It's not critical, but it is a failure, and may have implications for remote corporate management, as well as its being a nuisance for mere mortals.

Circumstances:
Win10Pro on two computers; TC10x
Remote standard user via Teamviewer
Standard user host
Execution of 'TCsetup.exe'
Choosing of update/reinstall over existing install
Entry of admin credentials at UAC elevation prompt*
Acceptance that running TC instance must be closed
>> Failure of NoClose... - Unsuccessful update of TC (or words to that effect).

[* Excellent!]
Regards, PhredE
Licence holder since 1999
Awaiting a $D donors-token for the title-bar so we can display that we have donated further.
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48021
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Re: The Curious Case of The NoClose No (via Teamviewer)

Post by *ghisler(Author) »

Try closing totalcmd.exe / totalcmd64.exe via task manager.
Author of Total Commander
https://www.ghisler.com
User avatar
Hacker
Moderator
Moderator
Posts: 13052
Joined: 2003-02-06, 14:56 UTC
Location: Bratislava, Slovakia

Re: The Curious Case of The NoClose No (via Teamviewer)

Post by *Hacker »

Christian,
How will that help install noclose.exe?
EDIT: Perhaps I misunderstood the original post.

Roman
Mal angenommen, du drückst Strg+F, wählst die FTP-Verbindung (mit gespeichertem Passwort), klickst aber nicht auf Verbinden, sondern fällst tot um.
User avatar
Phred
Senior Member
Senior Member
Posts: 375
Joined: 2009-06-16, 15:24 UTC
Location: SEAu

Re: The Curious Case of The NoClose No (via Teamviewer)

Post by *Phred »

ghisler(Author) wrote: 2021-05-30, 08:45 UTC Try closing totalcmd.exe / totalcmd64.exe via task manager.
Yes, correct, I could, Author Ghisler, but it's a speedbump that may not be necessary, an interruption to workflow, especially in corporate environments. Another memory item. An irritation, an unpredicted.
...It's nice to have a file manager to locate a setup executable, and what better file mangager can we think of than...?

And as Roman implies, NoClose might be inhibited from installing.
[edit: or not]

BTW, where you cite 'TOTALCMD.EXE' et al, is it time yet to change from ALL-CAPS short filenames within the 1980s 8-chara limit, for easier interpretation?
But that's for anther thread..
Regards, PhredE
Licence holder since 1999
Awaiting a $D donors-token for the title-bar so we can display that we have donated further.
User avatar
Phred
Senior Member
Senior Member
Posts: 375
Joined: 2009-06-16, 15:24 UTC
Location: SEAu

Re: The Curious Case of The NoClose No (via Teamviewer)

Post by *Phred »

I'll have to put this record on hold - I can't reproduce the behaviour.
I returned to the setup at the two PCs on which the NoClose error occurred, both in situ and via Teamviewer, and the error repeated.
I decided later to take screenshots and tried again - but couldn't raise the fault. I can see no reason for the change; neither PCs have been rebooted.
I was experimenting independently with SchTasks.exe in a Dos-box invoked by Run-command.exe (SoftwareOk.com) and editing a batch file with NoteTab Pro, but even reproducing that environment hasn't 'enabled' the fault again.
THREAD ON HOLD.
Regards, PhredE
Licence holder since 1999
Awaiting a $D donors-token for the title-bar so we can display that we have donated further.
Post Reply