Office COM kill bit for Macromedia Flash Factory Object
Setting the `Compatibility Flags` DWORD to `1024` (`0x00000400`) applies the Office COM kill bit to CLSID `{D27CDB70-AE6D-11CF-96B8-444553540000}`.
since 0.9.8.11
Purpose
Show registry keys (1)
HKLM\software\WOW6432Node\Microsoft\Office\Common\COM Compatibility\{D27CDB70-AE6D-11CF-96B8-444553540000}\Compatibility Flags
Setting the Compatibility Flags DWORD to 1024 (0x00000400) applies the Office COM kill bit to CLSID {D27CDB70-AE6D-11CF-96B8-444553540000}. Microsoft identifies this COM class as Macromedia Flash Factory Object.
The kill bit prevents affected Office applications from activating this ActiveX control. The original implementation covered COM objects embedded in or linked from Office documents. With the kill-bit behavior updated by KB3178703, Office blocks activation of the specified COM class throughout the Office process, including activation through mechanisms such as add-ins.
Notes
Security
Blocking the class reduces the attack surface presented by documents or Office extensions that attempt to load this Flash COM object. Active Flash content cannot execute inside the Office process through this CLSID.
This is an Office-specific control. It does not set the Internet Explorer ActiveX kill bit or disable the COM class system-wide. It also covers only CLSID {D27CDB70-AE6D-11CF-96B8-444553540000}. The related Shockwave Flash Object uses the separate CLSID {D27CDB6E-AE6D-11CF-96B8-444553540000} and is not blocked by this registry value alone.
Possible side effects
Office documents, templates, or add-ins that depend on Macromedia Flash Factory Object can no longer load or run that component. Depending on the Office version and document, the content may remain disabled or appear as an unavailable object.
Notes
The WOW6432Node location targets 32-bit Office running on 64-bit Windows. Microsoft documents the unversioned Office\Common location used here for Office 2010 and Office 2013. Office 2016 uses a documented Office\16.0\Common location, while Click-to-Run installations may use an additional virtualized registry path. This value should therefore not be assumed to affect every Office architecture and installation type.
Current Office kill-bit documentation lists this CLSID among the controls blocked by default. Microsoft describes that list as a snapshot that may change.
A separately defined ActivationFilterOverride value can alter the scope of the kill bit. The registry value documented here does not itself create that exception.
Microsoft documentation
Microsoft Support: Security Settings for COM objects in Office