BUG: In-program Update Failure

Lee
Lee Member Posts: 26
edited November 21 in English Forum

Since updating to Logos 10 (including SR and 10.1) on some computers the in-program update would fail with update to application "did not succeed" even though the full 299MB was downloaded.

When this happens, the entire 299MB update has to be downloaded again as if the previously downloaded chunk of data was deleted.

Sometimes, the update has to be initiated a few times before the update takes. Sometimes, nothing works and the update has to be performed manually with the latest LogosSetup.exe.

On every retry, 299MB of data has to be re-downloaded.

This bug is very inconvenient.

Tagged:

Comments

  • Dave Hooton
    Dave Hooton MVP Posts: 35,677

    This is rare. So it would be interesting to see logs on this for the next update, meaning that logging has to be permanently enabled if you permit downloads to start automatically (it isn't noticeable as I always have it enabled).

    Dave
    ===

    Windows 11 & Android 13

  • Lee
    Lee Member Posts: 26

    It happened several times but I never thought to log it. The in-program updates happen when I manually update within the desktop app and click on download available updates.

    The main annoyance is that an unsuccessful in-program update clears the download cache and triggers a re-download of 299 MB.

  • Joe McCune (Faithlife)
    Joe McCune (Faithlife) Member, Logos Employee Posts: 1,134

    Since updating to Logos 10 (including SR and 10.1) on some computers the in-program update would fail with update to application "did not succeed" even though the full 299MB was downloaded.

    If any user is having any difficulty with the in-program update, I would recommend closing or quitting Logos and using these instructions instead.

    Although these instructions are primarily meant for users installing Logos from scratch, they work just fine for getting the program up-to-date.

    Like I said, I recommend doing this for any user struggling with the in-program update, but I especially recommend it if you are making a big leap from your installed version of Logos to the new version.  Like if you have Logos 7 installed but have just upgraded to Logos 10.

  • Lee
    Lee Member Posts: 26

    If any user is having any difficulty with the in-program update, I would recommend closing or quitting Logos and using these instructions instead.

    Thanks Joe, eventually I had to resort to updating outside of the program according to the instructions.

    I had issues with in-program update going from the first build of Logos 10 to the next build (241 I think). Then faced problems again going to 10.1 from 10 SR-1. These weren't big level jumps.

  • Lee
    Lee Member Posts: 26

    It happened again on one machine.

    Update 10.1 to 10.1 SR-1, download in-program content of 680MB, goes into "Installing application update..." but errors out with:

    The installation of Logos Bible Software did not succeed.

    I see two bugs here:
    1. The failure to update.
    2. The repeated and useless download of 299MB which in some situations is extremely expensive and impractical.


    I have captured the LogosSetup.log. If any Faithlife technical support person wants to have a look at the logs, please leave his email address here.