39.0 (39.0.408) is now available
The Logos Bible Study application version 39.0 is now available to all users.
To immediately update to the current stable version, enter Update Now into the command box. Otherwise, the app will automatically update the next time it is scheduled to check for updates.
What's new in Logos v39?
Read an overview of the most important improvements.
Watch a demo of the new and improved features (and a preview of what's coming next).
Or read the detailed release notes.
Comments
-
The link to the technical release notes at the bottom of the article "What's New in Logos? January 2025" is incorrect. Providing incorrect links to the release notes seems to be a recurring problem. However, I do appreciate that the app now links to the article instead of the technical release notes. These articles are well done and fun to read.
0 -
Yep. Mary's great writeup has a bottom link to 'community' but goes to Word by Word. Which is interesting.
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0 -
Investigating.Fixed.0 -
- Command BoxWhen the toolbar is set to the top, the Command Box retains its original width after executing a command.
The most important change you made in v.39. Thank you Logos for finally fixing this.
1 -
I typed Update Now in the command box and it is saying no updates are available. I have version 38.1.2.
0 -
Are you on macOS or Windows? I'll install a version of 38.1.2 on a virtual machine and try updating now via the command box and see what happens on my end.
0 -
Same here @Matt Mattox - Update Now is not working, nor does Logos recognize the update when opened or restarted - running 38.1.2 on Windows 11
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Hi, my Logos updated to 39.0 (Desktop Mac on M4 Mac Mini) and now it's crashing when I click the donut chart under the Translation section of the Bible Word Study tab. This happens with multiple different Greek words. I am unable to use this feature, which is important for my sermon prep.
0 -
Thanks, I'll get my Windows VM and attempt to repro on our end and get a case created for our team.
0 -
Sorry for the disruption and thanks for the report. I'll look at reproing on my end and getting a case for our team.
0 -
Just got my virtual machine up and running with Windows 11. This ended up working on my end. Entering "Update now" initiated the process to download the update.
@Leonard D. Franklin @Frank Sauer - any update on your end or is this still causing issues for you?
Running Windows 11 version 10 (build 22621)
0 -
@M G I can't replicate on my end as entering different greek works and clicking in the donut chart under the Translation section works as expected. Can you provide some greek examples and if possible, a screenshot of your application with the Bible Word Study opened to an example you used. Your log files will also help with identifying the cause of the crash. Could you upload those at a convenient time? See instructions here on how to obtain your log files.
Curious too, what translation did you choose? I tried numerous ones but knowing the exact bible translation you used might help too. i.e CSB, KJV, etc.
0 -
@Matt Mattox - I gave up on the Update Now update route and just installed via installer…. Not sure what the issue is but this is the second release that I have experienced the need to run the installer… Never have had this issue before, no settings changed…
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Took me 3 times today (Jan 16, 2025) to update. I typed "update now" in command box, waited and waited and waited (all of about 10 minutes)…. nothing happened. I closed Logos, then re-opened Logos, still v38.1.2. then I went the "update now again" and this time it worked.
Probably me fumbling around… lol
xn = Christan man=man -- Acts 11:26 "....and the disciples were first called Christians in Antioch".
Barney Fife is my hero! He only uses an abacus with 14 rows!
0 -
We are experiencing some updating/installing issues and are currently investigating.
0 -
@Mark Barnes was excited about the new Reverse Interlinear of the Anglicised NIV.
Many people would be excited once a few Dutch Bibles become available as reverse interlinear. I am very much interested in seeing this come off the ground, as it will serve many existing users and also has the potential to bring in many new customers.
I know qualified people with the original language + tech skills to work on such a project. Is this something we can explore? Feel free to contact me directly in case Logos is interested in pursuing this option.
Dell XPS 17 9700, W11, 32GB, 1TB SSD, NVIDIA GeForce RTX 2060
L5+L9+L10 Portfolio | Logos Max | Translator's Workplace0 -
Thanks for your reply. Peitho is one example. Screenshot and logs attached. NASB2020.
0 -
Yes, "update now," which normally works just fine for me, froze at a certain point and did not complete the install correctly. I had to uninstall and reinstall to get up and running again. Now on version 39.0 and all is well again.
1 -
Verbum 39 is crashing for me as well - logs below
0 -
I can't get it to upload on my Windows 10, 64-bit system. I keep getting an error message it didn't load. I rebooted and made sure I was connected to the Internet and still got the same error message after several tries. However, I had no issues uploading on my new laptop that has Windows 11 and a 64-bit operating system. Go figure! So, I have a help desk ticket placed.
0 -
I would try this and see if it helps:
0 -
I would try this and see if it helps:
I would be cautious about this - running as Administrator.
General guidance has always been that we shouldn't do this - I do recognise it was the fix suggested by the Logos support person mentioned above.
0 -
I suppose it places too much trust in the official Logos installer?
0 -
Can you describe exactly what happened? In what way did it "freeze" - did progress stall or did the app freeze up? Did you see a dialog that said something like "The installation of Logos Bible Software did not complete"?
0 -
Thanks Graham, the team is looking into this.
1 -
I got a pop-up error, and it couldn't install on the final installation. I'm at work, so I can't provide you with a screen print of the error message.
Logos Support left me the following message and an install link to try. I will have to wait until I get home from work and try it.
Hi, Greg. What happens when you run: ?
-
Shara Heiniger
Customer Support
Logoshttps://downloads.logoscdn.com/LBS10/Installer/39.0.0.0408/Logos-x64.msi
It still won't install, even if I try in Administrative mode.
0 -
v39.0 seems to have set off an explosion of bugs. 😦
2 -
I'm now afraid to update!
0 -
Thanks Graham, the team is looking into this.
Thanks @Kamira Rea
Just to let you know I decided to try to update by downloading the Verbum installer and running that. That seems to have worked and Verbum 39 is running again.
1 -
It is a way to overcome problems with permissions on a users install folder which normally do not require Admin privilege. If that perception is correct and Logos then installs without further issue, subsequent updates will also require Admin privilege because it is a workaround.
Dave
===Windows 11 & Android 13
0 -
I will refrain from suggesting this workaround. But I would think there's a possibility that Logos would correct the installer so that it indeed installs correctly in the future.
0 -
I had Verbum v39 thru the beta testing without issues and Logos v38 updated via auto notification. But there was an issue with Smart Tags that caused me to look at the install folder and I noticed the Pending sub-folder was still in place. A restart fixed that and also enabled registration of Smart Tags.
Dave
===Windows 11 & Android 13
0 -
I've tried about everything that has been suggested here. I've closed/re-opened Verbum, reboot several times, ran "update now", deleted installer and let it download and try and install again. It continues to fail to complete the update.
Any other suggestions? Thanks.
0 -
With so many issues with this release I would not be surprised if Faithlife hurries to replace it. Hopefully there is a corrective patch to start. Just my opinion
0 -
Sorry that you're dealing with these issues @JJ Wurtz - if the uninstall and reinstall of V39 did not work, I would personally uninstall and go back to the last V38 found here →
https://downloads.logoscdn.com/LBS10/Installer/38.1.0.0002/Logos-x64.msi
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Yes, hopefully a 39.1 drops soon.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
[BUG REPORT]
MacOS Sonoma (14.5) (But it is happening also on Windows 11)
It hasn't started in this version, but I only had the chance to report now.
In Sermon Builder, when we call for a verse text typing the reference it comes as quotation block, as usual.
In previous versions one was able to double click the Bible reference and could format it, while it was still as quotation block. Now it is not possible.
Logos is fetching Bible Verse from the reference but it appears as "normal" but behaves as quotation block.
My use case: I add a specific format to every Bible reference so when I see it I know it is a Verse. Since some versions, I am only able to see the reference text formatted when I remove the quotation block, changing it to "normal" (even Logos saying it is "normal. Hope the picture attached will help)
Again: please improve your Sermon Builder ASAP. I a heavy user but it will not take long until I abandon it and get back to Onenote or Obsidian. Logos' Sermon Builder is so poor and I preach every week; so imagine my agony… Almost every new update something in Sermon Builder come to be broken.
0 -
Thiago,
I'll leave it to Logos and other users that are familiar with the Sermon Builder to give input on this issue - I honestly have always stuck with Microsoft Word and now Libre Office Writer for my Sermons and Lessons.
If this issue that you are facing impacts your ability to effectively use the Sermon Builder, I'd recommend using Copy Bible Verses with a Word Processor, as you can format the Verse to copy and paste into the word processor as you would like it.
You could then import your sermon into Logos, so it is in your Logos records - it may be a work around until the issue is resolved.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Yes, I understand your point, thank you, but c'mon…
How many dollars have I spent with Logos so far with the hope, as they promised, to have the "ultimate tool to study and prepare my sermons", and now have to open another software and keep copying and pasting Bible References from Logos because their Sermon Builder (in my opinion, one of the most basic features) is a mess.
I had to open my Windows system now to check how messy it was (stopped my sermon prep for tomorrow service).
Check the images provided below.
And more than that, when I go the preach the sermon using my Ipad all my formatting on Bible References is gone! ]Just for the record, trying to help Logos team, the issue is on quotation block option. Have just confirmed that it is "doubling" the reference for some reason.
0 -
I don't disagree - I was trying to give you a work around that has been successful for me personally, until they provide you with a resolution to your problem. In regards to the formatting issue with losing your Bible Verse format, I've not had that issue personally with my technique with my Android tablet and a friend does the same and has no issue with the iPad.
I know there are many who find Sermon Builder to work well for them, I never was comfortable with it myself and feel for fellow users when I read a post with the issues your experiencing.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Yeah, Frank! I thank you for your kind suggestion.
My disappointment goes to Logos poor Sermon Builder indeed!
For tech guys at FL. Please fix it ASAP. Thank you!
0 -
Yeah, Frank! I thank you for your kind suggestion.
My disappointment goes to Logos poor Sermon Builder indeed!
For tech guys at FL. Please fix it ASAP. Thank you!
0 -
Yeah, Frank! I thank you for your kind suggestion.
My disappointment goes to Logos poor Sermon Builder indeed!
For tech guys at FL. Please fix it ASAP. Thank you!
0 -
No problem! I hope that the issue is resolved quickly for you and that it doesn't frustrate your preparation.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
did we lose AI in v. 39.0?
0 -
No, but Smart search will automatically switch to Precise search if you include quotation marks around the entire query or include a Greek or Hebrew word in your query. I'm not sure if this is what you're referring to, but it is new behavior.
0 -
My (German) Logos 38.1.2 on a (German) Windows 10 LTSC virtual machine also does not want to upgrade to 39. It complains about the installation not being successful. Enabling installer logging with EnableLogging.js did not produce any log files. I traced it with procmon and found that it downloads logos-x64.msi and then runs it via msiexec. Manually running msiexec in verbose logging mode ( /l*v ) on the downloaded file resulted in the same error (you see that it uninstalls old version, installs new version, then rolls back, then the message appears) and produces this logfile:
I presume the issue is here:
MSI (s) (F8:2C) [19:11:59:767]: Executing op: ActionStart(Name=RegisterStubMsixPackage,,)
Action 19:11:59: RegisterStubMsixPackage.
MSI (s) (F8:2C) [19:11:59:798]: Executing op: CustomActionSchedule(Action=RegisterStubMsixPackage,ActionType=1025,Source=BinaryData,Target=RegisterStubMsixPackage,CustomActionData=INSTALLFOLDERNAME=Logos;INSTALLFOLDER=C:\Users\User\AppData\Local\Logos;BRANDINGNAME=Logos)
MSI (s) (F8:60) [19:11:59:798]: Invoking remote custom action. DLL: C:\windows\Installer\MSIA570.tmp, Entrypoint: RegisterStubMsixPackage
SFXCA: Extracting custom action to temporary directory: C:\Users\User\AppData\Local\Temp\SFXCABD560F692A44552AC8F9AD0F8375752ASFXCA: Binding to CLR versionv4.0.30319
Calling custom action LogosCustomActions!LogosCustomActions.CustomActions.RegisterStubMsixPackage
Install failed: : Der Windows-Runtime-Typ 'Windows.Management.Deployment.AddPackageOptions' wurde nicht gefunden.
CustomAction RegisterStubMsixPackage returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)Action ended 19:12:00: InstallFinalize. Return value 3.
MSI (s) (F8:2C) [19:12:00:001]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (F8:2C) [19:12:00:001]: User policy value 'DisableRollback' is 0
MSI (s) (F8:2C) [19:12:00:001]: Machine policy value 'DisableRollback' is 0
MSI (s) (F8:2C) [19:12:00:017]: Note: 1: 2318 2:MSI (s) (F8:2C) [19:12:00:017]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1513331066,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=0)
MSI (s) (F8:2C) [19:12:00:017]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (F8:2C) [19:12:00:017]: Executing op: DialogInfo(Type=1,Argument=Logos Bible Study)
MSI (s) (F8:2C) [19:12:00:017]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (F8:2C) [19:12:00:017]: Executing op: RegisterBackupFile(File=C:\Config.Msi\bb428.rbf)
MSI (s) (F8:2C) [19:12:00:017]: Executing op: RegisterBackupFile(File=C:\Config.Msi\bb429.rbf)
MSI (s) (F8:2C) [19:12:00:017]: Executing op: RegisterBackupFile(File=C:\Config.Msi\bb42a.rbf)
MSI (s) (F8:2C) [19:12:00:017]: Executing op: RegisterBackupFile(File=C:\Config.Msi\bb42b.rbf)
Action 19:12:00: Rollback. Rolling back action:
Rollback: RegisterStubMsixPackageJust for testing, I tried to enable MSIX sideloading in Windows settings, and I also tried to manually download setup and run it (both with and without Administrator privileges), but so far none of this worked.
Perhaps I just stay at v38.1.2 :-)
0 -
Since the update you can edit Bible quoatations, but in earlier versions you could delete the quotation as with one ← or Del. Thats not possible anymore and honestly quite cumbersome. Sometimes I just want the reference and if I mistakenly press Enter and want to delete the quotation…
0 -
Well, the icon in the top right that is the refresh icon used to indicate how much AI credits have been used does not now seem to show the AI usage.
0 -
The AI Credit Counter will only display when you have used 1 or more AI credits. Once per month, AI credits are refreshed and drop to 0. When this happens, the counter will disappear. If you run a Smart Search or summarize something, using any amount of AI credits, the counter will appear again.
1
