Beta 7 Installation failing

David B Phillips said:

Downloaded new updates, but I keep getting an error message that the installation has failed.

David, 

In looking at the log file, it appears that Windows Installer is failing to install the update because it's busy installing another install package. Maybe your machine is doing a Windows Update or something? I think that if you rebooted the machine and tried again that it would succeed. 

How did you first initiate the update? Was it from a tip or menu associated with the Indexer icon in the Task bar, or was it from a message box you saw when you launched Logos 4? I'm assuming that you're getting the error when launching Logos 4 and answering Yes to the install-new-update question. If you say no to launch Logos 4, could you check the version (click the question mark button in the upper-right corner of Logos 4 and choose About Logos Bible Software) and make sure that it's not already updated to Beta 7? 

Also, if you have a logos4indexer.log file, that might be helpful, too. 

Thanks,

Bryan

David,

I looked into the situation a bit more. It looks like when Windows Installer ran the Prerequisites Update on 10/6 that it either detected that the system needed to restart or it decided that the system needed to restart, I'm not sure which. Presumably, Windows Installer needed to restart the system in order to finish an installation it was doing, either the Prerequisites install or some install prior to that one. In any case, it appears to be in a loop where it won't let another setup start until the last one finishes, it thinks that the system needs to restart before the last one can finish, yet after a restart it doesn't finish. 

Please check these registry keys, if you're comfortable doing that and you know how, otherwise we'll figure something else out:

HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress

HKLM\System\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

Do these keys exist, and, if so, what are their data entries?

David B Phillips said:

HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress

Name: (Default)                  Type: REG_SZ                     Data: C:\Windows\Installer\ae1ecb.ipi

There is no PendingFileRenameOperations. There is a FileRenameOperations, which is set at the following:

Name: (Default)                 Type: REG_SZ                   Data: (value not set)

Great! Okay, from what I gather that's your problem. Windows Installer is checking those keys, the first one at least, deciding that there's an install already in progress and returning the error code. So, if you rename the InProgress key to something else, like NotInProgress, and rename the other key FileRenameOperations, too, the install should work.

If it works, which it should, you can just delete those keys and you should be good. (After a successful install, those keys don't exist at all.) 

Let me know how that goes!

Thanks,

Bryan