Hi andy,

We have a candidate build available for testing, if you'd like to give a shot. This issue appears to be rare but we've heard of similar as Adam notes above.

We'll have a full installer ready next week, but in the meantime a patcher is ready for trying out (v6.01 will be displayed in the about box) that delivers the same results at https://www.dropbox.com/scl/fi/yk2zloek6mmzeqxj8e8ws/UpdatePatcher_Debug_2025_06_13__3_23_06_pm.exe?rlkey=uez9ouhknhl3100mvbpqdnzyf&dl=1

Unfortunately, I was unable to download the patch as it said the link was incorrect 

Hi Andy just checking in to see if this helped. We just released v6.01 beta which includes this, and the link with the patcher above is more or less identical.

Hi Guys,

Just an update on this issue. I initially thought the latest release had solved the issue, but it appears to be back. If I click on an icon that is foremost, many times it opens or selects the icon shortcut that is directly underneath. It appears that if I hover over the icon and wait several seconds until it highlights then 9 out of 10, I get the application opening that I want, but if I just go to a topmost fence and immediately click a shortcut without the wait it opens the application that belongs to the underlying icon. The annoying thing is that this issue happens intermittently, for example as I wrote this post, I tried a few times to see if the issue arose and it hasn't, yet yesterday it happened all the time.  I know waiting for the shortcut to highlight is only a few seconds, but it does impact my use of fences.  I really want this feature as I asked for it way back but currently, I have ungrouped all my fences until this issue is resolved.

Thanks for listening,

Andy

Hello,
Sorry to hear you are having issues. Have you tried the latest Fences 6.01 Beta? If not please do and report back.

Thank you,
Basj,
Stardock Community Assistant.

Great, thank you for reporting back. I've forwarded it to Support.

Basj,
Stardock Community Assistant

Aye, disappointing Andy ty for letting us know.

This is a very tricky one to debug as it sounds like a timing issue with a matter of milliseconds. Logging still probably the next step.

It sounds like you've disassembled the situation. But if you put it back, *immediately* after it occurring, open the Fences Config → About → Troubleshooting → Upload error report. And likewise, beforehand as we did before, Fences Config → About → Troubleshooting → Enable Advanced Logging (and reboot / log off & on as necessary).

Upload the log along with the filename that you were *trying* to select, vs the one that *did* get selected, and we can see if there's any hints in the log as to determine next steps.

I imagine we're going to have to get pretty thick with the debug logging statements to track this one down, but we would really like to ensure this mechanism is 100%.