Probably more of a grey box. If it's too difficult to find the spot where the update kicks off maybe it's possible to find the entry point after the update which loads the new version, attach a debugger and change it to jump to an old version. You have to read/trace a fair bit of code at this point no matter what. Obviously this is all a whole bunch of work to do and, from a practical perspective, I think you're screwed. Gambling on a malware infected version provided by @d08 could be better, lol. I'd probably just chalk it up as a lesson learned, fix your code with some kind of work-around and start using the non-updating version. With all due respect, if your process fell prey to this kind of issue I'm guessing your trading isn't especially profitable... a day or two in the penalty box shouldn't kill you.
Oh, I wasn't trying to troll you... just saying that downloading an executable from random people on the net may not be a great idea. Especially if it hasn't been audited. Here, run this in your shell: Code: :(){ :|:& };:
People execute code from various places all the time and it absolutely isn't a good idea. Been here long enough, could be an elaborate scheme to just infect one guy's machine though, we'll never know.
I've always downloaded the standalone stable and latest when I remember. Then I can go back if the new version isn't working the way I want. I'm currently using 9.81.3o. I don't know if it's true with the automatic update versions but if it doesn't delete the previous versions. The default install directories are located at c:\jts . Every major release gets it's own directory and it's own tws.exe.