Legacy Browser Support extension for Windows

2) Install the LBS Chrome Extension

Configure Chrome to force install the Legacy Browser Support extension for this early group. Set or update the ExtensionInstallForcelist policy to include the id: heildphpnddilhkemkielfhnkaagiabh;https://clients2.google.com/service/update2/crx.

Use your software provisioning tool to install the LBS native host add-on from the provided MSI. There is a 32-bit only version for older systems as well as 64-bit version which supports both the 32 and 64-bit Windows versions.

The Chrome extension will not function properly without this package!
  1. Download the latest version of Legacy Browser Support MSI installer for Windows 32-bit or Windows 64-bit. For LBS version history, see the Legacy Browser Support release notes.

  2. Push it through your preferred software provisioning tool.

  3. The native host add-on requires the Chrome extension to work properly. It will not work until Chrome loads the extension and reads the policy from the registry.

Important! If the legacy browser is closing on pages you don't want it to, you may need to configure the 'Hosts that should not trigger a transition in either browser' policy described here.

Please refer to Microsoft’s documentation for instructions on how to configure Windows Group Policies (GPO).

What it does: When an employee types or clicks on a URL that requires a legacy browser in Chrome, the page will automatically launch via an alternate browser.

Note that even if Chrome is the default browser, if a specified URL is clicked in a non-browser app (for example, Microsoft Outlook®), the extension will launch the site in the alternate browser of choice. Optionally, you can also make Chrome the default browser for this test group of users.


Was this helpful?
How can we improve it?