ScriptureViewer DOWNLOAD LINKS for Windows

Back

ScriptureViewer by Forthright Systems & Consulting (Stan Troeh)

Windows apps are installed in "admin" mode on most computers for personal use. The "non-admin" mode is most often required when installing to corporate computers where corporate policies do not grant you "admin" access. ("Admin" install means that the scripture files and some of the customization settings are shared among all users of the computer, reducing amount of storage required in the event of multiple users.)

Windows systems are protective when accessing software from the internet, due to the number of bad actors in this space.

At this time, ScriptureViewer is an "unsigned" application. The following instructions apply to loading the "unsigned" application should you wish to proceed.

Your browser might try to protect you by blocking or quarantining ScriptureViewerWin.exe. Usually a right-click on the download will provide options. When you try to open (run) the downloaded file, Windows Defender (and/or your anti-virus software) may interrupt. Defender will provide a screen like below, by clicking on the More info link, Defender will add the App & Publisher information and add the Run anyway button. Sometimes the buttons hide off the right side, requiring you to use the bottom scroll bar to make the buttons visible. Click on the Run Anyway button to proceed.
  

Anti-virus software is quite varied but will generally let you (eventually) request that the download be allowed to run.

Once you can run ScriptureViewerWin.exe, you will get a User Account Control box similar to

Press or click the YES button. The remainder is a typical windows install, as shown in these images.

Sometimes your anti-virus will wake up as the install script attempts to run ScriptureViewer for the first time from the final install page. Again, most anti-virus have ways to indicate that you accept the risk.

The final screen (above) normally launches ScriptureViewer for the first time. Thereafter you can launch via the desktop icon or other paths to ScriptureViewer.


If you're stymied by a problem or wish to offer thoughts/requests/suggestions to the developer, reach out: Stan Troeh <stantroeh@gmail.com>. Please include 'ScriptureViewer' and platform (Windows) in the subject line.

Windows 7 and TLS 1.2

On Windows 7, the FETCH button on the By Reference screen will not work unless the internet protocol TLS 1.2 has been enabled. This Microsoft link addresses how to enable TLS 1.2. Under the heading "More Information" there is a sub-heading "Easy Fix" (just past half-way down the page) -- we've found its 'click here' link helpful on our Window 7 machines.