I realize there are numerous discussions similar to this topic but I have not found a permanent solution. I have followed many, if not all troubleshooting steps (store fences on per-screen resolution, reinstallation, etc.)
The major issue is that upon reboot or even a system wake-up, the Fences Registry value for the PrimaryMonitorLast is getting changed to a different monitor number than where my fences should appear, and sure enough, the fences are created on the monitor indicated in the PrimaryMonitorLast location rather than on the monitor(s) I want the fences to show on.
Restoring from any of my snapshots rarely fixes the issue, even though the layout was manually created by me when the Fences were correctly showing (occasionally this works, but it is very inconsistent).
HOWEVER, if I edit the XML file in the %UserProfile%\AppData\Roaming\Stardock\Fences\Backups folder, and I manually change the incorrect DISPLAY value (e.g. \\.\DISPLAY3 to \\.\DISPLAY4), AND I change the PrimaryMonitorLast registry value to \\.\DISPLAY4 then I can use the snapshot to restore the fences.
It seems that the PrimaryMonitorLast registry value is the root of this evil.
Fences 3 has not been updated or sold for many years. Deksloc. The most helpful feedback, and what will be updated, is for Fences 4.
I you wanted, you could install the fully functional Fences 4 30-day trial and give is your thoughts.
https://www.stardock.com/products/fences/download-trial
Sean DrohanStardock Product Lifecycle Manager
Thank you for your reply and the offer, but my point with mentioning that I was on Fences 3 was for the previous poster to avoid downgrading since the issue was present on 3 as well.
As for the trial you mentioned, when the issue is resolved, I'll be happy to give Fences 4 a try and purchase.
Support removed my previous post but since downgrading to 3 I haven't had the issue, but it's only been a couple of weeks. Previously it did happen every month or so with 3 but started occurring after every reboot with 4. Fixing it once a month is worth the tradeoff given the benefits Fences provides.
This was happening frequently enough on my triple monitor setup to be fairly annoying. I usually sleep my computer and reboot weekly, or less. Whenever the computer awoke with swapped monitors, I had to reboot to restore screen sanity.
As a troubleshooting measure, I tried this. I was running all 3 monitors via DP from a Powercolor 6800 XT GPU. I took 1 monitor off the GPU and connected it to the motherboard DP port (I have a Ryzen 7700X which has an iGPU).
Success! (so far). No swapped screens this past month.
Just in case this helps identify or narrow down what may still need to be addressed, since May 11, I applied the settings suggested in the "Win+P" post. My three-monitor setup running Fences v 4.21continues to work as expected. Even through ongoing random Windows 11 Standby crashes, regular and forced restarts, Fences has always placed everything back in the correct position since making the suggested changes. I don't know, but my three monitors are running off of a 3070TI and each monitor is set to a different resolution. One 1080, one 1440, one 4k. I do this intentionally for the type of work I do. From some of the Developer's statements, it sounded like that might help Fences retain screen position information? Hope that may be helpful to someone.
#34 works. With an extra little step.
My problem is on a fresh boot up, I have two monitors with Fences and a third has none (I'm calling monitor 1 and 3 good, monitor 2 bad) . I try restoring a snapshot that has all three screens with their icons and fences, they'll pop into position for a brief half-second and then mash up on my main monitor again. The fences on the third screen are good. Screens 1 and 2 are mashed up.
Screens 1 and 3 are DP and screen 2 is HDMI, fwiw.
What worked though was the trick to set monitor 1 as the PC monitor, THEN restore the snapshot, and then re-extend the desktops.
Replying to myself: Okay that fix isn't permanent. After any one of my three monitors goes to sleep - screens 1 and 2 bunch up again.
I've found a semi permanent solution: I save a snapshot, then i duplicate it manually (inside the Backup folder of the program) and replace all words with \\.\DISPLAY1 with \\.\DISPLAY2.
When the icons moves to the other monitor (i have 2 monitors) I restore the original version, if it doesn't work, I restore my REV versions.
It always works
Where do you find the backup folder?
Snapshots you mean?
https://support.stardock.com/space/SHC/1416626186/Fences+Settings+%26+Snapshot+Management
I have this problem still too. It never changed. The problem is less prominent since I deleted all monitors and reinstalled them. I did this, as I had problems with my new monitor and reopening of windows. As my new monitor is gone for the PC when turned off (I can't change it, only when I connect him via HDMI, but then I can't use his full resolution). Now windows doesn't open on the primary monitor, as that is always off in between. Now I could make my system to open those windows at least on my monitor 2 and not on monitor 3 (which I normally only use for special things).As said I still have the problems, but most times it works. Here you can find, what you need to do to reset your monitor numbering with Win10.You may try it, perhaps it makes things better for you too, but be aware, the problem won't be solved!
display - How to reassign monitor numbers in Windows 10 - Stack Overflow
Tried the method of manually editing the snapshot display values but after the second restore the display values ended up changing back to what I changed them from originally. Honestly at this point, I wish that rather than trying to fix the issue with fences as it currently is that they would add a new section or something where you can assign a static display for each of the fences groupings. Like a tab in fences customization that has each of your created fences groups where you have a drop down next to it that says "display1", "display2", etc. and it force whatever fence group you select and all its icons to have that display value. Rather than try to fix the problem as a whole, give us a method to fix the problem that's easier than going and manually editing the xml file for each group/icon line by line.
We have thought of this from all angles (this being one) but as long as Windows will randomly rename displays when connections are removed or changed (HDMI vs. DVI for example), this will continue to be a problem.
That said, we have not lost sight that this is one of the top 'quality of life' issues Fences faces with such setups. It is still very much a priority for us.
Can you read the date of the first installation of the monitor? It is part of the driver definitions of every monitor. Via that you might make an own numbering, which maybe even changed by the user.
As the dat of first installation is with date, time and even seconds, every monitor should be unique or can easily be made unique by deleting all monitors in Win10 and reconnecting them afterwards in the sequence that is wanted.
We certainly could but that install date changes depending on when it is plugged in, not the 1st time it's ever attached. Also, a date is not anything that we could call a reliable ID.
We do appreciate the ideas and feedback, however.
Another quick update from me: The "bunching up" problem was resolved when I ran the Purge Fences batch file.
Greetings,
I am a new Fences user, and I just installed Fences (4.21) and am still in the trial period. I noticed this EXACT same issue - after a reboot my fences and desktop icons are on different monitors (I have two external displays and I keep my laptop closed). I have noticed I can use my "backup" snapshot to fix it, but I would hope this was resolved by now (since this thread is a year old).
Is there anyone actively working this issue, or, can I help with troubleshooting and providing data to the development team? I used fences back in the early 2000's and I decided I wanted to give it a try again, just to de-clutter my desktop (but this is super annoying).
Here to help, and hopeful for a fix!
Thanks,DaveR
Note - if there is a way to submit a ticket, I will gladly purchase and go that route - I know the purchase will happen, just looking for a coupon code, etc.
This thread (and others) should be considered proof that we are, yes.
This thread (and others) should be considered proof that we are, yes.Sean DrohanStardock Product Lifecycle Manager
Sean,
GREAT! Thanks, as I wasn't sure if there was a better or "more official" place to post my findings and submit a support request. Ironically I just did a reboot to test, and it worked perfectly for the first time (where before each reboot would cause my icons and groupings to separate).
Again, THANKS, and if you need a tester for a fix, or more information I am glad to share.
That is not unexpected as you likely did not change any of your monitor configurations and \ or the monitors cycled up in the exact same order as they had when it worked last.
The core of the issue is how random Windows is with renaming monitors as they are seen (the order) by the OS.
That is not unexpected as you likely did not change any of your monitor configurations and \ or the monitors cycled up in the exact same order as they had when it worked last.The core of the issue is how random Windows is with renaming monitors as they are seen (the order) by the OS. Sean DrohanStardock Product Lifecycle Manager
Ah, got it. Thanks for the explanation, this helps. I am also noticing at times icons aren't pinned to the desktop in the location prior to a reboot, but I have struggled with this when I move between laptop and external monitors (even if I am deliberate in each config to save them where I want them.
Anyway, thanks,DaveR
I have a similar issue but it may not be exactly the same. My icons appear on the wrong monitor, but fences are on the correct monitor. Fences 4 does not restore the snapshot as what's shown in the snapshot thumbnail, it gets confused on where the icons-without-fences should go. I'm on Windows 10.
This started happening after I upgraded to Fences 4 from 3. Fences 3 never had any issue with this. This is important, because this is behavior is new with Fences 4 - at least in my case.
A reboot fixes this issue, but I don't want to boot up my computer and then reboot again for Fences to work.
This is likely because I turn on the monitors after I start the computer - and monitors may get enumerated differently. But Fences 3 never got confused about this. This seems to be a bug in Fences 4.
I also have a slightly unconventional display setup: Display 1 is disabled (no output), while Display 2 and Display 3 are my regular monitors. I don't use any multi-monitor apps or utilities. Just a disabled display in nVidia Control Panel.
Fences 4 doesn't seem to keep up with changing enumeration. But of course, the problem can be deeper than that.
This started happening immediately after I upgraded to Fences 4. No other changes were introduced to my system (no driver updates, no changes to monitors or displays, nothing else was installed or uninstalled).
Hope this helps somehow, but this seems to be a long running issue. I'll try to downgrade to Fences 3 for the time being if I can find the installer.
Hey Fattz,
You would be a prime candidate for users that we are looking to collect some data from in Fences 4 in relation to multi-monitor usage. If you have a chance, please review https://forums.stardock.com/516971/fences-multi-monitor-logging
Thanks!
Paul ScrogginsAssociate Technical Support Analyst
Also just found this post and having the same issues, its even more pronounced while i switched from a AMD to a nVidia GPU.
So basically for me if the monitors go into sleep via power management and i wake them, the one with all my fences needs a bit longer to wake and by this time fences has already moved everything to the main monitor.
I than have to manually power off my main again, than fences switches all to the now "main" aka old secondary. Than i switch my main on again and it kinda looks ok.
What i don't understand that every time this miss-match happens, any attempt to restore a manual "correct" created snapshot fails. It looks correct in the preview picture, but never fixes a wrong layout.
What also usually helps is fully rebooting the system, since than both monitors are active before fences is even started.
PS: Whats also weird is, i have two monitors, each with a different resolution/aspect, yet the restore logic never tries to match this and seems to prioritize using the wrong/changed display id's over any physical identifiers. So i would prefer a "match by resolution + aspect" option, instead of display id's that change, depending on which monitor was turned on first. Than also each monitor has a "display name" and other unique identifies which can be used as a hint, to figure out where fences should restore/go.
For me and others the default/current logic clearly does not work.
I have this exact problem. 3 monitors and the fences shuffle around and get screwed up everytime I start my machine or it goes to sleep. It almost feels random and makes me sad. I end up turning off monitors and restoring a snapshot, but it doesn't make sense always which monitor I turn off to get it to work. I just know it's frustrating. I'm using Stardock Fences 3 and love the concept, but I've probably reset up my fences 30x over the last year just to get them in the order I had before. I really wish there was a fix. The snapshot LOOKS correct, but it always restores them to the wrong monitors...
Help!
There are many great features available to you once you register, including:
Sign in or Create Account
