Follow-up to my last message. I installed Bible Analyzer on my wife's computer. She has Windows 10, version 22H2. She uses Microsoft Edge as her default web browser (I use Chrome), and she does not have extended security updates enabled. In other words, she has not had any security updates to Windows 10 since November 2025.
After a fresh install of Bible Analyzer on her Windows 10 computer, she experienced the same error that I have showed in previous messages.
I also have a laptop with Microsoft Windows 11 Home, ver 10.0.26100 Build 26100, version 24H2 (I have version 25H2 available for download, but I have not installed that update yet). On this laptop, I have Bible Analyzer version 5.6.5.04; my default browser on the laptop is Edge.
The same problem appears on Windows 11. Here are the steps to reproduce the issue:
1. Run Bible Analyzer
2. Press Alt-G to bring up the Parallel Presenter
3. Select module (Top Left) to "The Discourses of Jesus"
4. Change the title (Top Center) to "The Sermon on the Mount"
5. Change module again to "The Fourfold Gospel"
At some point in changing modules and titles, you should see the error message, "Error running JavaScript: ReferenceError: updateLinks is not defined"
What I think causes it. Choose any of the modules and titles. E.g., "Our Lord's Parables" > "The tares - Gennesaret"
If you right-click in the panel and choose "Export Page to browser" nothing will happen (this is a different bug, not the main issue). Change the Title of the page (lower right) to something simple like "test" and on the lower left corner click "Export". This will open up the page in a web browser.
Press Control-U to "uncover" the HTML code used to build the page. You will immediately see that it is non-compliant, invalid HTML that the web browser is nevertheless able to render for the viewer. To see the real problems, submit the generated HTML page to
https://validator.w3.org or check for errors using HTML Tidy.
Web browsers are generally very "forgiving", but I suspect the problem is caused by the invalid tags and the engine putting the <script> data in the body of the html document instead of the head.
I will update my Windows 11 system to the latest version of Windows 25H2, and will also update Bible Analyzer, and see if the problem disappears.