How to remove Adobe Acrobat context menu for image files?

++ADDING TO THE TOPIC,

@Mr302660931f1m ,

I normally fiddle a lot with the Windows registry and I am unsure if what you are trying to achieve is possible.

Although the modifying of context menus appears to be very flexible in both Microsoft Windows and macOS, there is other criteria to consider.

For instance, when it comes down to Adobe Acrobat you need to consult with the Acrobat Enterprise Toolkit | Regsitry Preferences Reference:

• https://www.adobe.com/devnet-docs/acrobatetk/tools/PrefRef/Windows/index.html

And unless there is a third-party (licensed and paid-for) registry editing tool that would allow the operating system to unrestrict such editing on Acrobat's context menus there are some registry hives, subfeatures and preferences that may not be lockable.

In a very ample context, the editing of the

HKEY_CLASSES_ROOT

 registry hive, is not enough.

For starters, there is no step-by-step documentation that will orient the users on how to manually create registry keys or sub-keys that are specific to Adobe Acrobat's context menu features.

That may include dWROD values and how to manually create the desired lockable preferences, which may not exist (such as the "bAllow or bDisable features) together with some documented Preferences  (such as, for example, "TWhiteList" or "TBlackList" or "cDefaultExecMenu").

The best you can do is to consult with the old (and almost fully deprecated) resources linked below:

• https://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/preferences.html

• https://www.adobe.com/devnet-docs/acrobatetk/tools/PrefRef/Windows/index.html

• https://acrobatusers.com/tutorials/executing_menu_items_from_javascript/

In which case, if these resources don't work for you then it may not be possible to edit such context menu, I'm afraid.

In addition, the ability by which  users benefit from deleting uselss menu items, which are by default, featured by the host operating system, the same is not true with apps or programs such as Acrobat.

If I am not wrong, the ability to interact like that with a program"s registry hive (which is binded to the secured enviroment of the host operating system) dates back to WindosXP (and maybe in the very early versions of Windows7).

After that era it all changed back to a very restricted operating system  environment to prevent exploits and reverse engineering of the hosted apps.