# V8.3.1 JXBrowserUtil - Failed to extract Chromium binaries **URL:** \ **Category:** Ignition\ **Tags:** vision, ignition83\ **Created:** [December 3, 2025, 3:51pm UTC](https://forum.inductiveautomation.com/t/v8-3-1-jxbrowserutil-failed-to-extract-chromium-binaries/112596 "2025-12-03T15:51:23Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![cmaynes](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmaynes/32/6852_2.png) [@cmaynes](https://forum.inductiveautomation.com/u/cmaynes)\ **Post date:** [December 3, 2025, 3:51pm UTC](https://forum.inductiveautomation.com/t/v8-3-1-jxbrowserutil-failed-to-extract-chromium-binaries/112596/1 "2025-12-03T15:51:23Z")
Version: v8.3.1 GUI Module: Vision We just migrated from v7.9.21 to v8.1.48 to v8.3.1 on our DEV server and then backed that up and restored it to our QAS server and started seeing this error. There is no web browser module installed. I think we used to have it installed at some point, but it is no longer installed on either of these servers. Vision client seems to run fine, but this adds noise to the logs and I am not sure if it will cause other issues at some point. ```python 10:36:19.865 [ProjectDownloader] ERROR designer.JXBrowserUtil -- Failed to start Browser Engine with options com.teamdev.jxbrowser.engine.EngineOptions: autoplayEnabled: false chromiumDir: C:\Users\autbasic\.ignition\cache\resources\jxbrowser\8.12.1 chromiumSwitches: [] diskCacheSize: fileAccessFromFilesAllowed: false isGpuDisabled: false isIncognitoEnabled:true language:en-us passwordStore: remoteDebugginPort: 9222 renderingMode: OFF_SCREEN isSandboxDisabled: false secureOriginWhitelist: [] isTouchMenuEnabled: false userAgent: userDataDir:C:\Temp\JxBrowser-UserData-d1c1ec44-867b-47e5-a41a-85b973531355 webSecurityDisabled: false . com.teamdev.jxbrowser.engine.ChromiumBinariesDeliveryException: Failed to extract Chromium binaries into C:\Users\autbasic\.ignition\cache\resources\jxbrowser\8.12.1 at com.teamdev.jxbrowser.internal.OfficialDelivery.deliverTo(OfficialDelivery.java:56) at com.teamdev.jxbrowser.engine.ChromiumBinaries.lambda$deliverTo$0(ChromiumBinaries.java:166) at com.teamdev.jxbrowser.engine.ChromiumBinaries.trySynchronized(ChromiumBinaries.java:196) at com.teamdev.jxbrowser.engine.ChromiumBinaries.deliverTo(ChromiumBinaries.java:156) at com.teamdev.jxbrowser.engine.ChromiumBinaries.deliverTo(ChromiumBinaries.java:109) at com.teamdev.jxbrowser.engine.internal.EngineImpl.newInstance(EngineImpl.java:153) at com.teamdev.jxbrowser.engine.Engine.newInstance(Engine.java:163) at com.inductiveautomation.ignition.client.util.JxBrowserUtil.lambda$getOrCreateEngine$2(JxBrowserUtil.java:352) at com.inductiveautomation.ignition.client.util.JxBrowserUtil.runResourceLockedAction(JxBrowserUtil.java:567) at com.inductiveautomation.ignition.client.util.JxBrowserUtil.getOrCreateEngine(JxBrowserUtil.java:352) at com.inductiveautomation.ignition.client.util.JxBrowserUtil.getOrCreateEngine(JxBrowserUtil.java:431) at com.inductiveautomation.webbrowser.BrowserInstanceManager.startup(BrowserInstanceManager.java:36) at com.inductiveautomation.factorypmi.application.FPMIApp.createApp(FPMIApp.java:336) at com.inductiveautomation.factorypmi.application.runtime.ClientPanel.startupApp(ClientPanel.java:893) at com.inductiveautomation.factorypmi.application.runtime.ClientPanel.startupAppSafe(ClientPanel.java:844) at com.inductiveautomation.factorypmi.application.runtime.ClientPanel.onProjectDownloadFinished(ClientPanel.java:853) at com.inductiveautomation.factorypmi.application.runtime.DownloadProjectPane.lambda$new$0(DownloadProjectPane.java:73) at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(Unknown Source) at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(Unknown Source) at java.base/java.util.concurrent.CompletableFuture.postComplete(Unknown Source) at java.base/java.util.concurrent.CompletableFuture.complete(Unknown Source) at com.inductiveautomation.factorypmi.application.runtime.DownloadProjectPane$DownloadProject.run(DownloadProjectPane.java:112) at com.inductiveautomation.ignition.client.launch.AbstractStepRunner.run(AbstractStepRunner.java:33) at java.base/java.lang.Thread.run(Unknown Source) Caused by: java.io.FileNotFoundException: chromium-win32.7z at com.teamdev.jxbrowser.internal.OfficialDelivery.deliverTo(OfficialDelivery.java:54) ... 23 common frames omitted 10:36:19.865 [ProjectDownloader] ERROR WebBrowser -- BrowserEngine was not initialized. Web Browser Component can not start! 10:36:20.130 [AWT-EventQueue-0] INFO vision.App -- Starting Up... 10:36:26.100 [EDT-Watchdog-1] INFO edt-watchdog -- Non-responsive UI thread detected. Stack saved at 'C:\Users\autbasic\.ignition\cache\gwqaignition.myjmawireless.com_443\C2\NonResponsiveEdt-2025-12-03_103626.json' ``` ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [December 3, 2025, 3:57pm UTC](https://forum.inductiveautomation.com/t/v8-3-1-jxbrowserutil-failed-to-extract-chromium-binaries/112596/2 "2025-12-03T15:57:57Z")
The web browser module has been rolled into the Vision module and a separate license is no longer needed. You are seeing the "graceful" fallback that allows Vision to run even on platforms where JxBrowser is unsupported. Prior to this change, any user that needed Vision on platforms (RPi in particular) where JxBrowser is unsupported would have to entirely exclude the Web Browser module from the gateway. Since this change, the Web Browser component can be used conditionally even when troublesome client platforms are present. You can simply ignore this client-side-only log message. ---
**Author:** ![cmaynes](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmaynes/32/6852_2.png) [@cmaynes](https://forum.inductiveautomation.com/u/cmaynes)\ **Post date:** [December 3, 2025, 7:24pm UTC](https://forum.inductiveautomation.com/t/v8-3-1-jxbrowserutil-failed-to-extract-chromium-binaries/112596/3 "2025-12-03T19:24:36Z")
@pturmel, thanks for the reply. I am running these vision clients on Windows 10, which I would assume is supported? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [December 3, 2025, 7:27pm UTC](https://forum.inductiveautomation.com/t/v8-3-1-jxbrowserutil-failed-to-extract-chromium-binaries/112596/4 "2025-12-03T19:27:30Z")
X86 or ARM? If the latter, no. IIRC. If the former, look for AV interference. (Try deleting caches and starting again.) But: > [@cmaynes](#): > > `Caused by: java.io.FileNotFoundException: chromium-win32.7z` I believe IA has dropped 32-bit support. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [December 3, 2025, 7:29pm UTC](https://forum.inductiveautomation.com/t/v8-3-1-jxbrowserutil-failed-to-extract-chromium-binaries/112596/5 "2025-12-03T19:29:48Z")
> [@cmaynes](#): > > `chromium-win32.7z` We don't bundle/ship the 32-bit Windows JxBrowser. It's surprising you can even get Windows 10 to report 32 bit - I thought all Windows past 7 was 64-bit only... ---
**Author:** ![cmaynes](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmaynes/32/6852_2.png) [@cmaynes](https://forum.inductiveautomation.com/u/cmaynes)\ **Post date:** [December 3, 2025, 7:31pm UTC](https://forum.inductiveautomation.com/t/v8-3-1-jxbrowserutil-failed-to-extract-chromium-binaries/112596/6 "2025-12-03T19:31:26Z")
It is Windows x86\_64. Not sure why it seems to be trying to use a 32-bit version. I will try deleting the cache as @pturmel mentioned. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [December 3, 2025, 7:34pm UTC](https://forum.inductiveautomation.com/t/v8-3-1-jxbrowserutil-failed-to-extract-chromium-binaries/112596/7 "2025-12-03T19:34:48Z")
Maybe some leftover Windows Compatibility mode settings trying to "help" java.exe? Consider not using Windows? _Cough_ ---
**Author:** ![cmaynes](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmaynes/32/6852_2.png) [@cmaynes](https://forum.inductiveautomation.com/u/cmaynes)\ **Post date:** [December 3, 2025, 7:41pm UTC](https://forum.inductiveautomation.com/t/v8-3-1-jxbrowserutil-failed-to-extract-chromium-binaries/112596/8 "2025-12-03T19:41:17Z")
Hahaha...not use Windows, that is a good one! 'Fraid that is next to impossible thanks to equipment driver support from vendors ☹ ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [December 3, 2025, 7:43pm UTC](https://forum.inductiveautomation.com/t/v8-3-1-jxbrowserutil-failed-to-extract-chromium-binaries/112596/9 "2025-12-03T19:43:13Z")
> [@cmaynes](#): > > equipment driver support I run Windows in VMs for engineering and maintenance tasks. I strongly recommend **not** using Windows on production systems, including plant floor HMIs. Adherence among my clients is mixed, but growing. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [December 3, 2025, 8:15pm UTC](https://forum.inductiveautomation.com/t/v8-3-1-jxbrowserutil-failed-to-extract-chromium-binaries/112596/10 "2025-12-03T20:15:01Z")
It looks like JxB automatically attempts to extract _both_ win32 and win64 libs, not really sure why. Potentially, you could try adding a system property to the Vision client launcher; I think the syntax would be `-Dignition.chromium.switch.jxbrowser.chromium.binaries.verification.disabled` Like this, but a different switch: > [@Perspective Not Showing](https://forum.inductiveautomation.com/t/perspective-not-showing/109959/17): > > Can you try adding -Dignition.chromium.switch.do-not-de-elevate as a jvm argument as well and relaunching one more time? This would be separated from the other jvm argument with a ; ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [December 4, 2025, 6:24am UTC](https://forum.inductiveautomation.com/t/v8-3-1-jxbrowserutil-failed-to-extract-chromium-binaries/112596/11 "2025-12-04T06:24:26Z")
I’m about to dump windows on my laptop at work, gotta run every vendor software in its own vm, so I’m taking the host to Linux and it’s gained huge speed on the VMs. Also I get easy command line tools natively. > [@pturmel](#): > > X86 or ARM? If the latter, no. IIRC. Is vision broken for this on macOS as a result? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [December 4, 2025, 1:20pm UTC](https://forum.inductiveautomation.com/t/v8-3-1-jxbrowserutil-failed-to-extract-chromium-binaries/112596/12 "2025-12-04T13:20:17Z")
> [@David\_Stone](#): > > on macOS Don't know. I have no Apple hardware at all. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [December 4, 2025, 2:18pm UTC](https://forum.inductiveautomation.com/t/v8-3-1-jxbrowserutil-failed-to-extract-chromium-binaries/112596/13 "2025-12-04T14:18:28Z")
No, we ship JxBrowser for Mac. The only thing to watch out for is we dropped Intel Mac support with 8.3, so make sure you’re getting one of the Apple Silicon models. They’re insanely fast.