You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Troubleshoot Self-Hosted Extension Deployment Group Policy Issues
3
-
description: Learn how to resolve deployment issues for self-hosted extensions in Microsoft Edge when using group policies like ExtensionInstallForcelist or ExtensionSettings.
3
+
description: Learn how to resolve deployment issues for self-hosted extensions in Microsoft Edge when you use Group Policy policies.
4
4
ms.custom: 'sap:Web Platform and Development\Connectivity and Navigation: TCP, HTTP, TLS, DNS, Proxies, Downloads'
5
5
ms.reviewer: dili, Johnny.Xu, v-shaywood
6
6
ms.date: 01/12/2026
7
7
---
8
8
9
-
# Failure to deploy self-hosted extension via group policy
9
+
# Self-hosted extension deployment fails in Group Policy
10
10
11
-
When you attempt to deploy a self-hosted extension through group policy, you might encounter an issue where the extension doesn't appear for the target user. This article provides guidance for identifying and resolving the cause of this problem, enabling you to successfully deploy your extension.
11
+
When you try to deploy a self-hosted extension through Group Policy, you experience an problem in which the extension doesn't appear for the target user. This article provides guidance for how to identify and resolve the cause of this problem so that you can successfully deploy the extension.
12
12
13
13
## Symptoms
14
14
15
-
When you deploy a browser extension to Microsoft Edge by using the group policy[ExtensionInstallForcelist](/DeployEdge/microsoft-edge-browser-policies/extensioninstallforcelist) or [ExtensionSettings](/DeployEdge/microsoft-edge-browser-policies/extensionsettings), the deployment fails and the extension doesn't appear on the `edge://extensions` page for the target users.
15
+
When you deploy a browser extension to Microsoft Edge by using the Group Policy[ExtensionInstallForcelist](/DeployEdge/microsoft-edge-browser-policies/extensioninstallforcelist) or [ExtensionSettings](/DeployEdge/microsoft-edge-browser-policies/extensionsettings), the deployment fails, and the extension doesn't appear on the `edge://extensions` page for the target users.
16
16
17
-
However, if you manually drag the same extension package (`.crx` file) onto the `edge://extensions` page with[Developer mode](/microsoft-edge/extensions/getting-started/extension-sideloading#locally-installing-and-running-an-extension) enabled, the extension installs successfully.
17
+
However, if you manually drag the same extension package (`.crx` file) onto the `edge://extensions` page by having[Developer mode](/microsoft-edge/extensions/getting-started/extension-sideloading#locally-installing-and-running-an-extension) enabled, the extension installs successfully.
18
18
19
-
## Cause: Incorrect group policy configuration
19
+
## Cause 1: Incorrect group policy configuration
20
20
21
-
You incorrectly configured the group policy**ExtensionInstallForcelist** or **ExtensionSettings**.
21
+
This problem occurs because the Group Policy**ExtensionInstallForcelist** or **ExtensionSettings** policy is configured incorrectly.
22
22
23
-
### Solution: Verify and correct the group policy configuration
23
+
### Solution: Verify and correct the Group Policy configuration
24
24
25
-
Verify and correct the extension group policy configuration by using the following documentation:
25
+
Verify and correct the Group Policy extension configuration by using the following documentation:
## Cause: Incorrect Content-Type header for the .crx file
30
+
## Cause 2: Incorrect Content-Type header for the .crx file
31
31
32
-
When you host the extension on an internal HTTP or HTTPS server and the server doesn't return the correct **Content-Type** header for the `.crx` file, the extension deployment fails.
32
+
When you host the extension on an internal HTTP or HTTPS server, and the server doesn't return the correct **Content-Type** header for the `.crx` file, the extension deployment fails.
33
33
34
-
If the `.crx` file isn't served with the header `Content-Type: application/x-chrome-extension`, Microsoft Edge or any other Chromium-based browser won't treat the file as an installable extension package when it's downloaded as part of the group policy installation flow.
34
+
If the `.crx` file isn't served by using the header,`Content-Type: application/x-chrome-extension`, Microsoft Edge or any other Chromium-based browser won't treat the file as an installable extension package when it's downloaded as part of the Group Policy installation flow.
35
35
36
-
As a result, the policy is processed, but the browser silently fails to install the extension.
36
+
As a result, the policy is processed, but the browser doesn't silently install the extension.
37
37
38
-
### Solution: Configure the web server to return the correct Content-Type
38
+
### Solution: Configure the web server to return the correct content type
39
39
40
40
Configure the web server to return the correct `Content-Type` for `.crx` files. The HTTP response for the extension package must include the following header:
41
41
42
42
```http
43
43
Content-Type: application/x-chrome-extension
44
44
```
45
45
46
-
After you configure this header, Microsoft Edge recognizes the `.crx` file as an installable extension when it's downloaded via the policy.
46
+
After you configure this header, Microsoft Edge recognizes the `.crx` file as an installable extension when it's downloaded through the policy.
47
47
48
48
#### Example: Configure MIME mapping on IIS
49
49
@@ -52,20 +52,20 @@ After you configure this header, Microsoft Edge recognizes the `.crx` file as an
52
52
1. In the **Actions** pane, select **Add…**.
53
53
1. Set **File name extension** to `.crx`.
54
54
1. Set **MIME type** to `application/x-chrome-extension`.
55
-
1. Select **OK**, then recycle the website or application pool if necessary.
55
+
1. Select **OK**, then recycle the website or application pool, if it's necessary.
56
56
57
-
## Cause: Invalid extension manifest or update manifest XML
57
+
## Cause 3: Invalid extension manifest or update manifest XML
58
58
59
-
The extension metadata in `manifest.json` or in the _update manifest XML_ is invalid. Examples include:
59
+
The extension metadata in `manifest.json` or in the _update manifest XML_ is invalid, such as in the following examples:
60
60
61
61
- The `version` field in `manifest.json` uses an invalid format (for example, `1.0-beta` or other non-numeric characters).
62
-
- The _update manifest XML_ used for self-hosted updates contains invalid or inconsistent values (for example, mismatched version numbers or malformed XML).
62
+
- The _update manifest XML_that's used for self-hosted updates contains invalid or inconsistent values (for example, mismatched version numbers or malformed XML).
63
63
64
-
In these cases, manual drag-and-drop installation might succeed in some scenarios, but policy-based installation or automatic updates might fail.
64
+
In these cases, manual drag-and-drop installation might succeed in some scenarios. However, policy-based installation or automatic updates might fail.
65
65
66
66
### Solution: Validate and correct the extension manifests
67
67
68
-
Validate and correct the extension manifest or update manifest XML by following the Chrome documentation, which also applies to Microsoft Edge and other Chromium-based browsers:
68
+
Validate and correct the extension manifest or update manifest XML by following the Chrome documentation (applies also to Microsoft Edge and other Chromium-based browsers):
0 commit comments