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.

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.

#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. 

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

Snapshots you mean?

https://support.stardock.com/space/SHC/1416626186/Fences+Settings+%26+Snapshot+Management

Sean Drohan
Stardock Product Lifecycle Manager

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.

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.

Another quick update from me:   The "bunching up" problem was resolved when I ran the Purge Fences batch file.

This thread (and others) should be considered proof that we are, yes.

Sean Drohan
Stardock Product Lifecycle Manager

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 Drohan
Stardock Product Lifecycle Manager

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.

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.