Release notes and version history

LiteView2 1.0.1.0 Maintenance release

Released 9 October 2026 · replaces 1.0.0.0

LiteView2 1.0.1.0 makes synchronous JavaScript calls predictable across WebView2's event model. It fixes several stability issues in synchronous calls, and its installer updates an existing installation in one step. The COM interface is unchanged.

Script execution and events

• Synchronous calls inside notification events. In the registered control, these ten events are now raised after WebView2 has finished its own callback: NavigationCompleted, NavigationCompletedHex, SourceChanged, ContentLoading, ContentLoadingHex, DOMContentLoaded, DocumentTitleChanged, HistoryChanged, WebMessageReceived and DevToolsProtocolEventReceived. Inside their handlers, synchronous calls such as ExecuteScript, ExecuteScriptWithResult, the DOM helpers and CallDevToolsProtocolMethod now return their results. In 1.0.0.0 they waited for the timeout.
• Immediate, descriptive failure where a synchronous call cannot work. Some places are still inside a WebView2 callback, so WebView2 cannot deliver a result until your code returns: WebViewReady, NavigationStarting and the other events that let you cancel or answer, and any VBA method that page script is calling through a host object. Synchronous calls in those places now fail at once with error 0x80040203 (Err.Number -2147220989). Nothing is started, and the message names the call to use instead, for example ExecuteScriptAsync. Before, the call waited for the timeout (about 30 seconds) and then failed.
• SynchronousTimeOut now also limits ExecuteScript, ExecuteScriptWithResult and the helpers built on them.
• ExecuteScriptWithResult reports a timeout in exceptionMessage and sets LastErrorCode.
• DevTools. DevToolsProtocolEventReceived is raised just after its WebView2 callback, so a CallDevToolsProtocolMethod inside the handler returns its result. Events still queued when you unsubscribe are not raised.

Stability

• A result that arrived after a synchronous call had timed out could corrupt memory or close the host application (ExecuteScriptWithResult, GetCookies, GetBrowserExtensionList, CallDevToolsProtocolMethod and others). Fixed.
• ExecuteScript no longer leaks a string on every call.
• Queued notification events are no longer delivered inside another event handler's message loop (DoEvents, MsgBox), where they could re-enter your code.

Installer

• One-step update. Running the 1.0.1.0 Setup over LiteView2 1.0.0.0 removes 1.0.0.0 with its own uninstaller and installs 1.0.1.0 in the same run. Your license, trial state, settings and browsing data are kept.
• Manual installations. Setup can safely migrate earlier customer releases that were installed manually with regsvr32. It backs up that registration first and restores it if the installation does not finish. A registration Setup cannot verify is left untouched, and Setup explains what to do.
• Recovery from leftover registrations. Incomplete per-user registry entries that an earlier LiteView2 left behind, and the entry that regsvr32 /u leaves behind, no longer block installation. They are backed up and removed.
• Clearer screens. Repair and Update choices, a readable license page, messages that say what happened and what to do, a light and a dark appearance, and a link to the Setup log on every stop. Setup stays responsive while it works.

Compatibility

Unchanged

• The COM interface: type library LiteView2 1.0 Type Library (version 1.0), all GUIDs, ProgIDs, DISPIDs, method signatures and enums. Existing VBA and VB6 projects keep their reference; you do not need to re-add it.
• Registered and Reg-Free deployment. Both the 32-bit and the 64-bit control are included.
• System requirements: Windows 10 or 11 (64-bit) for Setup, and the Microsoft Edge WebView2 Runtime.

Changed behavior you may notice

• A synchronous call inside WebViewReady or NavigationStarting, or inside a VBA method called from page script, now fails immediately and does nothing. In 1.0.0.0 such a call timed out after about 30 seconds, but its effect (the script, the navigation, the registration) often still happened afterwards. Code that ignored that error and relied on the late effect must change: use ExecuteScriptAsync there; or move the work to NavigationCompleted or DOMContentLoaded; or register page code with AddScriptToExecuteOnDocumentCreated / EnableLvFacade in Form_Load, before the browser is ready.
• The ten notification events listed above arrive slightly later than before, after WebView2's callback. Among themselves their order is unchanged, but a callback-type event or a host call can now run before a notification that was raised earlier.
• While a DoEvents or MsgBox loop runs inside a callback-type event or a host-object method, queued notifications are delivered after that handler returns, not during the loop.
• ControlVersion returns "1.0.1.0". In Apps & features the product is listed as "LiteView2".

Private Sub LiteView2Ctrl1_WebViewReady()
    ' Set up and navigate here. Calls that wait for the page fail here.
    LiteView2Ctrl1.SetLocalContentRoot CurrentProject.Path
    LiteView2Ctrl1.Navigate "https://lv2.example/index.html"
End Sub

Private Sub LiteView2Ctrl1_NavigationCompleted(ByVal url As String, ByVal success As Boolean)
    ' In 1.0.1.0 a synchronous call returns its result here.
    If success Then Debug.Print LiteView2Ctrl1.ExecuteScript("document.title")
End Sub

Known issues

• Click, DblClick, KeyPress, MouseEnter and MouseLeave are not raised while a page is displayed. Workaround: listen for the event in page script, send it with chrome.webview.postMessage, and handle it in WebMessageReceived.
• BrowserGotFocus and BrowserLostFocus are not raised. Workaround: listen for focus and blur in page script and send them with chrome.webview.postMessage.
• ClearBrowsingDataInTimeRange returns without an error but clears nothing. Workaround: use ClearBrowsingData, which clears the chosen kinds of data for all time, or ClearCookies.
• NavigateSync, NavigateToStringSync and NavigateWithWebResourceRequestSync can return when another navigation completes, before their own page has loaded, if a navigation is already in progress. Use Navigate and handle NavigationCompleted when navigations can overlap.

Checksums (SHA-256)

To check a download in PowerShell: Get-FileHash .\liteview2-setup.zip, then compare the result with this table.

Updating LiteView2

1. Close Microsoft Access, Excel, Word and the VB6 IDE.
2. Run the latest LiteView2 Setup (liteview2-setup.zip from the download page).

Setup updates the version you have in a single run:

• Installed with an earlier LiteView2 Setup? Setup updates it in place.
• Installed manually with regsvr32? Setup can safely migrate earlier customer releases that were installed manually with regsvr32. Your old files are left where they are and are no longer used.

In both cases your license, trial state, settings and browsing data are kept, and your Access, Excel and VB6 projects keep their LiteView2 reference. Your code and your license key stay as they are.

Reg-Free (side-by-side) deployments: replace LiteView2_x64.ocx and LiteView2_x86.ocx next to your database or workbook with the files from the latest Reg-Free package (liteview2-regfree.zip). Keep the same file names.

If Setup stops with a message, follow the message: it says what happened and what to do, and Setup changes nothing it cannot undo. If you need help, send us the Setup log; the message shows where it is.

Before you update, read Changed behavior if your code calls ExecuteScript (or another synchronous method) inside WebViewReady, NavigationStarting or a VBA method called from page script.

Product updates

Where to get updates. The current version is always on the LiteView2 download page, and every release is listed on this page with its notes and checksums. The latest Setup updates the version you have.

How you hear about them. Each release is published on this page, and licensed customers are told about it by e-mail.

What your license includes. Your license is permanent. Each license includes one year of updates and support from the date of purchase; after that, the optional Annual Support plan ($79/year) keeps you receiving new releases, bug fixes and e-mail support. A licensed version you have installed never expires: if you do not renew, it keeps working with no restrictions. See pricing and plans.

LiteView2 1.0.0.0

First commercial release · March 2026

The first public release of LiteView2, the WebView2 ActiveX control for Access, Excel VBA and VB6, in Registered and Reg-Free modes, with the 30-day trial. Later 1.0.0.0 builds added the installer and the separate Reg-Free download package (September 2026).

Earlier versions are available from support on request.