Block Flash activation in Office documents (CLSID 6E, Common)
The `ActivationFilterOverride` DWORD value controls an exception to the Office COM kill bit for the `Shockwave Flash Object`, identified by CLSID `{D27CDB6E-AE6D-11CF-96B8-444553540000}`.
since 0.9.8.11
Purpose
Show registry keys (1)
HKLM\software\microsoft\Office\Common\COM Compatibility\{D27CDB6E-AE6D-11CF-96B8-444553540000}\ActivationFilterOverride
The ActivationFilterOverride DWORD value controls an exception to the Office COM kill bit for the Shockwave Flash Object, identified by CLSID {D27CDB6E-AE6D-11CF-96B8-444553540000}.
A value of 0 does not override the activation filter. The Flash control that Office blocks from activation by default therefore remains fully blocked within Office processes. This covers instances embedded in or linked from Office documents as well as attempts to activate the control through other components running inside an Office process.
This value does not independently establish a COM kill bit for arbitrary objects. Its meaning is limited to the Office block associated with this CLSID. A value of 1 has a different effect: it restricts the block to linking and embedding scenarios while permitting other activation paths within the Office process.
Notes
Security
The setting prevents Office from loading the specified legacy Flash ActiveX component. Office documents and other components loaded inside an Office process therefore cannot use this control to run active Flash content.
The block is limited to Office processes and to the specified CLSID. It does not uninstall Flash, block other COM or ActiveX classes, or provide a system-wide Flash restriction. In particular, the separate Macromedia Flash Factory Object identified by CLSID {D27CDB70-AE6D-11CF-96B8-444553540000} is outside the scope of this registry value.
Possible side effects
Office documents, add-ins, or other Office extensions that depend on the specified Flash control cannot load or run their Flash content. Affected content may appear blank or lose its intended interactive functionality.
Notes
Microsoft documents the unversioned registry branch for Office 2010 and Office 2013. For Office 2016, Microsoft instead specifies a path below Office\16.0\Common; 32-bit Office on 64-bit Windows also uses the corresponding Wow6432Node branch. This value therefore has an effect only when the installed Office version and architecture read this exact registry location.
Microsoft documentation
Microsoft Support: Security Settings for COM objects in Office