Microsoft Configuration Manager

12709700

12 November 2026Doc updateAction required+45 / −3 lines

In brief

The documentation now details an issue where multiple required versions of an extension can repeatedly prompt installation and prevent the Configuration Manager console from opening. It adds a SQL workaround for previous versions.

What Intune admins need to know

Administrators affected by this issue on previous versions should run the documented SQL script on the CAS and all primary site databases.

This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.

Documentation change

View full page diff

View on Microsoft Learn

The comparison below shows only the changed extract. Use the full-page view for complete context.

Adding or deleting orchestration post-installation script can cause the deletion of post-installation scripts from other orchestration groups.
~~The following issue described in~~Unable to open the ~~2111 release notes is resolved.~~console because extension installation loops

~~Unable to open console because extension installation loops~~In certain circumstances, you're unable to open the console due to an extension installation loop. This issue occurs when two or more versions of a single extension are marked as required for installation. This issue can occur for extensions imported through the wizard, from a PowerShell script, or through Community hub. To prevent the issue, use the Make optional setting before importing a new version of the extension.
When this issue occurs, it initially appears as a normal console extension installation. After the extension finishes installing, you select Close to restart the Configuration Manager console. When the console restarts, you're prompted to install the console extension again. The extension installation continues to loop, and the Configuration Manager console doesn't fully open.
To prevent and work around this issue in previous versions of Configuration Manager, run the following SQL script on your CAS database and all your primary site databases:
```
ALTER VIEW vSMS_ConsoleExtensionMetadata
AS
    WITH m AS(
       SELECT *,
           RN = ROW_NUMBER()OVER(PARTITION BY ID ORDER BY Version DESC)
       FROM ConsoleExtensionMetadata
    )
    SELECT
        m.ID,
        m.Name,
        m.Description,
        m.Author,
        m.Version,
        m.IsEnabled,
        m.IsApproved,
        m.CreatedTime,
        m.CreatedBy,
        m.UpdateTime,
        m.IsTombstoned,
        m.IsRequired,
        m.IsSigned,
        m.IsUnsignedAllowed,
        CASE m.IsRequired
            WHEN 0 THEN ''
            ELSE
            (
                SELECT top(1) author FROM ConsoleExtensionRevisionHistory h
                WHERE m.ID=h.ExtensionId AND m.Version=h.Version AND h.Changes & 1=1
                ORDER BY h.RevisionTime DESC
            )
        END AS RequiredBy,
        m.IsSetupDefined
    FROM m
    WHERE RN = 1
GO
```

Update information for Microsoft Endpoint Configuration Manager, version 2111

@@ -61,9 +61,51 @@ You can access the update in the Updates and Servicing node of the Configuration 
 - Adding or deleting orchestration post-installation script can cause the deletion of post-installation scripts from other orchestration groups.
 
-- The following issue described in the 2111 release notes is resolved.
-
-    [Unable to open console because extension installation loops](../../core/servers/deploy/install/release-notes#unable-to-open-console-because-extension-installation-loops)
+- **Unable to open the console because extension installation loops**
+
+    In certain circumstances, you're unable to open the console due to an extension installation loop. This issue occurs when two or more versions of a single extension are marked as [required for installation](../../core/servers/manage/admin-console-extensions#require-installation-of-a-console-extension). This issue can occur for extensions imported through the wizard, from a PowerShell script, or through Community hub. To prevent the issue, use the **Make optional** setting before importing a new version of the extension.
+
+    When this issue occurs, it initially appears as a normal console extension installation. After the extension finishes installing, you select **Close** to restart the Configuration Manager console. When the console restarts, you're prompted to install the console extension again. The extension installation continues to loop, and the Configuration Manager console doesn't fully open.
+
+    To prevent and work around this issue in previous versions of Configuration Manager, run the following SQL script on your CAS database and all your primary site databases:
+
+    ```sql
+    ALTER VIEW vSMS_ConsoleExtensionMetadata
+    AS
+        WITH m AS(
+           SELECT *,
+               RN = ROW_NUMBER()OVER(PARTITION BY ID ORDER BY Version DESC)
+           FROM ConsoleExtensionMetadata
+        )
+        SELECT
+            m.ID,
+            m.Name,
+            m.Description,
+            m.Author,
+            m.Version,
+            m.IsEnabled,
+            m.IsApproved,
+            m.CreatedTime,
+            m.CreatedBy,
+            m.UpdateTime,
+            m.IsTombstoned,
+            m.IsRequired,
+            m.IsSigned,
+            m.IsUnsignedAllowed,
+            CASE m.IsRequired
+                WHEN 0 THEN ''
+                ELSE
+                (
+                    SELECT top(1) author FROM ConsoleExtensionRevisionHistory h
+                    WHERE m.ID=h.ExtensionId AND m.Version=h.Version AND h.Changes & 1=1
+                    ORDER BY h.RevisionTime DESC
+                )
+            END AS RequiredBy,
+            m.IsSetupDefined
+        FROM m
+        WHERE RN = 1
+    GO
+    ```
 
 ## Update information for Microsoft Endpoint Configuration Manager, version 2111