This article describes how to identify when Logos has crashed and what to do in response.
Note: We do not recommend these solutions unless the crash occurs more than once. Sometimes an external variable can cause a “fluke” or one-off crash. These instructions are intended to resolve a recurring crash.
Update Logos
Be sure you have the latest version of Logos by downloading and running the installation software from the here .
Verify Windows is up to date
Click here and chose your version of Windows to learn how to check for Windows updates.
Repair the Installation
Sometimes repairing the Logos via Windows' Repair tool in "Programs and Features" will fix what is causing the crash.
- Press Windows + R (the Windows key is in the bottom-left corner of the keyboard).
- Copy and paste appwiz.cpl into the Run dialog box.
- Click OK.
- Find Logos, right-click it and click Repair
- Allow Windows to run the install to repair the software.
- Open Logos.
Open Logos to a blank layout
- Press and hold the Control key.
- Open Logos with the Control key still held.
- When the sign in window appears release the Control key and click Sign in. (Logos should open to a blank layout.)
- Click the Dashboard icon
in the top left or use Logos as you normally would.
Third-party Security Software
Third-party security software can cause Logos to crash. Follow your vendor's support documentation to create an exception for Logos, or add Logos to a whitelist in your security software's settings.
You can find the Logos file by following the steps below:
- Press the Window key + R.
- Type %localappdata% and press Go.
- Open the Logos folder.
Still having trouble?
If these solutions do not resolve the issue please visit our article on how to enable and submit logs for instructions on how to collect and submit more data to troubleshoot the problem.
Update Logos
Be sure you are running the latest version of Logos by replacing the application file with the newest version from our website.
- Quit Logos and open Finder.
- Navigate to the Applications folder.
- Locate the Logos application.
- Move it to Trash on your Dock (this does not delete books or index).
- Download and install the latest version.
Tip: Run Software Update to ensure your Mac has all the latest updates from Apple.
Open Logos to a blank layout
- Press and hold the Cmd key down and open Logos with the Cmd key still depressed.
- When the sign in window appears, release the Cmd key and click “Sign in.” (Logos should open to a blank layout.)
- Click the Dashboard icon
in the top left or use Logos as you normally would.
Validate macOS’ Fonts
- Open macOS’ FontBook utility found in the Utilities inside the Applications folder.
- Follow the Validate fonts instructions here.
- Delete all fonts that macOS indicates validation has failed for via a red icon and test the behavior again.
- If the crashing continues, you may want to remove fonts flagged with a yellow icon indicating there was an error with them and test again
Check Font Book for Corrupt Fonts
Logos loads fonts from the Font Book when opening. If an incomplete or corrupt font has been detected, Logos may crash while loading it. Use the steps below to check for and remove bad fonts.
- Download the MacFontTest Tool.
- Extract the FontTest application (if it didn’t extract automatically).
- Open FontTest (use Control-click if you receive a warning dialogue about the file being created by an unknown developer).
FontTest will attempt to load all fonts in the Font Book. If a bad font is detected, an error will be displayed. Delete the last font loaded before the error, then repeat this process until no errors occur. Below is an example of what will appear if the Mac FontTest Tool finds a corrupt font.
Checking CappioExtrafrisky
display name: CappioExtrafrisky
Checking Cardigan
display name: Cardigan
Checking Caricature
display name: Caricature
Checking Carolus Roman
Bus error: 10
——
In the above example Carolus Roman should be removed from macOS’ using the FontBook utility found in macOS’ Utilities folder inside the Applications folder.
Report the Problem
If these solutions do not resolve the issue please visit our article on how to enable and submit logs for instructions on how to collect and submit more data to troubleshoot the problem.