It is windows 11. Adding shortcut to context menu does not affect fences

It works!

well i did only 1 thing is to restore the legacy context menu.

In the past all of the desktop folders would occasionally vanish and double clicking on a blank screen never did bring them back. I always had to reboot. I am running an fully updated Windows 10 system. Today I updated to version 4.10 and most folders keep vanishing.  I really want to keep the software as I do like it but I also wish it worked. I do not want to reboot all day long. Please fix the software...... 

Windows 22H2 (OS build 19045.2604)  Win10PRO

You don't need a program to change back to legacy menu, it's all done within windows.

https://answers.microsoft.com/en-us/windows/forum/all/restore-old-right-click-context-menu-in-windows-11/a62e797c-eaf3-411b-aeec-e460e6e5a82a

cheers

Restore to the actual Windows11 context menus

Paul Scroggins
Associate Technical Support Analyst

It was an effort to test - to see if restoring how Windows 11 was meant to render such things works.

We are still looking into it but, if it works for you, that would be the current workaround for people that have manually altered how such menus appear in Windows 11.

Sean Drohan
Stardock Product Lifecycle Manager

Windows 11 22H2 update KB5023706.

Fences 4.1.0.6 and 4.1.1.1 causes Windows Explorer to crash on startup.  Initially Fences displays a message dialog saying that it has disabled itself because of an Explorer problem, but the dialog disappears quickly as Explorer continues to crash in a never ending loop.  The desktop does not get displayed and I cannot get control!

The only fix has been to restore my System Drive from backup and then immediately pausing Windows Updates to stop KB5023706 from being downloaded and installed.

The Windows release notes for KB5023506 do mention this possible behavior for UI modifying apps. Is this the issue here?

"March 14, 2023 - KB5023706 (OS Build 22621.1413)

After installing this or later updates, Windows devices with some third-party UI customization apps might not start up. These third-party apps might cause errors with explorer.exe that might repeat multiple times in a loop. The known affected third-party UI customization apps are ExplorerPatcher and StartAllBack. These types of apps often use unsupported methods to achieve their customization and as a result can have unintended results on your Windows device.

We recommend uninstalling any third-party UI customization app before installing this or later updates to prevent this issue. If your Windows device is already experiencing this issue, you might need to contact customer support for the developer of the app you are using. If you are using StartAllBack, you might be able to prevent this issue by updating to the latest version (v3.5.6 or later).

We are presently investigating and will provide more information when it is available."

I would like to continue using Fences 4, but this does not bode well.

OOPS, sorry guys, but this turned out to be my own fault.  I was using a Registry change to re-enable the older File Explorer Ribbon, and this did not play nicely with the updated version of Explorer in KB5023706.  Once I edited the Registry 'Shell' entry back to default the update applied and ran correctly.  No issue with Fences.

Still can't load Fences configuration from the context menu in Windows 11. I sent debug info by e-mail yesterday.

Hello,
Sorry to hear you are having issues. But, If you have issue with Fences, please give us more details on your issue. Refer here as a guide: https://support.stardock.com/space/SHC/1387954197/Contacting+Stardock+About+Fences+Issues

Thank you.
Basj,
Stardock Community Assistant.

Yes - this is where the issue is. It hadn't dawned on me that using the legacy menu would make a difference there. Hopefully, Fences can be made to work with the legacy menu as it gives me much faster access to the many tools I use on my system.