Custom registry entries are deleted after you install updates for Office Click-to-Run editions


Assume that in a Click-to-Run edition of a Microsoft Office application you run an Office add-in that creates custom registry entries under the HKEY_LOCAL_MACHINE (HKLM) hive. In this situation, the custom registry entries are created in a specific part of the Click-to-Run registry subkey. For example, if an add-in creates a registry entry under the HKLM/Software hive, the following registry entry is created:
This behavior is by design because Office Click-to-Run editions use Application Virtualization. Any custom registry entry under the Click-to-Run hive may be changed by any Office update because the Office Click-to-Run editions own the Click-to-Run registry entries. For example, any custom registry entry may be deleted after you install an Office update.
For more information, see 32-bit and 64-bit application data in the registry and Registry Redirector.


To work around this issue, use one or both of the following methods.

Create a logon script

Create a logon script or something similar that will be periodically run on the computer. This script will make sure that the Click-to-Run hive contains the custom registry key.

Create an external process

Create an external process that can be used to write and read custom registry entries. The external process is outside Office Click-to-Run editions, and it will run with a hidden window. When an add-in has to write or read custom registry entries, it can communicate with this external process by using something like Window Messages or pipes. The external process returns the result after it writes or reads custom registry entries.

Article ID: 4012711 - Last Review: 2017, ഫെബ്രു 20 - Revision: 13

Microsoft Excel 2013, Microsoft Word 2013, Microsoft PowerPoint 2013, PowerPoint 2016, Excel 2016, Word 2016