Fences 4 context menu options don't work

Can't open Fences settings from right-click, lock fences, etc.

from Stardock Forums

I recently upgraded from Fences 3 to Fences 4. Doing so broke my context menu options in Fences 4. Right-clicking and going to "Configure Fences" does nothing, and I'm unable to "Lock Fences".

I've tried uninstalling and reinstalling.

Tried uninstalling and reinstalling with "Remove Settings" checked.

Tried uninstalling my antivirus (Malwarebytes) and repeating this process.

Tried the Purge and re-install as suggested here https://forums.stardock.com/486084/fences-support-faq#reinstalling

Tried deleting all keys related to Fences 3 in my registry.

I've probably uninstalled and reinstalled, trying different things, at least 10 times now. I'm out of ideas, short of reinstalling Windows.

 

Everything else seems to work, but these context menu options just will -not- function.

 

(Windows 11 Pro)

fences context menu lock fences configure options broken
16,935 views 17 replies
Elemental: Reforged
Reply #3 from Stardock.net Forums Top

Quoting basj, reply 1

Hello,
Sorry to hear you are having issues. Need to know more on your system. Please refer here: https://support.stardock.com/space/SHC/1387954197/Contacting+Stardock+About+Fences+Issues

Thanks
Basj,
Stardock Community Assistant.
End of basj's quote

Thanks Basj, here are some more details on my particular environment:

Edition    Windows 11 Pro
Version    22H2
Installed on    ‎5/‎26/‎2023
OS build    22621.1848
Experience    Windows Feature Experience Pack 1000.22642.1000.0
Processor    13th Gen Intel(R) Core(TM) i9-13900K   3.00 GHz
Installed RAM    32.0 GB (31.8 GB usable)
System type    64-bit operating system, x64-based processor

This is a new issue. I haven't experienced this particular issue before, either on this PC or any other.

Thanks

 

Reply #4 from Stardock Forums Top

Need to know your Fences installed version please.

Thank you,

Basj,
Stardock Community Assistant

Reply #6 from Stardock Forums Top

Quoting leriazjay, reply 2

Same issue here. I'm not sure at exactly what point this happened because I rarely need to make changes to my fences, but I just noticed it today. None of the context options work. 

Windows Version 22H2 (OS Build 22621.1702)
End of leriazjay's quote

leriazjay, it looks like your problem is somewhat different than mine; I am able to use context options in a Fence fine, but the "Lock Fences" and "Configure Fences" buttons, which are not options for a specific Fence, do not work for me.

Reply #7 from Stardock Forums Top

Please try purge and reinstall steps as mention here : [Link]. Just make sure to redownload the latest version. Reboot after the purge. Reinstall and reboot again after the installation. Retest and report back here.

Thank you,
Basj,
Stardock Community Assistant.

Reply #8 from Stardock Forums Top

Quoting PHP_CIG, reply 6


Quoting leriazjay,
reply 2

Same issue here. I'm not sure at exactly what point this happened because I rarely need to make changes to my fences, but I just noticed it today. None of the context options work. 

Windows Version 22H2 (OS Build 22621.1702)



leriazjay, it looks like your problem is somewhat different than mine; I am able to use context options in a Fence fine, but the "Lock Fences" and "Configure Fences" buttons, which are not options for a specific Fence, do not work for me.

End of PHP_CIG's quote

 

I see. Regardless, I did execute the steps outlined in the Fences purging and re-installing link. I'm still encountering the same issue. On the latest Fences version, 4.12.

Reply #9 from Stardock Forums Top

Quoting leriazjay, reply 8

I see. Regardless, I did execute the steps outlined in the Fences purging and re-installing link. I'm still encountering the same issue. On the latest Fences version, 4.12.
End of leriazjay's quote

Did you somehow changed Windows 11 default right click menu to Windows 10 type context menu?

Thank you,

Basj,
Stardock Community Assistant

Reply #10 from Stardock Forums Top

Quoting basj, reply 7

Please try purge and reinstall steps as mention here : [Link]. Just make sure to redownload the latest version. Reboot after the purge. Reinstall and reboot again after the installation. Retest and report back here.

Thank you,
Basj,
Stardock Community Assistant.
End of basj's quote

 

Okay, I followed the steps there and did the purge again. I made a snapshot, made sure to run the .bat as Administrator, as suggested. It uninstalled Fences, asked me to reboot which I pressed "No" to, per the article, then pressed "Ok" to the prompt to reboot. I then rebooted, downloaded the latest installer from the Stardock website (which is indeed 4.12, though it's labeled incorrectly on the download button as 4.10.6), and restored the snapshot. My issue with the "Configure Fences" and "Lock Fences" context menu options persists.

Here is the output of the purge batch file:

SUCCESS: The process "explorer.exe" with PID 8452 has been terminated.

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
    Fences    REG_SZ    "c:\program files (x86)\stardock\fences\Fences.exe" /startup

The operation completed successfully.

HKEY_CURRENT_USER\Software\Stardock\Fences
    LastConfigSyncAttempt    REG_SZ    6/16/2023 12:18:03 AM
    DateInstalled    REG_SZ    6/13/2023 4:21:56 PM
    LastLangID    REG_SZ    en-US
    ProVersionEverInstalled    REG_DWORD    0x1
    LastConfigDate    REG_SZ    6/16/2023 12:18:03 AM
    LastConfig    REG_SZ    <Configuration>

<BugSplat>
CrashReporting-BuildEnabled-3.0.5
CrashReporting-BuildEnabled-3.0.6
CrashReporting-BuildEnabled-3.0.7
CrashReporting-BuildEnabled-3.0.8
CrashReporting-BuildEnabled-3.0.9
CrashReporting-BuildEnabled-3.0.10
CrashReporting-BuildEnabled-3.0.11
CrashReporting-BuildEnabled-3.1.0
CrashReporting-BuildEnabled-3.1.1
CrashReporting-BuildEnabled-3.1.2
CrashReporting-BuildEnabled-3.1.3
CrashReporting-BuildEnabled-3.1.4
CrashReporting-BuildEnabled-3.1.5
CrashReporting-BuildEnabled-3.1.6
CrashReporting-BuildEnabled-3.1.7
CrashReporting-BuildEnabled-3.1.8
CrashReporting-BuildEnabled-3.1.9
CrashReporting-BuildEnabled-3.1.10
CrashReporting-BuildEnabled-3.1.*
CrashReporting-BuildDisabled-3.0.*
</BugSplat>

<Telemetry>
TrialTelemetry-BuildEnabled-3.0.5
TrialTelemetry-BuildEnabled-3.0.6
TrialTelemetry-BuildEnabled-3.0.7
TrialTelemetry-BuildEnabled-3.0.8
TrialTelemetry-BuildEnabled-3.0.9
TrialTelemetry-BuildEnabled-3.0.10
TrialTelemetry-BuildEnabled-3.0.11
TrialTelemetry-BuildEnabled-3.0.*
TrialTelemetry-BuildEnabled-3.1.0
TrialTelemetry-BuildEnabled-3.1.1
TrialTelemetry-BuildEnabled-3.1.2
TrialTelemetry-BuildEnabled-3.1.3
TrialTelemetry-BuildEnabled-3.1.4
TrialTelemetry-BuildEnabled-3.1.5
TrialTelemetry-BuildEnabled-3.1.6
TrialTelemetry-BuildEnabled-3.1.7
TrialTelemetry-BuildEnabled-3.1.8
TrialTelemetry-BuildEnabled-3.1.9
TrialTelemetry-BuildEnabled-3.1.10
TrialTelemetry-BuildEnabled-3.1.*
</Telemetry>


<Pulse>
Pulse-BuildEnabled-3.0.5
Pulse-BuildEnabled-3.0.6
Pulse-BuildEnabled-3.0.7
Pulse-BuildEnabled-3.0.8
Pulse-BuildEnabled-3.0.9
Pulse-BuildEnabled-3.0.10
Pulse-BuildEnabled-3.0.11
Pulse-BuildEnabled-3.0.*
Pulse-BuildEnabled-3.1.0
Pulse-BuildEnabled-3.1.1
Pulse-BuildEnabled-3.1.2
Pulse-BuildEnabled-3.1.3
Pulse-BuildEnabled-3.1.4
Pulse-BuildEnabled-3.1.5
Pulse-BuildEnabled-3.1.6
Pulse-BuildEnabled-3.1.7
Pulse-BuildEnabled-3.1.8
Pulse-BuildEnabled-3.1.9
Pulse-BuildEnabled-3.1.10
Pulse-BuildEnabled-3.1.*
</Pulse>


</Configuration>
    CrashReportingEnabled    REG_DWORD    0x1
    LastDebugHeader    REG_SZ    4.1.2.1 5437208 - 5/1/2023 7:23:16 PM 3189016 - 5/1/2023 7:23:16 PM 3588376 - 5/1/2023 7:23:16 PM 3670296 - 5/1/2023 7:23:16 PMNone
    ReportState    REG_DWORD    0x2
    InstallID    REG_SZ    0875647d-1249-4fd2-8da1-160fe004e3b5
    InstallBucket    REG_DWORD    0xd71730d
    LastPulse    REG_SZ    1686896284
    LastDailyScreenshotDate    REG_DWORD    0xb457d
    LastDailyScreenshot    REG_DWORD    0x0

HKEY_CURRENT_USER\Software\Stardock\Fences\Groups
HKEY_CURRENT_USER\Software\Stardock\Fences\Icons
HKEY_CURRENT_USER\Software\Stardock\Fences\InitialSnapshot
HKEY_CURRENT_USER\Software\Stardock\Fences\NavHistory
HKEY_CURRENT_USER\Software\Stardock\Fences\Rules
HKEY_CURRENT_USER\Software\Stardock\Fences\Settings
HKEY_CURRENT_USER\Software\Stardock\Fences\Skinning
HKEY_CURRENT_USER\Software\Stardock\Fences\Tips
HKEY_CURRENT_USER\Software\Stardock\Fences\ViewStates
The operation completed successfully.
ERROR: The system was unable to find the specified registry key or value.

ERROR: The system was unable to find the specified registry key or value.

ERROR: The system was unable to find the specified registry key or value.

ERROR: The system was unable to find the specified registry key or value.

ERROR: The system was unable to find the specified registry key or value.

ERROR: The system was unable to find the specified registry key or value.

ERROR: The system was unable to find the specified registry key or value.

ERROR: The system was unable to find the specified registry key or value.

ERROR: The system was unable to find the specified registry key or value.

ERROR: The system was unable to find the specified registry key or value.

SUCCESS: Sent termination signal to the process "rundll32.exe" with PID 9752.
SUCCESS: Sent termination signal to the process "rundll32.exe" with PID 9760.
C:\Program Files (x86)\Stardock\Fences\FencesMenu64.dll
Access is denied.
C:\Program Files (x86)\Stardock\Fences\FencesMenu64.dll - Access is denied.
        1 dir(s) moved.

End of quote

Reply #11 from Stardock Forums Top

Quoting PHP_CIG, reply 10

Okay, I followed the steps there and did the purge again. I made a snapshot, made sure to run the .bat as Administrator, as suggested. It uninstalled Fences, asked me to reboot which I pressed "No" to, per the article, then pressed "Ok" to the prompt to reboot. I then rebooted, downloaded the latest installer from the Stardock website (which is indeed 4.12, though it's labeled incorrectly on the download button as 4.10.6), and restored the snapshot. My issue with the "Configure Fences" and "Lock Fences" context menu options persists.
End of PHP_CIG's quote

Did you somehow changed Windows 11 default right click menu to Windows 10 type context menu? If yes, you did, please revert back to default Windows 11 right click menu. If not, please try cleanboot : https://forums.stardock.com/486084/fences-support-faq#cleanboot

Thank you,

Basj,
Stardock Community Assistant

+1 Loading…
Reply #12 from Stardock Forums Top

Quoting basj, reply 11


Quoting PHP_CIG,
reply 10

Okay, I followed the steps there and did the purge again. I made a snapshot, made sure to run the .bat as Administrator, as suggested. It uninstalled Fences, asked me to reboot which I pressed "No" to, per the article, then pressed "Ok" to the prompt to reboot. I then rebooted, downloaded the latest installer from the Stardock website (which is indeed 4.12, though it's labeled incorrectly on the download button as 4.10.6), and restored the snapshot. My issue with the "Configure Fences" and "Lock Fences" context menu options persists.



Did you somehow changed Windows 11 default right click menu to Windows 10 type context menu? If yes, you did, please revert back to default Windows 11 right click menu. If not, please try cleanboot : https://forums.stardock.com/486084/fences-support-faq#cleanboot

Thank you,

Basj,
Stardock Community Assistant

End of basj's quote

A-ha, that is indeed the culprit! I'd followed the instructions here https://www.elevenforum.com/t/disable-show-more-options-context-menu-in-windows-11.1589/ to turn off the new Windows 11 "Show More Options" style context menu (because it's stupid!)

When I removed the aforementioned registry key and rebooted, I was indeed able to open the Configure Fences menu, and use the Lock Fences option again, through the right-click context menu.

However, I -really- don't want to keep the Windows 11 style context menu this way. This worked as-expected with Fences 3 on Windows 11. I'm sure a lot of others out there will make this change on their computers as well, as many feel similarly about this menu, and if they're running Fences 4, they will run into the same trouble I did.

As such, can this be escalated to the devs to make a programming change, so that this works for people who enable the classic context menu in Windows 11?

Reply #13 from Stardock Forums Top

From what I know, Stardock software always work with vanilla Windows. This is to ensure it work on most people who use their computer as is. However, I have forward your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

+1 Loading…
Reply #14 from Stardock Forums Top

Quoting basj, reply 13

From what I know, Stardock software always work with vanilla Windows. This is to ensure it work on most people who use their computer as is. However, I have forward your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant
End of basj's quote

Thanks bud. I appreciate all your help!

Reply #15 from Stardock Forums Top

Hi

Same issu for me.

I have follow all step without result.

For me, if I use Fences v4.0.7.2, everything running fine. If I use Fences v4.1.2.1, I lost fences menu from desktop.

It will be fine to you to find the problem without to ask evrybody to try many thing with hope to resolve the problem.

Something is different after v4.0.7.2.

 

Thanks to close this subject with issu.

 

Best regards

 

DBX

Reply #16 from Stardock Forums Top

Quoting THE_DBX, reply 15

Hi

Same issu for me.

I have follow all step without result.

For me, if I use Fences v4.0.7.2, everything running fine. If I use Fences v4.1.2.1, I lost fences menu from desktop.

It will be fine to you to find the problem without to ask evrybody to try many thing with hope to resolve the problem.

Something is different after v4.0.7.2.

Thanks to close this subject with issu.
Best regards
DBX
End of THE_DBX's quote

I did not mentioned the issue was closed, in reply#13 I mentioned I've forward the issue to Support. When we ask user do things with specific reason to try to figure out where the issue came from. There are lot of possibilities, different system have different component and software running in the background. There definitely differences between older version and newer version. Newer version come along to resolved issues. Refer here if you wish to know what and why it change: https://www.stardock.com/products/fences/history. Also notice that Windows 11 context menu does changed from it previous form. Hence Fences need to change itself accordingly.

If you have issue and your issue is not related at all with the mod context menu as mention by OP. Please create a new thread for your issue and we will try to help you on your issue from there. Include all the details in there.

Thank you,

Basj,
Stardock Community Assistant

Reply #17 from Stardock Forums Top

Fences 4.2.2/Win 11

Found another post and it indicates that in Win 11 the context menu moved under right click/context menu/More options/View ->/

I found the Lock Fences selected and unselected it - full capabilities restored