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.
I used Fences 3 for years on two monitors with no problems. Earlier this year I swapped my two monitors for one very large monitor and everything continued to work fine. However, I missed not easily being able to get into another program so I added a second monitor. The addition of a second monitor has been a giant hassle. My carefully constructed fences on my larger monitor nearly always get relocated to my substantially smaller monitor on system startup each morning. Using snapshot to restore often doesn't work. The fences get relocated to the smaller monitor at next bootup even if the smaller monitor is turned off when I shut down the computer.
These are things I have tried: locking the fences setup, which I would think would stop the fences from being moved at all but does not.
Rearranging the desktop to add more space between various fences but fences still get moved to my smaller monitor.
Upgraded to Fences 4 but fences still get moved.
If someone has a permanent fix for this please point me to it. I am hoping for a fix from StarDock that doesn't require the user to edit html or other coding magic.
Thanks.
I, as I suspect everyone does, also have this issue of Fences moving Fences. I am running Win 11 and Fences 4, both fully up to date. I have three monitors; 1, 2, 3. Primary Monitor is 2. The fences on 3 usually, not always, and not always all of them, end up on 2 .
As an added bonus, folders and files on 1 often, but not always, and not always all of them, move to 2.
Did this issue ever get resolved?
I am having the same issue with multiple monitors (fences on wrong monitor after wake).
It appears to me as if the developer is not interested in fixing this issue for the growing number of people using multiple monitors. It has been issue for nearly a year and Fences 4 does not stop this from happening. I would warn anyone running multiple monitors to not install this program. It is too much of a hassle to routinely have to "FW" your personal desktop layout to keep it organized the way WE want.
That is just not the case. It is being actively investigated.
That would be doing a disservice to the people who - like the vast majority of Fence installs that do not have the issue and never have - would greatly benefit from the use of Fences.
We understand that it is a frustrating issue for the clients that do see it and, again, we are working on it.
Sean DrohanStardock Product Lifecycle Manager
I have the same issue using Fences version 4.0.7.2.
I don't want to switch my monitor cables because one cable is thunderbolt/USB-C and the other is HDMI, and the HDMI cable would barely reach my 2nd monitor. I have a two monitor setup.
I am tired of having to keep re-positioning the fences. I would like to what the status is on this issue. I would be willing to meet on MS Teams and run any diagnostic software.
For me, the issue occurs when restarting my PC, and also when waking the PC from hibernation.
I am facing the same issue as a multi-monitor user, and it's a dealbreaker for me. I kindly request the Fence development team to find a solution for this problem.
Hello,Sorry to hear you are having issues. Stardock is looking into this issue. If you wish, you can contribute to help with it. Please refer here : https://forums.stardock.com/516971/fences-multi-monitor-logging
Thank you.Basj,Stardock Community Assistant.
All,
I have written up a 'Winkey + P' test here and would like your feedback on it regarding this issue:
https://support.stardock.com/space/SHC/1344503818/Fences+going+to+wrong+monitor+after+reboot#Winkey-+-P
Thanks,Sean DrohanStardock Product Lifecycle Manager
Hello;
I have the same issue, I have been redirected to this thread.... and I see that more people have this problem and there is no normal ' permanent solution.
In my case there is an additional variable:
- I use various screen setups (home, office, extra screens via USB-C or HDMI, various projectors.....)
- I want ma fences ALWAYS on my main - embedded laptop screen
Do we have a solution how to do it?
Hello,Sorry to hear you are having issues. Have you tried Sean Test mentioned in Reply #34? Try that and report back.
ThanksBasj,Stardock Community Assistant.
Right-clicking the title bar, hovering over "View", and selecting "Lock Fences" fixed it for me.Also, I have "Store my Fences' positions on a per-screen resolution basis" selected but I don't think that is what fixed it for me.
I've had this issue for years as well. I just applied the settings you suggest in your "Win+P" post. After changing to PC Screen Only then back to Extend (following the "Store my Fences' positions on a per-screen-resolution basis", the Fences I have set up do snap back to their original locked position. I have bookmarked this thread and will report back once I have been through a sleep mode incident when Fences has always failed and let you know. Thank you for putting effort into this. I don't know of a good option for me to this software and count on it working all day, every day.
Fences appears to use the color management identity numbers. These can change when the monitors wake from sleep.Fences needs a way to use the Windows 11 Monitor identity numbers because these do not change when the system or monitors wake from sleep.
Sean, have you experimented with using the Windows 10 or Windows 11 Identity numbers instead of the Color Management numbers? Seems like this would do the trick and should be fairly easy to modify the code using a Find/Replace in a sandbox environment.
I know it would be nice if Windows would keep the two in "sync" but its pretty clear that if Fences were to source the Display Numbers from Windows instead of from Color Management, this issue would likely be resolved. Seems like a simple solution to an extremely frustrating problem.
*Update: I realize now that it may not be that simple. With a little more digging, my understanding is that when any application request the Display number from Windows, Windows is choosing to return the Color Management number instead of the Display Configuration/Resolution number, so its a Windows problem. Anyway you can bypass that and pull the Display Numbers directly from the Display Configuration/Resolution registry?
Same issue here and not only after rebooting, but after waking up from sleep (sometimes).The 'Winkey + P' test didn’t work in my case unfortunately.Windows 11 22H2 OS Build 23451.1000 and using 2 monitors + Fences 4.10.06.
I have had a couple of failure to wake up (Windows) issues and a forced restart, and so far, Fences has recovered its position for 7 fences over my three monitors! WIN+P / Per Screen Basis for the win thusfar - thank you.
I had hoped locking would work, but it definitely does not (not for everyone, at least). Just had it swap monitors after waking from sleep. It's impossible to say if it reduces the frequency of this bug.
1 year later...
Stardock.. what is status on this bug?? Soon have a fix ready insted of workarounds? This issue still persists.
I am afraid there is nothing new to report on this.
Hello,
I have exactly the same problem with 4 monitors in version 3. Even an update on version 4 did not help!
It is slowly even getting worse over time, I now not even can store a snapshop and then restore it. Always a very old configuration is restored and not the newest one I selected for restoring.The money I spent i just thrown out of the window, do not buy this software it is not worth its money and it produces only anger!!!
Hello,Sorry to hear you are having issues. But can you elaborate on you can not save a snapshot? Have you tried deleting off old configuration that you're not working and create a new one and see if the new one work?
I can only recommend this Warnung!
I guess Stardock is only intetested in earning money and not in fixing reported errors in their product!
Even the most casual glance at our forums and product history pages would show that not to be the case, urskeiser.
Multi-monitor issues are not unique to Fences; MANY products suffered from how Microsoft has chosen to identify them post reboot \ sleep.
That said, we continue to work on the issue and hope to have a workable solution soon.
Has this been fixed yet? I'm going to try downgrading back to 3 and see if that works. Very frustrating turning on my computer everyday and having to drag a dozen fences to the correct monitor. Still not sure what I paid for when I upgraded.
I'm on 3.1.3.3 and Windows 10 and can confirm that the issue is present here too, so don't bother. I've stopped caring about the new features Fences offers because this issue is so frustrating.
I have a relatively simple setup with 2 monitors and 3 fences on a single monitor, and whenever the problem shows up, 2 of them disappear completely and the third moves to another spot (the same one consistently) on the same monitor every time.
It's hard to troubleshoot this because as mentioned by another person, the issue doesn't arise consistently. I can go a week with rebooting and the fences appear normally, and then have a few days straight where my fences are broken. If two thirds of my desktop icons are potentially missing on each startup, it's hard to rely on Fences as a product, let alone justify the upgrade cost, nominal as it may be.
There are many great features available to you once you register, including:
Sign in or Create Account
