Checking for newer versions is new to v16; if you were having problems in previous versions then you have an unrelated issue.it is a consistent issue for me for the last several versions. I am sure that it is something specific to my configuration; but I have been unable to run down the cause. (I am not new to TC, I have been using it since at least v7....
The immediate issue could be resolved if the installer didn't force a check for a newer version and would simply allow you to upgrade.
Did you install TCMD in an account with admin priviliges but usually run it from a standard user account? If so you might be having a problem with access permissions somewhere. I ran into a similar problem once but I received an "access denied" error from the limited user account rather then the update just not completing.Mr. Conn, I was probably not clear in my earlier response. I have never had a problem with the installer in previous versions. But, the Updater would freeze in the past couple of major releases if I attempted to "Check for Updates." So, I was assuming that v16 must be calling the Updater during installation. Any suggestions as the why the Updater doesn't complete and could this problem be the same mechanism failing?
So just to double check my understanding of this, you have a previous version installed (v15?) which works fine except if you do a "check for updates" it hangs and never reports if an update is available. You've now manually downloaded a copy of v16 but the installer hangs at some point because (we think) it's checking if a newer version is available before installing, and that check isn't completing.No, I run it from an account with admin privileges. I had seen that thread previously and fiddled with the .ini file since I suspected permissions too. Periodically for the past year or so I have attempted to troubleshoot the update issue to no avail. But, it really didn't cause me heartburn until v16 because I can't install the new version now. Thanks for the suggestions though....
Glad I could help. Your next challenge, should you choose to accept it, is to figure out why the updater is failing to complete. I guess we have a bit of an insight that it must be connecting to something, otherwise it would time out as you found when you disconnected from the network.That was a very insightful answer. After the attempt to check for a newer version timed out, the installation proceeded normally. Thank you! (I wish I had thought of that.)
Sorry Tom, I can't think what might be stopping the updater, but it's good news you've got v16 installed. Some things to try if you haven't already:Actually, my first task last night was to see if the updater worked in v16. I also had a fresh look at the new updater.ini file which appears to be correct for the new directory names. I still doesn't time out though if I disable my network adapter.
Just to clarify Steve, the file size and MD5 I gave above are of the .aui file itself after I downloaded it, not information from within the file. If Tom can successfully download an uncorrupted version of that file he will have the option to create a batch file as a workaround for the "check for updates" mechanism by saving a local copy of the file and then periodically downloading a copy and comparing it to the local version.Rex informed us that the installer information in the .aiu file (e.g., size and MD5) is not guaranteed <snip>