@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
Stardock Forums
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
Stardock Forums
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!
Stardock Forums
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
Stardock Forums
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.
Stardock Forums
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
Noted! So a few things pop out (1) Indeed, Virtual Desktop sync is something we are looking at! The undocumented Windows API is unstable around this so we're having to tread carefully, and likewise there are other complexities, but it's something we're looking at for the next "Major vNext" update. That said, I'm curious about this script you've put together with AutoHotKey, as there is no API functionality of sorts to switch pages today. So, I want to make sure I ask the question
Stardock Forums
[ResetFrom] Icon monitor origin changed (.lnk) [\\.\DISPLAY3, 3840x0->1920x0] Very interesting! So yes, one minute after workstation lock, the screen goes to sleep (at least for a second), then 15 seconds later a WM_DISPLAYCHANGE notifies of a display settings change. But, according to the display enumeration, everything is still the same – \\.\DISPLAY1, \\.\DISPLAY2, \\.\DISPLAY3, and the overall virtual screen size etc. Yet – those icons somehow then report
Stardock Forums
Sounds good!
Stardock Forums
Hi Jeffis, newsch1, We put in enhanced debug logging for this in the new version above, so just checking in on if anyone has been able to give this a shot, assuming the issue is this occurring. Thanks for any insight
Hi Chongzhou thanks for the report. Wondering if you might be able to submit your settings so we might take a look. If we’re unable to reproduce, we may add a few lines of debug output and see if we can capture more information. To submit a report, go to the About dialog and use Troubleshooting → Create error package. Thanks for your help
Definitely seeing something in these logs, and this is definitely strange. Thanks again for sending the logs Looks like the system is switching to a configuration of 640x480, and things are going haywire then. Will have to work to recreate on our side. Hope to get to the bottom of this
Hi Aylwyn, this is some serious visual carnage! Thank you for the video upload. I'm a little confused, so, some questions to help clear this up if you could. You're stating that you're a long time customer, however you're only citing that only now have a whole bunch of visual issues have cropped up (per your video), while also stating that it occurs on both new and old versions (v6.40 and v6.20). From the sound of it, this is a "rebuilt system from scratch" as well as you
Stardock Forums
Hi Ken, thanks for sharing this and for the video detail. This looks quite strange and have not heard of this. I'm wondering if you have other system enhancements installed that could be conflicting? We'd like to gather more data, if you would be able to help put together a report. (1) Please install the beta version below (2) Enable "Advanced Debug Logging". You can find this in "About" -> "Troubleshooting". (3) Reboot, so the change has effect (4) Reproduce
> I have a mismatch error. How do I correct this. Have you attempted to reinstall, and if so was this unsuccessful? (After reboot)
Stardock Forums
Hey Jeffis, newsch, sorry about having dropped this, the team was taking care of other tasks. Good news, we've been able to add a considerable amount of debug logging around this topic of icon position changes, to hopefully help us get to the bottom of what's going on. Please give the new build an install at https://www.dropbox.co