What to do if Logos Crashes | Windows

Print Friendly and PDF

What to Do If Logos or the Logos Indexer Crashes


When trying to open or use Logos the application may close unexpectedly. Depending on what exactly has caused the crash, a message advising that the app has stopped working may appear.

While this doesn't provide any specific information regarding the cause of such a crash, there are a few general responses we can apply to attempt to fix the most common causes.

Note: It is not recommended to attempt these solutions unless the problem occurs more than once. Sometimes an external variable can cause a "fluke" or one-time crash. These instructions are intended to resolve a recurring issue.


Solution 1: Update Logos Manually

Often times updating to the latest version will fix whatever is causing Logos to crash. To do this simply install the latest update from the installation page.


Solution 2: Verify Windows is up to date

Click here and chose your version of Windows from the Product drop-down menu to learn how to check for Windows updates.


Solution 3: Repair the Installation

Sometimes repairing the Logos Bible Study app via Windows' Repair tool in "Programs and Features" will fix what is causing the crash.

  1. Press Windows+R (the Windows key is in the bottom-left corner of the keyboard).
  2. Copy and paste appwiz.cpl into the Run dialog box.
  3. Click OK.
  4. Find Logos Bible Study, right-click it and click "Repair."
  5. Allow Windows to run the install to repair the software.
  6. Open the Logos Bible Study app.


Solution 4: Open Logos to a blank layout

  1. Press and hold the Control key down.
  2. Open Logos with the Control key still depressed.
  3. When the sign-in window appears release the Control key and click Sign in. (Logos should open to a blank layout)
  4. To navigate to the home page click the house icon in the top left or use Logos as you normally would.


Still having trouble?

If these solutions do not resolve the issue, it will be necessary to collect more information about the problem. Please visit the enable and submit logs page for instructions on how to collect and submit more data to troubleshoot the problem.

Was this article helpful?
Suggest an improvement or request a feature