CKB:Add in is disabled when launching Outlook: Unterschied zwischen den Versionen
(Lösung herforgehoben) |
(Registry Key angepasst) |
||
| Zeile 10: | Zeile 10: | ||
== Cause: == | == Cause: == | ||
The load behavior of Cryptshare for Office 365 & Outlook is controlled by a registry entry stored in the following path: | The load behavior of Cryptshare for Office 365 & Outlook is controlled by a registry entry stored in the following path: | ||
Computer\HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\ | Computer\HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\Pointsharp.CryptshareForOutlook.AddinModule\LoadBehavior | ||
Additionally, other entries in the registry might influence whether or not the Add-in is loaded during the Outlook startup. | Additionally, other entries in the registry might influence whether or not the Add-in is loaded during the Outlook startup. | ||
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Resiliency\DisabledItems | HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Resiliency\DisabledItems | ||
| Zeile 16: | Zeile 16: | ||
== Solution: == | == Solution: == | ||
Please ensure that there is no registry entry at HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outlook\Addins\ | Please ensure that there is no registry entry at HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outlook\Addins\Pointsharp.CryptshareForOutlook.AddinModule\'''LoadBehavior''', otherwise delete the key. In some cases, the Add-In will write the key in the HKEY_CURRENT_USER tree on every startup. The reason is not identified as of yet. If this happens, please ensure that the '''LoadBehavior''' is set to '''3''' to overcome this issue. | ||
If the Add-in can not be re-enabled with this method, there's a good chance that the Add-in is listed as an entry within '''DisabledItems''' or '''CrashingAddinList'''. If existent, '''remove these entries''' and relaunch Outlook. | If the Add-in can not be re-enabled with this method, there's a good chance that the Add-in is listed as an entry within '''DisabledItems''' or '''CrashingAddinList'''. If existent, '''remove these entries''' and relaunch Outlook. | ||
Aktuelle Version vom 26. Juni 2025, 08:03 Uhr
Applies to:
Symptoms:
When the user launches Outlook, the Cryptshare for Office 365 & Outlook Add-in is disabled.
Cause:
The load behavior of Cryptshare for Office 365 & Outlook is controlled by a registry entry stored in the following path:
Computer\HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\Pointsharp.CryptshareForOutlook.AddinModule\LoadBehavior
Additionally, other entries in the registry might influence whether or not the Add-in is loaded during the Outlook startup.
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Resiliency\DisabledItems HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Resiliency\CrashingAddinList
Solution:
Please ensure that there is no registry entry at HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outlook\Addins\Pointsharp.CryptshareForOutlook.AddinModule\LoadBehavior, otherwise delete the key. In some cases, the Add-In will write the key in the HKEY_CURRENT_USER tree on every startup. The reason is not identified as of yet. If this happens, please ensure that the LoadBehavior is set to 3 to overcome this issue.
If the Add-in can not be re-enabled with this method, there's a good chance that the Add-in is listed as an entry within DisabledItems or CrashingAddinList. If existent, remove these entries and relaunch Outlook.
If these entries are not present either, open "Outlook Options → Add-ins → Manage: Disabled Items → Go..." and enable CS4O.
| Related issues | How to manipulate the Registry in a different User Context |
|---|