Knowledge Base
Browse Docs
  • Introduction
    1. DefensX
    2. DNS & Web Filtering
    3. Zero Trust Files
    4. Zero Trust Credentials
    5. ADWare Protection
    6. Remote Browser Isolation
    7. Secure Browser Extension
    8. Secure Mobile Browser
  • Management
    1. Role-Based Access Control
  • Deployment
    1. Deployment via RMM
    2. Operating System Agent
    3. Deployment via GPO
    4. Deployment via Intune
    5. VDI and Terminal Servers
    6. Windows Manual Deployment
    7. Mac MDM Deployment
    8. Mac Manual Deployment
    9. Network Deployment
    10. Secure Mobile Browser
    11. Bypass Option
    12. AI Protections
    13. SaaS Restrictions
    14. Bookmark Manager
  • Secure Access (ZTNA)
    1. Configuration
  • Integrations
    1. Azure AD
    2. Identity Providers
    3. SIEM
  • Policy Management
    1. Configuring Policies
    2. Configuring Consents
  • Questions & Answers
    1. Licensing
    2. Incognito Mode
    3. Onboarding
    4. Active Directory
    5. Group Synchronization
    6. Agent
    7. Conflicting Softwares
    8. Reporting
    9. Virtual Desktops
    10. Using the Backend
    11. DNS & Web Filtering
  • Training Videos
    1. Onboarding Videos
    2. Attack Scenarios
    3. MSP Admin Training Series
  • MSP Automation
    1. Overview
    2. External Notifications
    3. Integrations
    4. Partner API
ONLINE DOCUMENTATION

Browser Extensions Missing After DefensX Installation

In this document
  • Problem
  • Root Cause
  • Solution
  • Impact

Problem

After installing the DefensX software, some browser extensions that were previously installed via Group Policy at the user level may disappear from Chrome or Edge.

This behavior is due to how DefensX configures browser policies to enforce security features.

Root Cause

DefensX installs its browser extension and required policies at the computer level, not the user level. This ensures consistent security features across all user profiles.

The browser extension installation is controlled through the ExtensionInstallForcelist policy key. However, Chrome and Edge cannot merge this policy if it exists at both the user and computer levels. When this happens, the browser may show a policy conflict.

You can confirm this by navigating to:

  • chrome://policy (in Chrome)

  • edge://policy (in Edge)

extension conflict

Look for the ExtensionInstallForcelist key. If the Status column shows a warning like Conflict, this confirms the issue.

Solution

To resolve the conflict, you need to move the affected extension’s policy from the user level to the computer level:

  • Open the Group Policy Editor (gpedit.msc)

  • Locate the existing user-level policy: User Configuration > Administrative Templates > Google Chrome > Extensions > Configure the list of force-installed apps and extensions

  • Copy the values from this policy.

Then go to:

  • Computer Configuration > Administrative Templates > Google Chrome > Extensions > Configure the list of force-installed apps and extensions

  • Paste the copied values into the computer-level setting.

  • Set the user-level policy to "Not configured".

Ensure that only the computer-level policy sets the ExtensionInstallForcelist key, and that it includes all required extension IDs, including the ones that were disappearing.

extension conflict gpo
Tip
Configuring browser policies at the computer level is not unique to DefensX, it is a common requirement for software solutions that use browser extensions. Managing all browser-related policies centrally at the computer level helps prevent similar issues with other software in the future.

Impact

As of Q2 2025, this issue has been reported in only 0.02% of DefensX installations, primarily involving password manager extensions like Keeper Security or Bitwarden, when installed via user-level GPOs.

www.defensx.com
Secure Industries, Inc 101 Avenue of The Americas, Floor 9 New York, NY 10013