Page 2 of 2 (32 items) < Previous 1 2
This post has 31 Replies | 9 Followers

Posts 160
Darcy S. Van Horn | Forum Activity | Replied: Thu, May 27 2021 12:52 PM

I've been having the same problem for a while now, but thought I'd wait to see if anyone else on the Forums mentioned it before reporting it.  I'm not sure if it was triggered by an update to Logos (9.3 to 9.4?) or to Word 365, but now any attempt to use Additional Actions in Word makes it extremely unresponsive. I currently have 'Enable additional actions in the right-click menu' checked, but none of the specific Additional Actions (including Logos) checked, and Word runs normally.  If I check Logos in the Available actions list, Word stops running normally and is extremely slow to respond, while the Logos Bible Reference function does not work at all.  The only way to restore it is to clear all the Additional Actions check-boxes and restart Word. This is extremely sad as I have used this function extensively for sermon and Bible study prep for years, both to add Bible texts to my Word doc and even to get Logos to open a Bible to a text whose reference I type into a Word doc.  Copy Bible verses is a work-around, but way slower, less efficient, and less convenient.  If anyone comes up with a solution, or if MS posts a fix somewhere, please let us know on this Forum, as the Additional Actions function connecting Logos and Word is one of the most beneficial I've ever used in Logos!  Thanks a bunch! 


Posts 27856
Forum MVP
Dave Hooton | Forum Activity | Replied: Thu, May 27 2021 4:39 PM

Bradley Grainger (Faithlife):
"Enable additional actions in the right-click menu" is buried three layers deep in the Options dialog and disabled by default, correct?



Windows 11 & Android 8

Posts 2
Brian Leicht | Forum Activity | Replied: Wed, Jun 2 2021 5:14 PM

I lost the tags function six months ago on a Dell PC with Windows 10 Pro 32-bit, Office 365, and Logos 7 and got it back 5/14/21 after numerous updates.

In short: I assume the update to 64-bit Windows and Word, update to Logos 9, and registering or installing LSmtTg64.dll recovered the tags function, but I can’t confirm. Maybe the text below isn't necessary, but over many weeks, I appreciated thorough ID of the problem and user-friendly steps others tried. So, I’ll provide a lengthy description.

More information: After updates, Bible reference tags works with my current system:

  • Dell Latitude 7480 Intel Core i7-6600U CPU @ 2.60GHz, 2.81 GHz
  • Windows 10 Pro, 64-bit, version 20H2, OS Build 19042.985, Windows Feature Experience Pack 120.2212.2020.0
  • Microsoft Word version 2008 for Microsoft 365 MSO (16.0.13127.21624), 64-bit
  • Logos 9 Bible Software 9.5 SR-1, (free update, so still with Logos 7 Base Pkg Library)

Problem was same as described by many: right-click on Bible reference > mouse-over Additional Menus immediately disabled specific contextual menus (Additional Actions, Synonyms, Translate, Link, and New Comments) and caused general sluggishness and freeze in Word. Waiting did no good. Necessary force-quit Word (ctrl-alt-delete > Task Manager) or restart even after quitting Logos.

Tags now works perfectly as it worked prior to this problem.

Process included days of research, hard work by our I.T. director, repeatedly “registering” the tags database (whatever that means) per:

and two tech calls with Logos. (Logos reps did not seem familiar with the tags function or the issue, but Logos is clear they “cannot help troubleshoot any problems related to this feature”:, probably due to dependence on Microsoft for the tags function.

Both of the following files are in C:\Users\brianl\AppData\Local\Logos\System\

L4SmrtTg.dll          LSmtTg64.dll           Probably only the second is significant.

I cannot locate the wwlib.dll file Mr. Hooten mentions, so I don't know the version I have. He noted that version 16.0.13801.20266 causes trouble, but the previous version 16.0.13628.20380 worked.


  • No help from Microsoft after much research.
  • Logos gave free upgrade Logos 7 to 9 (minus resources that were not included in 7). This was great but did not fix the problem. Nevertheless, may be necessary to the solution. They did not say a fix was possible.
  • Per Mr. Hooten’s wiki page, registered tags database with PowerShell script download. It did not fix the problem at this point. Tried troubleshooting with Options (AutoCorrect) within Additional Actions, such as deselecting and re-selecting the checkbox by “Logos Bible Software (Bible References)” and other boxes and enabling/disabling Additional Actions with intermittent restarts. No results.
  • I.T. director updated Windows and Word as follows, but that did not help (at least not for several days):
  • Repeated various troubleshooting steps.
  • Windows 10 Pro version update to 64-bit system and 64-bit Office
  • He ran the tags registration script again (several times)
  • Since no result, he agreed with Mr. Hooten (3/9/2021 that Microsoft “deprecated” tags (no longer servicing it?), or perhaps corrupted in some other way as Mr. Grainger mentioned.
  • He gave up. Nothing he tried brought results after three hours.
  • I stopped troubleshooting but tried Additional Actions now and then (with freezing) for two days (denial stage).

Several days later, after prayer for my computer (remember the Sparrow) and checking the function, it worked! Something was definitely resolved.

Thank you to Mr. Hooten and Mr. Grainger and all who commented.


Posts 160
Darcy S. Van Horn | Forum Activity | Replied: Fri, Jun 4 2021 2:23 PM


I'm glad to hear that Smart Tags are working again for you, Brian.  Unfortunately, they still don't work for me.  My set up is not quite the same as yours, though it is fairly similar.  I'm using Windows 10 Home version, 64-bit and 32-bit Office 365.  My version of Windows 10 is 20H2 and the Build is 19042.985, which appears to be the same update as your version of Windows 10 Pro.  My 32-bit Office 365 actually looks like it might be more recent than your 64-bit version (mine is Version 2105, Build 14026.20246), but I'm not sure if the numbers are comparable since one is 32-bit and the other is 64-bit. My laptop has a similar CPU (Intel Core i7-6700HQ @ 2.60 GHz) and my version of Logos 9 is up-to-date (9.5 SR-1, 

I tried reinstalling the Smart Tags dll using PowerShell as per the instructions in the Wiki, but the result is still the same: Word will not access the Logos Reference Smart Tag, and Word slows down incredibly after the attempt.  The only way to get Word running properly again is to deselect the Enable Additional Actions check box under the Add-Ins section of the Options menu and then restart Word. 

So I guess I'm stuck with using Copy Bible Verses for now, but it is much more of a hassle than using the right click Actions menu in Word the way I have been doing for several years.  Hopefully someone will come up with a way of fixing the problem.  Will definitely try prayer, as you did, in your journey to success!  Thanks for sharing your experience. 



Posts 9181

Darcy S. Van Horn:
32-bit Office 365 ... Version 2105, Build 14026.20246

I just updated to this version and can confirm that Smart Tags are not working.

Posts 9181

Brian Leicht:
Microsoft Word version 2008 for Microsoft 365 MSO (16.0.13127.21624), 64-bit

This is older than the version known to cause problems, 16.0.13801.20266, which is probably why your Smart Tag is still working.

It's likely that if you update to 16.0.13801.20266 or later it will stop working again.

Posts 160
Darcy S. Van Horn | Forum Activity | Replied: Fri, Jun 4 2021 6:19 PM

Bradley Grainger (Faithlife):

Brian Leicht:
Microsoft Word version 2008 for Microsoft 365 MSO (16.0.13127.21624), 64-bit

This is older than the version known to cause problems, 16.0.13801.20266, which is probably why your Smart Tag is still working.

It's likely that if you update to 16.0.13801.20266 or later it will stop working again.

Looking at Brian's version of MS Word, I was wondering the same thing.  If he updates to a more recent version, he might lose the functionality of Smart Tags.  On the other hand, I am wondering if I can roll back my version of Office to an earlier point so that Smart Tags would work again.  But this probably isn't a good long term solution because a future update of Word would probably stop Smart Tags from working, and I'd lose any other new/improved features of Word by rolling back to a previous version.  But it is tempting - the Smart Tag function in Word calling Bible references from Logos has been so helpful in my sermon prep for many years! 

Posts 3
Taj Michael Eaton | Forum Activity | Replied: Thu, Jun 24 2021 11:02 AM

Hey sir, I am really clueless as to the innerworkings of the smart tag feature and in reading through this discussion you seem to have a very good understanding. My situation is fairly simple. I recently purchased a new Lenovo laptop and upon downloading Logos to it I had to upgrade to logos 9. I run MSWord 7. After getting everything setup the smart tag features do not work. Is there anything simple I can do? I use that feature MULTIPLE times per day.

Thanks for your time,


Posts 160
Darcy S. Van Horn | Forum Activity | Replied: Thu, Jun 24 2021 3:58 PM

I wish I could help you, but I'm not much of an expert on Smart Tags.  I have recovered the functionality in the past by following the instructions on the Wiki page ( but this recent problem seems to be connected to an update in MS Word, and it doesn't look like there's a solution available for the moment.  Bradley Grainger (Faithlife) and Dave Hooton (MVP) are both far more well-versed in this subject than I am.  Perhaps they could help you.  But if the problem you're having is connected to the current loss of functionality connected to the Word update, I'm not sure if a solution has been found yet.  Still hoping. 



Posts 2
Brian Leicht | Forum Activity | Replied: Fri, Jun 25 2021 11:52 AM

The Copy Bible Verses tool may be the best alternative to the Smart Tags function. It is opened with a keyboard shortcut. Some might prefer it since it’s all keyboard, but there are a couple more steps.

Be sure Logos is running. (No need to type the verse reference in your Word document. Smart Tags are not involved.)

  1. Place the insertion point in the document where you want the Bible verse to appear.
  2. While still in Word (according to “any” Windows or Mac application opens the Copy Bible Verses tool with the keyboard shortcuts Ctrl-Alt-B (Windows) or Opt-Cmd-B (Mac).
  3. Type the verse reference in the search field.
  4. Press “Enter” to display the verse in the window.
  5. Press tab three times to highlight the “Copy and Paste” button. (That’s three moves, ha—we’ll pretend it’s one.)
  6. Press “Enter.” The verse will appear formatted as it would with the Smart Tags method.
  7. Click on or toggle back to your document with Alt-Tab (Windows) or Cmd-Tab (Mac). If you leave the Copy Bible Verses tool window open, for additional insertions of verses, toggle to the Copy Bible Verses tool (Alt-Tab or Cmd-Tab or press the keyboard shortcuts Ctrl-Alt-B or Opt-Cmd-B) and click on or Tab to the search field, 3-4 tabs depending if you go forward (Tab presses) or backward (Shift-Tab presses). 

The nifty Smart Tags method we’d like to keep: (1) type the verse reference, (2) right-click on the reference, (3) mouse over “Additional Actions,” then (4) mouse over “Replace with Passage” and click. 4-plus steps involving keyboard to type verse reference, then only mouse/trackpad.

The Copy Bible Verses tool alternative is 7++ steps with keyboard only.

An advantage of the Copy Bible Verses tool is you can enter multiple, non-contiguous passages at once and enter them all at once (e.g. Jn 1:1,14,Eph 2:1-10,Ro 8:28-30,1 Co 2:14,2 Co 4:4-6,13,16). That isn’t possible with Smart Tags. On the FaithLife forums there are unanswered questions about that limitation (“Replace with Passage Not Working with Non-Sequential Verses”). Since Word used to be able to recognize “Person Names” which could be rather random (a feature that ended in Word 2010), it would seem verse combinations could be recognized, but it’s surely very complex.

Note about versions: You might know, both Word versions, 16.0.13801.20266 and 16.0.13127.21624 (mine), are (were at time of my first post) the most recent supported within their “update channels” ( MS has six channel options.

16.0.13801.20266 is associated only with the “Current Channel” (formerly “Monthly Channel”), version 2102, released March 1, 2021.

16.0.13127.21624 (mine) is associated only with the “Semi-Annual Enterprise Channel,” version 2008, released May 11, 2021. Since my first post, updates bring it to Build 13127.21668, version 2008, released June 8. The exact build numbers do not overlap in all versions, but 13127.##### (version 2008) was replaced by an update in the Current Channel September 28, 2020. That’s about when I lost my Smart Tags function (or perhaps in the next version update October 27). I.T. may have changed my channel subscription when they did the large update that restored Smart Tags.

Perhaps due to testing requirements, Semi-Annual Enterprise is always catching up to the other channels. Therefore, it could be that Smart Tags is only functional (for now) in the Semi-Annual Enterprise Channel subscription and will be disabled when the version updates beyond version 2008 or 2009, which happened in some other channels between September 28 and November 10, 2020 or March 9, 2021 for Semi-Annual Enterprise Channel (Preview).

I decided to continue all updates and not try to hold back—as Darcy said, not updating isn’t a good long-term solution. No doubt it will stop working soon. The Copy Bible Verses tool seems a good fallback with the keyboard shortcut.

Posts 160
Darcy S. Van Horn | Forum Activity | Replied: Fri, Jun 25 2021 1:07 PM

Thanks for all the helpful info about Copy Bible Verses, Brian!  I had forgotten about the keyboard shortcut (Ctrl-Alt-B) which makes it somewhat better than changing focus from Word to Logos, clicking on Copy Bible Verses, typing, clicking on Copy, changing focus back to Word, typing Ctrl-v, etc.  Still miss Smart Tags - it also enabled me to open my Bible in Logos to a passage I typed in Word just to see if it is the passage I was looking for (before actually inserting it in Word).  Was all so easy and convenient!  Anyway, still thankful to have both Logos and Word.  Thanks again for your helpful post.  Like you, not allowing updates to Word is not a long term solution that I want to engage in. 



Posts 160
Darcy S. Van Horn | Forum Activity | Replied: Fri, Jun 25 2021 1:12 PM

By the way, for interest's sake, I just checked my version of Word (formerly Office 365 - now Microsoft 365), and for what it's worth it is Version 2105 (Build 14026.20308). 


Page 2 of 2 (32 items) < Previous 1 2 | RSS