Skip to content
Browsium Documentation Portal Browsium

[Known Issues]

  • Due to a bug in Microsoft Edge (Chromium) 80, the browser extension will not be automatically enabled. To force enablement, the extension will have to be installed into Edge’s extension install forcelist. Once this bug is addressed by Microsoft the extension will be automatically enabled without this additional step.

  • 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.

  • Proton Manager may throw an exception when attempting to export CSV files with large number of rows. The CSV export feature was designed for smaller reporting uses. For larger data exports, query the Proton database directly using alternate reporting tools.

  • The name of the Proton database cannot have a ”.” in the string (e.g., naming the database “Proton4.4”). Completing set-up with such a string will result in failure to properly set up the Proton database.

  • Java usage detection may detect the incorrect version if the web site requesting the Java applet is only open briefly, either because the tab was closed or because there was a navigation to another web site.

  • Java usage detection may detect the incorrect version if there are navigations to multiple web sites requesting Java applets in a tab and one of the web sites uses a non-default version of Java. For example, if there is a navigation to site A for which Ion is remediating a non-default version of Java followed by a navigation to site B for which the default version of Java is used, then Proton may detect that site B used the non-default version of Java that was used by site A.

  • As part of creating an inventory of ActiveX components installed on a machine, Proton will attempt to load the ActiveX components to test the safety flags. If Proton cannot load the ActiveX component for any reason (e.g., the component has dependencies not loaded by Proton), Proton will not be able to determine the safety flags reported by the component’s module. Proton will still determine the safety flags reported in the registry for the component.

  • Java version detection during browsing activity may not be reported until the browser tab is closed because of the way Java interacts with the Internet Explorer DOM.

  • The version number of the Browsium Client extensions for Edge (Legacy and Chromium) Chrome and Firefox may not be an exact match with the version number of the Browsium Client and Internet Explorer extension. This is by design as the version and publishing mechanisms are different for each component. Consult the Proton Knowledge Base for a current list of the version numbers for each Proton component.

  • Running the Browsium Client on virtual machines that have been cloned may result in a duplicate machine SID causing Proton to only see inventory and activity data from one of the clients. It’s also possible that the client connected to the Proton Server may alternate, resulting in unpredictable inventory and activity data.

  • Proton does not provide an easy way to recover lost administrator passwords. If you forget your Proton administrator account password, contact Browsium Support for assistance. Direct access to the SQL database can be used to reset the accounts so you can re-create the first, auto-approved administrator account.

  • The bar chart on the Activity -> Web Application Usage page shows a bar for each application displayed in the table. When a large page size (e.g. 100 or 1000) is selected, the bar chart may become unreadable.

  • When you make a rule change, you can see the new or updated rule in the Manager, but the changes to web application mappings are not enacted immediately. Rule mapping is done in the background on the Proton database server. The length of time that takes varies depending on the size of the database, the change made, how many URLs the rule matches, the speed and load on the database server, and what other background processing is occurring.