Script Builder 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

Recent updates to Google Chrome and Microsoft Edge introduced changes to their security mechanisms. In some environments, these changes may prevent the Panaya browser extension used by ScriptBuilder from loading correctly.

To address this issue, upgrade to ScriptBuilder version 26.07.203 or later. Download the latest version from Panaya and install it before proceeding with the steps below.

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

This ensures that the Panaya extension is installed and enabled even when your organization's security policies block browser extensions.

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

For Chrome and Edge version 150 or later -

Organizations that manage browser extensions must configure the Panaya extension using the ExtensionInstallForcelist policy.

Microsoft Edge

Recent updates to Google Chrome and Microsoft Edge (version 150) introduced changes to their security mechanisms. In some environments, these changes may prevent the Panaya browser extension used by ScriptBuilder from loading correctly.

To address this issue, upgrade to ScriptBuilder version 26.07.203 or later. You can download the latest version from Panaya and install it before proceeding with the steps below.

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 Panaya extension to the ExtensionInstallForcelist in the Edge registry.

This ensures that the Panaya extension is installed and enabled even when extension installation is restricted by your organization's security policies.

For Chrome and Edge version 150 or later -

Organizations that manage browser extensions must configure the Panaya extension using the ExtensionInstallForcelist policy.

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 -

After the policy is applied and the extension is installed, restart the browser and launch ScriptBuilder again.

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.