Also curious how it all behaves if you uncheck the box "Enable Fences" at the very bottom of the welcome panel, and enable auto arrange on the desktop
Dr W - Fences Support
Hmm. I'm not certain this will give the information we need but it may, can you check the box for Enable Advanced Logging, reboot and then move the groups around? Will have to let the team know to see if there's more debug information we can add.
Hi Publius, thanks for posting. Is this something new you're seeing with this build specifically, upon upgrading? This type of thing can happen sometimes during awkward DPI changes and is generally driven by Explorer not Fences itself. Fences picks up spacing info from Explorer. If the explorer process restarts (without reboot, say, during an upgrade) after there's been a DPI change is in particular when this type of thing can occurr. Please let us know if logging off and on help
Hi asanidar, seeing if any report?
Hi, please try installing the copy in the previous post, v6.41 and see if it helps. Thank you https://www.dropbox.com/scl/fi/m4zxfd1ynmw75a991zvpv/Fences6_6.4.1.4-j113-Setup.exe?rlkey=rnfr843eia2eylsv1eygq4ovp&dl=1
Woooooo!!!! Huge! Yup confirmed in that log that refreshing the handle resolved issue in full. Thank you again, and, other silent Fences users thank you for your patience as well 🙏🙏
Fixed! Thanks again https://www.dropbox.com/scl/fi/m4zxfd1ynmw75a991zvpv/Fences6_6.4.1.4-j113-Setup.exe?rlkey=rnfr843eia2eylsv1eygq4ovp&dl=1
Aye! The team has been futzing with signing in the build pipeline recently, and yes looks like this one came up broken. Thanks for the heads up. We’ll get a new one printed up shortly
Alright! New version is here, 6.4.1.4 https://www.dropbox.com/scl/fi/un6k5ah5l286gzvumclnb/Fences6_6.4.1.4-j111-Setup.exe?rlkey=c8o8bi2o8gyyk7q4lt39eb7nv&dl=1 I have good hopes that it resolves the issue. In either event fixes/does-not, would appreciate a copy of the report for the debug data to confirm the fix and verify the hypothesis
Hi Chongzhou, I think we have this fixed. Can you try updating here (v6.41 / 6.4.1.4) and let us know? We'd like to include it in an upcoming release. Thanks for your help https://www.dropbox.com/scl/fi/m4zxfd1ynmw75a991zvpv/Fences6_6.4.1.4-j113-Setup.exe?rlkey=rnfr843eia2eylsv1eygq4ovp&dl=1
@Norwicensis, we have a new build that might help with your situation. And in either event, would be happy to get your debug log. (1) Enable advanced debug logging. Go to About, Troubleshooting, and click "Enable advanced logging". (2) Please install the latest version and reboot https://www.dropbox.com/scl/fi/m4zxfd1ynmw75a991zvpv/Fences6
Unclear. It does look like it's just an issue with the handle being invalidated. More or less, the monitor never leaves, but its handle is invalidated during the display changeover. We haven't seen this before, but, we should be able to handle it, and this isn't actually that crazy of a scenario. I'm surprised we haven't seen it before. Found a gap in the just-added handle refresh logic in 6.4.1.2 (saw it just now walking through in debug after reviewing log), so, there's a good chanc
2026-03-04 22:45:02,561 - [ResetFrom] Icon monitor Pre-Change-Verify [rcMonitorValid 0] (.url) [\\.\DISPLAY3, 1920x0->1920x0] [VerifyMonitor1: 10062 0 0,0 0x0] [VerifyMonitor2: 0 0 0,0 0x0] - 0 We are getting close! This verified that the monitor handle at \\.\DISPLAY3 was indeed invalidated, and as well, we're unable to look up a new handle for it, even though it's still being reported as present by Windows via EnumMonitors. This is touching on
Oh no, thanks for the heads up! Fixed link is here But yes for your purposes, I believe v6.40 should do it. Thanks for confirming and glad to hear!
Thanks Jeff! Aye! Looks like this attempt was with v6.40 from February. Had added v6.41 (6.4.1.2) in the post above March 2 – though, looks like the link was broken, so you might not have been able to try. Here it is fixed: https://www.dropbox.com/scl/fi/z601k08hmmzrjifde2su6/Fences6_6.4.1.2-j110-Setup.exe?rlkey=vslexmaoq2fzoyud17h4n7wo6&
Oh, yeah. That is definitely buffer corruption. Yeap, looks like a video card and/or driver issue indeed. Hopefully you can get some different drivers installed and get that resolved. Step one, uninstall current drivers in full, see if problems resolve, and go from there. 🤞🤞!
PS of course last guess here is this pretty cool status bar app you have going on. (yasb?) Guessing maybe you shut that off as well to test, but yeah. From what I'm aware YASB doesn't live inside Explorer.exe's process. But, nonetheless.
Honestly have never seen anything like this. Last time I remember seeing any remotely of this sort (not this, but funny behavior) was maybe a decade+ ago when video card driver bugs were more prevalent, especially in regards to Layered Window / alpha blending support. In that case, layered windows simply weren't hiding/showing properly, as in, they remained visible even when set to invisible. But this one is even more bizarre x100. What you show in "Fences 6.20 - 2.mp4" with the graph
Aye, yes we were able to open up the settings you sent, but could not recreate the issue 💔. It's something that's going on on this system. Clearly it's having to do with the folder portals however. The regular icons seem to be fine. Since you've taken a backup snapshot, have you tried resetting with "Perform automatic layout" and adding just one or two to another page, and seeing if you can reproduce? More or less... does this happen regardless? Li
Hi sakodockadmin, just checking to see if you've been able to test to see if this resolves the issue. It has a lot of additional debug info as well, in case it doesn't – but I think it should be resolved! You can get the latest-latest version at https://www.dropbox.com/scl/fi/7rg79de1cl7jumfls02zw/Fences6_6.4.1.2-j110-Setup.exe?rlkey=vslexma
Hi Chongzhou, Checking in again on if you might be able to submit your settings to us so that we can take a look? You can find "Create error report" below, within About -> Troubleshooting. Thanks for your help
Hi asanidar, we've got a new build ready, that hopefully gives some additional clues. It might take a few shots here, but can you recreate the problem and share the logs from this? Attached v6.41 (6.4.1.4) below: https://www.dropbox.com/scl/fi/m4zxfd1ynmw75a991zvpv/Fences6_6.4.1.4-j113-Setup.exe?rlkey=rnfr843eia2eylsv1eygq4ovp&dl=1 &nbs
Hi Ken, checking to see if you've been able to run the test procedure above. We're happy to look into this, but need more data. Thanks for the help.
Hi Jeffis, new build here that contains some zoomed-in debug logging around that "Icon monitor origin changed" event, around the idea that the monitor handle might be invalidated and thus causing problems. There's a chance that it fixes the problem, but please send log either way, so we can see definitively if our mitigation technique resolves the issue? Thank you! <a href="https://www.dropbox.com/scl/fi/z601k08hmmzrjifde2su6/Fences6_6.4.1.2-j110-Setup.exe?rlkey
Heads up that Windhawk is a tool that not only could – but definitely would – be a likely source of something like this. It's entire purpose is to apply hacked patches on top of explorer. So, I'm betting it is this. Very likely some patch is interrupting a draw procedure of some kind and causing what you're seeing. Might want to give that one a look. For sake of reference, let us know what patches you have applied, so that we can figure out which one is causing the co