The Designer opens, Vision works, tags go to Good quality, and the project tree still has no Perspective node. The Perspective Components panel and Perspective Property Editor are also missing. A colleague on the same Gateway and the same project sees all of it. The license is fine and the module is installed. The Designer's embedded Chromium engine never started on this workstation. The failure is in the file system under the user profile, not in project configuration.
Fixes That Do Not Touch the Failure
Most engineers try the UI-level fixes first, because the symptom looks like a docking or visibility problem. None of these fixes reach the component that failed.
| Attempted fix | What it changes | Why it fails here |
|---|---|---|
Delete the .layout file in the .ignition folder |
Resets panel docking positions and sizes | Layout only positions panels that a module has registered. If Perspective never registers its workspace, a reset layout has nothing to restore. |
| Check the hidden/preview features setting in the Designer | Shows or hides features behind a flag | Perspective panels are not behind that flag. An unchecked box with nothing hidden confirms that the setting is irrelevant. |
| Update system Java | Changes the Java runtime installed on the machine | The Designer Launcher normally runs the Designer on its own bundled runtime, not the system Java. Check which runtime the launcher uses before you spend time on this. |
| Reinstall the Gateway or pick a different install edition | Replaces server-side modules | The Gateway already delivers Perspective. The startup log reports Mode: Activated, so the module is present and licensed. |
The Java check is a reasonable secondary check, but it is rarely the root cause. The decisive evidence is in the Designer output console.
Startup Log Timing: Where the Sequence Breaks
Open the Designer output console with Ctrl + Shift + C and read the module startup block. The relative timestamps show how far startup gets before it stops:
11:57:11.466 [Designer-Startup] INFO designer.main -- Downloading... [+0]
11:57:11.581 [Designer-Startup] INFO designer.main -- Cleanup... [+115]
11:57:11.590 [Designer-Startup] INFO designer.main -- Initializing UI... [+124]
11:57:14.465 [Designer-Startup] INFO designer.main -- Starting module: Vision [+2999]
11:57:16.755 [Designer-Startup] INFO designer.main -- Starting module: Perspective [+5289]
11:57:18.328 [Designer-Startup] INFO Perspective.Designer -- Starting up Perspective module. Mode: Activated
11:57:18.834 [Designer-Startup] ERROR designer.JXBrowserUtil -- Failed to start Browser Engine with options .....
com.teamdev.jxbrowser.engine.ChromiumBinariesDeliveryException: Failed to extract Chromium binaries into C:\Users\<user>\.ignition\cache\resources\jxbrowser\7.36.3The line that matters is the ERRORMode: Activated. Everything up to that point is healthy:
- The Gateway connection is up.
- The Vision module starts.
- The Perspective module loads and passes license activation.
The failure starts when Perspective asks JXBrowserUtil to launch the Chromium engine. Perspective's Designer workspace renders views in that embedded browser. If the engine does not start, the module does not complete its workspace and panel registration, and the Designer shows no Perspective UI at all.
| Quantity | Healthy value | Observed | Where to read it |
|---|---|---|---|
| Perspective module mode |
Activated (or trial) |
Activated |
Designer console, Perspective.Designer line |
| Browser engine start | No JXBrowserUtil error |
ChromiumBinariesDeliveryException |
Designer console, designer.JXBrowserUtil
|
| Chromium binary folder | Fully populated, readable, executable | Extraction failed | %USERPROFILE%\.ignition\cache\resources\jxbrowser\<version> |
| JxBrowser version expected by the Designer | Matches the folder name | 7.36.3 |
Path in the exception text |
| Gateway-side errors | None related to Perspective | Check | Gateway web page, Status > Logs |
Root Cause: Chromium Binary Delivery to the User Cache
JxBrowser does not run Chromium from the Ignition install directory. At first launch it unpacks a full set of Chromium executables and libraries into a version-numbered folder in the per-user Designer cache. On later launches it checks that folder and starts the Chromium process from it. ChromiumBinariesDeliveryException means this delivery step failed. Either the files could not be written, or they were written and then could not be verified or executed.
The fault stays with one user profile on one machine. That is why a colleague on the same Gateway sees Perspective normally. Their cache folder holds a complete, working set of binaries. Yours holds a partial set, a locked set, or nothing. Related launch failures sometimes surface as a java.io.IOException during Designer startup. The mechanism is the same: the Designer cannot read or write its cache files.
Why the Extraction Fails
The exception reports that extraction failed, not why. On Windows engineering workstations, one of these conditions is almost always behind it:
| Symptom or context | Likely cause | Diagnostic |
|---|---|---|
| The folder exists but has few or zero files | Endpoint protection quarantined or blocked the Chromium executables as the Designer unpacked them | Check the antivirus or EDR quarantine and event history for entries under .ignition\cache
|
| The failure started after a Designer crash or forced close | A leftover Chromium or Designer process still holds files in the cache open | In Task Manager, look for orphaned Chromium or Java processes after closing the Designer |
| A corporate laptop with a redirected or synced profile | The profile folder is redirected to a network share or a cloud-synced location, which blocks executable extraction or locks files during sync | Run echo %USERPROFILE% and check whether .ignition sits on a local disk |
| A non-admin account on a locked-down image | Application control policy blocks execution from user-writable paths | Ask IT whether execution from %USERPROFILE% is restricted |
| A low-space system drive | The extraction ran out of space partway through | Check free space on the drive that holds the profile |
| A Gateway upgrade came before the error | A stale or partial folder from an interrupted earlier download | Compare the folder contents with the same version folder on a working machine |
Procedure A: Purge and Re-Extract the JxBrowser Cache
Try this first. It resolves partial downloads and stale folders, and it tells you whether something on the machine is actively blocking extraction.
- Close every Designer instance and the Designer Launcher.
- In Task Manager, end any leftover Java or Chromium processes that belong to your user account.
- Browse to
C:\Users\<user>\.ignition\cache\resources\. The.ignitionfolder can be hidden, so turn on hidden items in Explorer if needed. - Delete the entire
jxbrowserfolder, not just the7.36.3subfolder. - If endpoint protection quarantined anything in step 3 of the diagnostic table, get an exclusion for
%USERPROFILE%\.ignition\cache\resources\jxbrowserbefore you continue. Otherwise it quarantines the files again on the next extraction. - Start the Designer from the launcher and open the project. The Designer re-downloads and re-extracts the Chromium binaries, so the first launch takes longer than usual.
- Open the console with
Ctrl + Shift + Cand confirm there is noJXBrowserUtilerror after the Perspective startup line.
If the same exception returns right after a clean purge, something on the machine is blocking the write or the execution. Go back to the diagnostic table before you repeat the purge.
Procedure B: Seed the Cache From a Working Workstation
When the automatic extraction keeps failing, copy a known-good binary set from a colleague whose Designer shows Perspective. In practice this is often the fastest fix.
- On the working machine, confirm that it connects to a Gateway running the same Ignition version. The JxBrowser version folder must match the version in your exception text,
7.36.3in this case. - Close the Designer on the working machine so no files are locked during the copy.
- Copy
C:\Users\<colleague>\.ignition\cache\resources\jxbrowser\7.36.3in full. - On the failing machine, close the Designer and launcher, delete any existing
jxbrowser\7.36.3folder, and paste the copied folder intoC:\Users\<user>\.ignition\cache\resources\jxbrowser\. - Right-click the pasted folder, open Properties > Security, and confirm your account has full control. Files copied through a share can inherit restrictive permissions.
- Launch the Designer and check the console.
This workaround skips the download and unpack step. It does not remove a policy that blocks execution. If seeded binaries still fail to start, the blocker is application control or endpoint protection, not delivery.
Verification
- In the Designer console, confirm that
Starting up Perspective module. Mode: Activatedappears with nodesigner.JXBrowserUtilERROR after it. - Confirm that the project tree shows the Perspective node with Views, Page Configuration, and Session Events.
- Open or create a View and confirm that the canvas renders. The canvas is the embedded Chromium surface. A blank or grey canvas means the engine is still failing.
- Confirm that the Perspective Components panel and Perspective Property Editor are available. If they are closed, open them from the View menu.
- Open the Gateway web page, go to Status > Logs, and confirm there are no Perspective-related errors. That separates a clean client-side fix from a Gateway issue that happened at the same time.
- Restart the Designer once more. A second clean start shows that the binaries survive a restart and are not quarantined after the fact.
FAQ
Does deleting the .layout file restore missing Perspective panels in Ignition Designer?
Only if the panels exist but are docked off-screen or closed. If the console shows ChromiumBinariesDeliveryException, the Perspective workspace never registered, and resetting the layout changes nothing. Clear or rebuild .ignition\cache\resources\jxbrowser instead.
Can I copy the jxbrowser folder from another PC?
Yes, as long as the version subfolder matches the one in your error, such as 7.36.3, and both Designers connect to Gateways on the same Ignition version. Copy the whole version folder with the source Designer closed, then check that your account has full control of the pasted files.
Does updating Java fix the JxBrowser Chromium extraction error?
Rarely. The launcher usually runs the Designer on its own bundled runtime. Extraction fails because of file writes, locks, quarantine, or execution policy in the user profile, not because of the Java version.
Does this need Inductive Automation support if the cache rebuild still fails?
Escalate if the exception persists after a clean purge, a seeded cache with correct permissions, and a confirmed antivirus exclusion. Send Inductive Automation support the full Designer console output from Ctrl + Shift + C, the Gateway Status > Logs export, and your Ignition version.