Legacy Browser Support 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.

    Legacy Browser Support version history

    Here's a list of the new features with each LBS release:


    1. Always move IE windows forward when launched from LBS.


    1. Added "Use IE Enterprise Mode site list if present" policy.
    2. Added "Show transition message for some time" policy.


    1. Fixed a bug where URLs could be cut in half when transitioning to IE.


    1. Disabled the extension in Incognito mode.
    2. Respect IE setting for opening URLs in tabs or windows.
    3. Support EPM mode in modern IE versions.


    1. Removed a reference to the NPAPI plugin, which would cause issues with Chrome 45+.


    1. Added "Keep last Chrome tab open" policy.
    2. Fixed a bug where more precise entry in the list of URLs to open in any browser will be ignored if a match in the list to transition is found.
    3. Support for environment variables in the policies. For example, this is now a valid entry: %PROFILE%/AppData/Local/Google/Application/chrome.exe.


    1. Fixed a bug causing the extension to hang Chrome if it has a problem loading its components.
    2. Introduced a beta channel for testing future LBS versions.


    1. Removed deprecated NPAPI plugin from the extension.
    2. Added policy schema manifest as required by newer Chrome versions.
    3. Detect browsers installed works for a single user instead of system-wide as it used to be.
  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 article helpful?
How can we improve it?