Designer/Perspective Workstation slow startup on Windows - advisory and recommended hotfix

Recently, a Windows Defender update rolled out that is inadvertently causing dramatically slower launching of the Ignition Designer, Perspective Workstation, and Vision with the Web Browser module installed.
This is confirmed to be related to the packaged Chromium browser extraction due to some change in Windows Defender.

The remediation options are:

  1. Add the directory with Chromium binaries to the whitelist.
  2. Rollback the Windows Defender update.

Our recommendation is to add the binaries directory to the whitelist:

  1. Go to StartSettingsUpdate & SecurityWindows SecurityVirus & threat protection.
  2. Under Virus & threat protection settings, select Manage settings.
  3. Under Exclusions, select Add or remove exclusions.
  4. Select Add an exclusion, and then select the directory with the Chromium binaries. this is within the .ignition directory: ~/.ignition/cache/resources/jxbrowser
59 Likes

Can confirm. this worked for me. Thank you @jcoffman

The recommended fix worked for us. For anyone looking to deploy the recommended fix via group policy, see here:

1 Like

My corporate security team is vehemently against whitelists unless there is no other recourse. Is Inductive pursuing a resolution with MS?
Thanks!

This looks to be an issue with other software also using JxBrowser, not just Ignition:

Looks like the solution is for Inductive to upgrade JxBrowser to v7.42.0

7 Likes

This worked for me! Thanks! @jcoffman

Do these changes have to be made on the gateway, on the computer where designer is installed, or both?

This would have to be done on clients where the designer, workstation, or vision clients which use the Web Browser Component are installed, not the gateway.

2 Likes

Thank you for finding a solution.
At first, the solution didn't work for us. For some reason, our Windows environment variable %USERPROFILE% did not work in the Anti-Virus Exclusions. Our Admins had to use a different wildcard to the same path, and then it worked.

From a cmd prompt, I typed SET to see the environment variables, and it looked correct.

%USERPROFILE%\.ignition\cache\resources\jxbrowser
vs
C:\users\*\.ignition\cache\resources\jxbrowser

For running locally in powershell, this one-liner can add the exclusion for you:

Add-MpPreference -ExclusionPath "C:\Users\*\.ignition\cache\resources\jxbrowser"
6 Likes

Can we expect a fix in 8.1.46?

We are working on a fix at the moment and are targeting the 8.1.46 release. The fix itself is a bit of a moving target at the moment due to some other considerations that have to be made, but its the highest priority ticket currently.

9 Likes

image

I've just added the exclusion to my VM that is running designer - I can now launch a designer session where before i couldn't. However, now the perspective module has disappeared...

The Perspective module not showing up in the Designer indicates a failure on startup. Check the 'Output Console' in the designer after startup and you should see logging indicating that something failed when launching JxBrowser.

The following error showing in the console:

08:11:42.065 [Designer-Startup] INFO Perspective.Designer -- Starting up Perspective module. Mode: Activated
8:11:42.203 ERROR Starting chromium process... [FAILED]
java.io.IOException: Cannot run program "XXX\.ignition\cache\resources\jxbrowser\7.38.2\chromium.exe" (in directory "XXX\.ignition\cache\resources\jxbrowser\7.38.2"): CreateProcess error=1392, The file or directory is corrupted and unreadable

Delete your cache and try again.

If it keeps happening, look at your anti-virus logs.