This is what I got back from the installer developers:
---------------------------------
Unfortunately we can't replicate the behavior either, we tried with both EXE and MSI.
From the log, this behavior seems to be related to your software's prerequisites, however I am not sure because the log has an abrupt ending. This may very well be related to something blocking the installer on that particular machine.
You could also look with Event Viewer to see if Windows logged anything significant.
To quicly open Event Viewer try:
• Windows key + R
• type in "eventvwr" then Enter
Look in the Setup and Application sections.
Also try testing on a clean machine with a similar configuration/architecture as your client's. If your attempt is successful, you can rule out anything to be wrong with the installer itself.
Another thing that came to mind: your client can try to install any required prerequisites before running the main installation. If there are any prerequisites already installed on that machine, have him re-install them and then try the setup again.
----------------------------------------------
The TCMD installer does not have any prerequisites. The only thing it's doing before performing the installation is looking to see if Everything Search is running, and if so the installer stops it so it can install the new version. Do you have Everything Search installed? If so, try stopping that manually before running the installer and see if it changes the behavior.
Are you doing an upgrade of an existing TCMD installation, or doing a new install?
Rex Conn
JP Software