Every time my computer boots Logosindexer.dll fails to run

TCBlack
TCBlack Member Posts: 10,978
edited November 21 in English Forum

Every single time I try to load my computer (windows 10 initially, and now even windows 11 after a recent upgrade) I get a dialog telling me I'm attempting to open a file type of DLL.  

I hit open in Notepad so I can figure out what it is: this proves to be the Logos Indexer DLL as seen here:

I have gone in and actively removed it from the registry - and it came back.

(It was at: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce)

The key is named: "C:\Users\<Myusername>\AppData\Local\Logos\System\LogosIndexer.dll" /user:zlixaonx.tbh /lang:en-US

This has been going on for months, but as I seldom reboot my computer I keep forgetting to post this.

I'm going to delete it again since my registry is open again.  But has anyone else experienced this?

Hmm Sarcasm is my love language. Obviously I love you. 

Tagged:

Comments

  • DMB
    DMB Member Posts: 13,413 ✭✭✭

    Haven't seen you for a while, TC!  Hope all is well for you.  I always associate a water tower with you ... I think you looked out your window at one.

    I'm assuming Dave's the expert.  And I'm on a Mac. But the indexer loads quite early in the Mac startup. I'd assume also on Windows.  I'd think the mixup is not the dll loading but rather how it bening opened?

    "If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.

  • Dave Hooton
    Dave Hooton Member, MVP Posts: 35,672 ✭✭✭

    I'm going to delete it again since my registry is open again.  But has anyone else experienced this?

    I have never experienced this, and can't imagine why Logos would defer indexing in this manner (let alone running the dll versus the exe).

    I suggest you contact Customer Service and let them have access to your computer.

    Dave
    ===

    Windows 11 & Android 13

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 11,955

    Thanks for reporting this; it's a bug in how the indexer registers itself to re-run if you reboot your system before indexing finishes. (It should be "LogosIndexer.exe" not "LogosIndexer.dll".)

    This registry value is typically deleted when the indexer completes working. Your seeing it on every single reboot must mean that your indexer is crashing every single time it tries to run. Can you upload LogosIndexer.log and LogosIndexerError.log files?

  • TCBlack
    TCBlack Member Posts: 10,978
    https://community.logos.com/discussion/comment/1279090#Comment_1279090

    You bet, sorry for the delay.

    Here are the log files. 2451.LogosIndexer.zip

    EDIT: Schrödinger's Bug.  I uploaded those logs, then decided to reboot as a test. Of course for the first time in months that dialog didn't happen. Thanks for the speedy fix!

    :insert shrugging meme gif here:

    Hmm Sarcasm is my love language. Obviously I love you. 

  • TCBlack
    TCBlack Member Posts: 10,978
    https://community.logos.com/discussion/comment/1278832#Comment_1278832

    Greetings right back at you!  Yeah I'm ok.  :-)  

    Hmm Sarcasm is my love language. Obviously I love you. 

  • Savanna Lineberger
    Savanna Lineberger Member, Logos Employee Posts: 759

    Every single time I try to load my computer (windows 10 initially, and now even windows 11 after a recent upgrade) I get a dialog telling me I'm attempting to open a file type of DLL.  

    I hit open in Notepad so I can figure out what it is: this proves to be the Logos Indexer DLL as seen here:

    I have gone in and actively removed it from the registry - and it came back.

    (It was at: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce)

    The key is named: "C:\Users\<Myusername>\AppData\Local\Logos\System\LogosIndexer.dll" /user:zlixaonx.tbh /lang:en-US

    This has been going on for months, but as I seldom reboot my computer I keep forgetting to post this.

    I'm going to delete it again since my registry is open again.  But has anyone else experienced this?

    This has been resolved in 31.0

Categories