You may receive one of the following errors when attempting to update or install Logos Bible Software:
From LogosSetup: "Unable to download a required file"
From within Logos: "A download or update was found, but did not download or install."
LogosSetup process merely hangs without progressing for a significant amount of time (>30 minutes).
LogosSetup ends prematurely and is not visisble in Task Manager.
This problem occurs when Logos or LogosSetup is unable to download resources or the individual installers necessary to install Logos.
If solutions 1-4 do not resolve the problem, see BITS Troubleshooting.
Sometimes this error can appear if the Microsoft's Background Intelligent Transfer Service (BITS) has been temporarily disabled. To resolve this possibility, reboot your computer before proceeding.
Solution 1: Verify Windows Update is not running
Please ensure Windows Update is not currently checking for, downloading, or installing an update when running LogosSetup.exe. Allow Windows to download and install all updates prior to installing Logos.
Solution 2(A): Make sure your computer is plugged in.
Windows 10's Battery saver setting disables certain features that use increased energy. This can conflict with LogosSetup's ability to download required files. Turn the feature off or plug your computer into an outlet will eliminate this behavior.
Solution 2(B): Allow Setup through the Firewall
If you use the Windows Firewall, these steps will help you "allow" Logos to communicate with the Logos servers to update Logos or Logos resources.
Download LogosSetup.exe from the install page here and save it to your Desktop.
Click the Start menu in the bottom-left hand corner of your screen.
Click the gear icon on the left.
In the Find a setting field type firewall.
Select Allow an app through Windows Firewall.
Click Change Settings and Allow another program...
If Logos Bible Software is not listed, click Browse... and locate the Logos.exe file.
Default Location: C:\Users\your name\AppData\local\Logos\Logos.exe
Logos Bible Software" will now appear in the list.
Click "OK" to apply the changes and retry the Logos download.
Solution 3: Allow Setup through additional Firewalls
(See Also: Using Logos with Security Software)
Third-party security software may vary, but the general principles are the same. Look for a "Settings", "Options" or "Firewall" menu, then open the "Allowed Programs", "Exceptions" or similar menu to add Logos.exe and/or LogosSetup.exe to the exceptions list. If you need more specific help with a third-party security software you can contact the maker of the software for more specific instructions to allow program exceptions.
Solution 4(A): Allow LogosSetup through a Proxy
If you connect to the internet through a large Campus or Office network, it is possible you connect through a Proxy. Proxy Settings are usually controlled by your Network Administrator. You can enter proxy setting information into the Sign in window for Logos on Windows.
Hold the Control key down before and while you open Logos.
Keep Control held down until the sign in window appears.
Click Proxy Settings and enter your proxy information.
Solution 4(B): Turn off Windows' Proxy
Even if you don't have a proxy setup by a network administrator, it's possible Windows' proxy has been enabled in Windows. Whether you recall enabling it there or not it is worth checking.
Click the Start menu.
Click the "gear" icon.
Click Network & Internet.
Click Proxy on the left.
Make sure under Manual proxy setup" that Use a proxy server is set to off.
Logos uses Microsofts' BITS to download necessary files to support and install Logos. If the above solutions do not resolve the issue, it may be possible the BITS service has been damaged, is overloaded, or is disabled. Use BITSAdmin to check the BITS' current status.
Click the Start menu.
Type in cmd.exe.
Right-click on cmd.exe.
Choose Run as administrator.
Type: BITSADMIN /LIST and hit enter.
This will display two possible results:
Result 1: A list of Jobs
If you receive a list of "jobs", we know BITS is enabled, but if that list contains more than 50 items it's possible that it has become overloaded. We can clear the list to resolve this.
In most cases, overloaded downloads are stuck in a "suspended" or "error" state and will not download on their own anyway. Type the command BITSAdmin /list and press Enter/Return to view a list of current BITS download "jobs" .
If you see over 50 jobs you may need to run the BITSAdmin /reset to clear the BITS jobs in order to allow LogosSetup access to BITS. The /reset command cancels downloads currently using BITS.
It is recommended to run Windows Update after doing this. If you receive an error downloading Windows Updates speak with a Windows certified technician.
Result 2: No results found
If you see that no results appear(the number 0 will also be absent) when running bitsadmin /list then something may be wrong with the service. Running the winsock Reset (see below) command and restarting the computer may fix this, but if BITS is inaccessible, it may have been damaged by a virus or malware attack or disabled by your administrator so that Windows Updates can be managed at the admin level.
Reset the winsock catalog
If the download process hangs and provides no error messages, resetting the computer's network adapter may be necessary. This is done by opening a Command Prompt as an administrator (see Using BITSAdmin above) and running the following command:
netsh winsock reset
Restart the computer and run BITSAdmin /list.
If there are still no results you will you will need to contact your network administrator, computer manufacturer, or Microsoft for assistance repairing or enabling BITS before you will be able to use the Logos.
Result 3: BITS generates a Transient Error.
If you receive a Transient Error when running bitsadmin /list you will want to obtain a set of "verbose" BITSadmin logs. Copy and paste the following command into the command prompt and hit enter:
bitsadmin /list /verbose > "%USERPROFILE%\Documents\bitsverbose.txt"
The BITSadmin verbose logs are located in your Documents folder with the name bitsverbose.txt. Use the contents of the log to find the specific error number.
You can use this to investigate what is causing the transient error in Windows' BITS service, or provide this information to a computer technician to help them troubleshoot the problem for you.