--- title: "ScriptBuilder Extension Policy – Troubleshooting Guide" slug: "script-builder-browser-issue-troubleshooting-guide" updated: 2026-08-12T11:15:15Z published: 2026-08-12T11:15:15Z canonical: "success.panaya.com/script-builder-browser-issue-troubleshooting-guide" --- > ## Documentation Index > Fetch the complete documentation index at: https://success.panaya.com/llms.txt > Use this file to discover all available pages before exploring further. # ScriptBuilder Extension Policy – Troubleshooting Guide This article explains how to resolve the following issues - - ScriptBuilder does not launch. - A message indicates that the required extension is not installed. - Test automation execution fails unexpectedly. --- ## Google Chrome ### Before You Begin If the Panaya Chrome extension is already installed, remove it from Google Chrome before continuing. ### Verify Your Chrome Policy If your organization's ExtensionInstallBlocklist policy is configured as "*", your IT administrator must add the Panaya extension to the ExtensionInstallForcelist policy in the Chrome registry. To verify whether this policy is configured: 1. Open Google Chrome. 2. Navigate to: chrome://policy 3. Locate the ExtensionInstallBlocklist policy. If its value is "*", ask your IT administrator to add the following entry to the ExtensionInstallForcelist: bhbpajbdlmemfiimcpbemelcoijoiikb;[https://clients2.google.com/service/update2/crx](https://clients2.google.com/service/update2/crx) This ensures that the Panaya extension is installed and enabled even when your organization's security policies block browser extensions. > [!CAUTION] > Important! > > The extension ID and update URL must be added as a single entry in the ExtensionInstallForcelist policy, exactly as shown below. Do not add them as separate entries. > > bhbpajbdlmemfiimcpbemelcoijoiikb;https://clients2.google.com/service/update2/crx > [!CAUTION] > For Chrome and Edge version 150 or later - > > [Organizations that manage browser extensions must configure the Panaya extension using the ExtensionInstallForcelist policy](/v1/docs/script-builder-browser-issue-troubleshooting-guide#versions-150-or-later). --- ## Microsoft Edge ### Before You Begin If the Panaya Edge extension is already installed, remove it from Microsoft Edge before continuing. ### Verify Your Edge Policy If your organization's ExtensionInstallBlocklist policy is configured as "*", your IT administrator must add the Panaya extension to the ExtensionInstallForcelist policy in Microsoft Edge. To verify whether this policy is configured: 1. Open Microsoft Edge. 2. Navigate to: edge://policy 3. Locate the ExtensionInstallBlocklist policy. If its value is "*", ask your IT administrator to add the following entry to the ExtensionInstallForcelist: bbejbghccebkkldiblfnmaoojikndnib This ensures that the Panaya extension is installed and enabled even when extension installation is restricted by your organization's security policies. > [!CAUTION] > For Chrome and Edge version 150 or later - > > [Organizations that manage browser extensions must configure the Panaya extension using the ExtensionInstallForcelist policy](/v1/docs/script-builder-browser-issue-troubleshooting-guide#versions-150-or-later). --- ## ExtensionInstallForcelist Policy If you are running Chrome or Microsoft Edge version 150 or later and your browser extensions are managed by your organization's IT policies, they must be force-installed through the browser registry policies. Ask your IT administrator to add the Panaya extension IDs to the ExtensionInstallForcelist - | Browser | Extension ID | | --- | --- | | Microsoft Edge | bbejbghccebkkldiblfnmaoojikndnib | | Google Chrome | bhbpajbdlmemfiimcpbemelcoijoiikb;https://clients2.google.com/service/update2/crx | After the policy is applied and the extension is installed, restart the browser and launch ScriptBuilder again. > [!NOTE] > **Tip!** If the extension was previously installed manually, it can be removed after verifying that the policy-installed extension is working correctly. This may improve browser startup time.