How to remove "configure fences" from context menu?

I try to keep my context menu pretty lean and only populated with things directly related to my work, and non-redundant.

I looked at fencesmenu64.dll which doesnt seem to do the job, this seems to be tied to directory/folders etc which is fine. I'm looking to disable the handler when clicking on blank space.

Would be great to be able to toggle this as an option, but until then can someone point me in the right direction (presumably ala registry?)

fences

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

Hello,

I don't think you have that option in Fences. But you can try Context Menu Editors to do it. Some listed here: https://www.thewindowsclub.com/remove-click-context-menu-items-editors

Caution : use on your own risk.

Thank you,

Basj
Stardock Community Assistant.

Successfully updated karma reason!

thank you for the reply. yes that its the first place i looked. disabling it via shellexview has no effect.

unsure what or where fences is hiding thats unconventional regarding shell extensions but i cant get it to omit. Hopefully a dev can step in and point me in the right direction.

ive renamed every FencesShlExt i could find in the registry manually and it is not only still in the context menu, but still functional as well!

EDIT - it did in fact work. took a restart, i coulda swore disabling a shellextension worked instantaneously. Win!

partial win anyhow. seems it disables the folders/directories etc context menu items as well. now that i know it requires a restart (or presumably just restart of explorer.exe) i can hopefully isolate which reg entry is for the desktop background specifically and disable that alone.

Successfully updated karma reason!

so its an all or nothing. No way i can find to disable just the context menu entry from the desktop. No way to even remove it manually ala registry within reason (renaming a key for example)

shellexview moves the dll from the approved to the blocked list via clsid in the registry which is cumbersome to keep track of, but works if your ok with it being gone from your context menu in all its varieties.

A checkbox to integrate/unintegrate with explorer would be so much easier!

figured id flesh out the post in case someone came-a-googling in the future.

Successfully updated karma reason!