Allow COM object registration in a Windows Defender Application Control policy

Applies to:

  • Windows 10
  • Windows Server 2016
  • Windows Server 2019


Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.

The Microsoft Component Object Model (COM) is a platform-independent, distributed, object-oriented system for creating binary software components that can interact. COM specifies an object model and programming requirements that enable COM objects to interact with other objects.

COM object configurability in WDAC policy

Prior to the Windows 10 1903 update, Windows Defender Application Control (WDAC) enforced a built-in allow list for COM object registration. While this mechanism works for most common application usage scenarios, customers have provided feedback that there are cases where additional COM objects need to be allowed. The 1903 update to Windows 10 introduces the ability to specify allowed COM objects via their GUID in the WDAC policy.

NOTE: To add this functionality to other versions of Windows 10, you can install the following or later updates:

Get COM object GUID

Get GUID of application to allow in one of the following ways:

  • Finding block event in Event Viewer (Application and Service Logs > Microsoft > Windows > AppLocker > MSI and Script) and extracting GUID
  • Creating audit policy (using New-CIPolicy –Audit), potentially with specific provider, and use info from block events to get GUID

Author policy setting to allow or deny COM object GUID

Three elements:

  • Provider: platform on which code is running (values are Powershell, WSH, IE, VBA, MSI, or a wildcard “AllHostIds”)
  • Key: GUID for the program you with to run, in the format Key="{33333333-4444-4444-1616-161616161616}"
  • ValueName: needs to be set to "EnterpriseDefinedClsId"

One attribute:

  • Value: needs to be “true” for allow and “false” for deny
    • Note that deny only works in base policies, not supplemental
  • The setting needs to be placed in the order of ASCII values (first by Provider, then Key, then ValueName)


Example 1: Allows registration of all COM object GUIDs in any provider

<Setting Provider="AllHostIds" Key="AllKeys" ValueName="EnterpriseDefinedClsId">

Example 2: Blocks a specific COM object from being registered via Internet Explorer (IE)

<Setting Provider="IE" Key="{00000000-4444-4444-1616-161616161616}" ValueName="EnterpriseDefinedClsId">

Example 3: Allows a specific COM object to register in PowerShell

<Setting Provider="PowerShell" Key="{33333333-4444-4444-1616-161616161616}" ValueName="EnterpriseDefinedClsId">