Skip to content
Browsium Documentation Portal Browsium

[Known Issues]

  • Log4j releases 2.0 (only released in beta), through 2.9.1 are not covered by the default settings applied to Java Profiles starting in Browsium Ion 4.9.1.

  • Certain versions of Java are not compatible to be used as the default version or as the JDK as a requirement of project development due to a version detection bug that exists in certain versions of Java. Inconsistent behavior where certain earlier versions may not be properly detected may be observed if the default version is earlier than Java 8u90. In addition, inconsistent behavior may be observed when using Limited Java profiles and the default version is between Java 8u77 and Java 8u90.

  • Due to the forced user notification change in the way Mozilla Firefox handles sideloading of extensions, starting with Firefox 74 Browsium Client requires the use of the ESR to ensure extensions are auto-enabled during installation. Use of the non ESR will prohibit automatic enablement of the Browsium Client Extension.

  • Some users may experience an installation failure, resulting in a loop, with the Microsoft Visual C++ 2017 redistributable (x86 and x64) installers. This is an issue with the prerequisite installation process and not the Browsium Client installer. To resolve this issue, manually install the Visual C++ runtimes prior to installing the Browsium Client.

  • When remediating the Java version with a full Ion profile for a JNLP application loaded from a website, the Ion rule must match the URL of the website hosting the JNLP file, not the URL of Java applet (which might be on another site). If using a Limited Java profile, the rule must match the URL of the Java applet.

  • If 64-bit Java installed, JNLP applications may use 64-bit Java by default, depending on how Java is configured on the system. If 64-bit Java is the default, JNLP remediations to an older version of Java must be to a 64-bit version. This is true for both standalone JNLP applications or JNLP applications launched via a browser. Read Oracle’s guidance for running 32-bit and 64-bit Java side by side for more information.

  • Rules for Limited Java profiles are always evaluated in order from top to bottom after rules for full profiles, regardless of the order displayed in Rules Manager. This is by design. A future release of Ion will always place rules for Limited Java profiles below rules for full profiles in Rules Manager.

  • Projects with a legacy Custom Files-based Java remediation that has not yet been migrated using the Java Version Manager will display System Default in the Java Version field in Profile Properties, even though the project will remediate Java using the entry in Custom Files Manager. It is recommended that all legacy Java remediations (for Java 1.4 and later) be migrated to the new remediation architecture using Java Version Manager.

  • A change to Java introduced by Oracle in Java 7u71 and Java 8u25 and above creates an incompatibility in the Java cache between the current version of Java and the version being remediated by Browsium Ion when invoking Java 6 versions below 6u10 (e.g., Java 6u7, 6u6, 6u5, and 6u4). This may result in Java failing to load in Ion-managed instances of Internet Explorer on Windows 7 or later. To work around this issue, follow the guidance to create a Custom Files entry for Java’s deployment.properties file as detailed in the Ion Knowledge Base.

  • Internet Explorer may crash when attempting to override Java 7 or Java 8 with specific early versions of Java 6 (6u0 - 6u3) due to a bug in Java that was fixed in Java 6u7. Therefore Browsium Ion does not support profiles using Java 6u0, 6u1, 6u2, or 6u3. Contact Browsium Support for more information.

  • When navigating between Ion-managed and unmanaged instances of Internet Explorer, the source webpage may navigate to a blank page or close the tab entirely if the navigation crosses between Internet Explorer zones. This is due to an issue with how Internet Explorer exposes its History to Browser Helper Objects (BHOs).

  • The Browsium Internet Explorer Extension only logs when Protected Mode is disabled for the zone in which the web page loads. This functionality is by design. As a workaround, turn off Protected Mode if you need to capture logs for troubleshooting the Browsium Internet Explorer extension.

  • Pinned Site shortcuts created by Internet Explorer fail to respond to Ion rules and do not open in an Ion-managed window of Internet Explorer. Pinned Site shortcuts should not be used with web sites that require Ion remediation. Internet Shortcuts on the desktop or Start menu will work properly. See the Ion Knowledge Base for information on disabling Pinned Site shortcuts via Group Policy.

  • The address bar in an unmanaged Internet Explorer window may continue to show the URL that was redirected and opened in an Ion-managed window. The content of the web page in the originating window is not affected.

  • On systems with IE10 or IE11 installed, selecting “Auto” for each Profile’s “Examine Web Requests” property will default to the “Always” behavior.**