Logos and Security Software

Logos scans the binaries for every application before they are available for download. We will never release software that has malware embedded within it. You can upload any file file to VirusTotal and scan it for malware for free. 

Problem:

During an update to Logos, a security application (e.g.: Avast, Norton, McAffee, etc.,) may:

• Attempted to delete or quarantine a Logos file.
• Provide an erroneous message that there is malware in the package.

When opening Logos or LogosSetup you may see a message that "Windows cannot access the specified device, path, or file", "You may not have the appropriate permissions to access the item" or Logos may shut down unexpectedly.

See will also: Unable to connect to Logos.com and Unable to Download a Required File or Resource

Solution:

Step 1: Adding an Exception

1. Identify and open the responsible security application.
2. Locate the instructions for adding a file or folder to the security application's exceptions list.
3. Add an exception for the Logos directory¹ (or Logos.exe file in the Logos directory).

Step 2: Repairing Logos

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. Right-click Logos Bible Study and click Repair.
5. Allow Windows to run the install to repair the software.
6. Open Logos.

Is Logos a threat?

At Logos, we take extensive steps to ensure security for Logos users and maintain a clean application. It is highly unlikely that Logos contains an actual threat, but occasionally some antivirus and security vendors may flag a Logos component by mistake. As long as you are downloading Logos from logos.com or an official Logos email, you should not need to be concerned.

¹Note: Due to the extreme variation in security application user interface (both across applications and overtime within the same application) it is impossible to provide comprehensive steps on how to create exceptions in any one security application. We urge each user that uses a third-party security application to become familiar with their application's exceptions processes. Please contact your security application vendor for further assistance.