Quiet install of Paratext 8/9

Question

Recent attempts to do a quiet install (without user interaction) of Paratext have resulted in a situation where C:\ (and not a subfolder of it) ended up being used as the project folder.
Is it possible to run a quiet install of Paratext 8 or 9 in such a way that a regular ‘My Paratext … Projects’ folder ends up being used as project folder?

Answer 1

@anon818964, I am able to recreate the problem and have created the following Paratext support issue: PTX-21029. Here is what I found about this problem:

The error message suggests looking in Help for how to fix this, but that is not possible, since the program will not start.

I tried to uninstall the program from the Apps & features tab in Windows Settings, choosing the ‘Remove settings’ option. I also tried to clean up left-over registry entries using Revo Uninstaller. But after installing again (not using the /quiet option), the same errors occurred, and the same resources were copied to the root folder!

To get Paratext to open, I had to delete the following key from the Windows registry prior to opening:
HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Paratext\\8\\Settings_Directory
After opening, Paratext did an automatic download of an update and suggested I restart Paratext. On restart, the registry key got the wrong value again, so I had to delete it a second time.

All that to say, please don’t try using the /quiet feature again on any machine until we are able to fix this bug!

Comments

@thoatson, has there been any progress on this issue?

Answer 2

@thoatson or @anon291708, has there been any progress on this issue?

And would a similar issue apply to Paratext updates (in the sense that they should not be performed ‘quietly’ either)?

Answer 3

There hasn’t been any work to specifically address this issue. I’m guessing the product owner considers this a low-priority issue, sorry.

Is there a particular reason you want/need to do a quiet install?

Answer 4

@anon291708
Not being able to do a quiet install means that we cannot automate the installation (or update) in what would be the preferred way for that in our situation.
This led to some extra work last year, and may lead to some extra work on future occasions.
It is not a big problem, but rather a matter of convenience.