Fences 4 not keeping their position with RDP

I am having a similar issue to what I had back with Fences 3 where they will not keep their position. I am running Fences 4 on a headless Windows 10 22H2 workstation which I RDP in to from my MacBook Pro using Jump Desktop. No matter how I adjust the Fences, as soon as I close the RDP desktop (I do not log out, just disconnect) and open the session back up, the Fences will lose their position. 

Here is how I had them adjusted originally:

I simply disconnected the RDP session and immediately reconnected and here is what they look like after:

Here are the layout settings:

I've tried using "Preserve my desktop layout by scaling my Fence groups" but I end up with the same problem.

 

14,328 views 15 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. Please try reading this thread, and try the last reply (Reply#3) suggestion: https://forums.stardock.com/503620

Thanks
Basj,
Stardock Community Assistant.

Reply #2 Top

That is what I am doing now, restoring the snapshot every time I connect in but that gets very old, especially since I reconnect 10 to 15 times a day. Is there a way to fix the issue so that I don't have to do that?

Reply #3 Top

Hello,
I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #4 Top

Hi Tonym3,

Your situation seems to be exactly the type that we have been looking for for our "Multi-Monitor" logging data collection (even if this is not a multimonitor situation, it should still log the changes). Please review this link: https://forums.stardock.com/516971/fences-multi-monitor-logging

And if you have time to contribute some logs, that would be a great help to be able to improve Fences in the future

Paul Scroggins
Associate Technical Support Analyst

 

 

Reply #6 Top

Quoting sergedornseiffer, reply 5

I have the same issue since years. Any solution?
End of sergedornseiffer's quote

Hello,
Sorry to hear you are having issues. Which Fences version you have on?

Thank you.
Basj,
Stardock Community Assistant.

Reply #8 Top

Quoting sergedornseiffer, reply 7

I had the problem in V3 and now also in V4 (latest update). I have no trust that V5 is any better
End of sergedornseiffer's quote

Hello,
I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #9 Top

Quoting sergedornseiffer, reply 7

I had the problem in V3 and now also in V4 (latest update). I have no trust that V5 is any better
End of sergedornseiffer's quote

Thanks for that feedback, sergedornseiffer.

However, since you do have access to Fences 5 (and the 5.5 Beta in particular that has modifications to address monitor issues), is there a reason you are not choosing to participate in the discussion here?

https://forums.stardock.com/527284/fences-55-beta-feedback-thread

Sean Drohan
Stardock Product Lifecycle Manager

Reply #10 Top

This is the first time I hear about Version 5 solving my problem. Thank you for this information. I will test Fences 5 and see if it solves my issue.

Just to explain that I do not mind buying Version 5 at all, on the contrary I always like to be up to date. My point was that I refuse to buy a new Version if I know that a bug exists and that is not solved. I have checked the forums and I am not the first one to complain about it.

Best regards

Serge

Reply #11 Top

Quoting sergedornseiffer, reply 10

I have checked the forums and I am not the first one to complain about it.
End of sergedornseiffer's quote

You are also not the 1st to be affected by how Microsoft has poorly managed their desktop - including Microsoft themselves

https://www.pcworld.com/article/394488/microsoft-is-finally-fixing-windows-most-annoying-multi-monitor-bug.html

Sean Drohan
Stardock Product Lifecycle Manager

Reply #13 Top

Hello. A little feedbackup after testing Fences 5.51.

The issue seems to be solved. I have tried on multiple machines and it all as it should be.

 

Thanks to anyone involved in solving the issue and also to sdrohan.

 

Best regards

Serge

Reply #14 Top

I can confirm 5.5 has fixed my issue as well

Reply #15 Top

Quoting sergedornseiffer, reply 13

Hello. A little feedbackup after testing Fences 5.51.

The issue seems to be solved. I have tried on multiple machines and it all as it should be. 

Thanks to anyone involved in solving the issue and also to sdrohan. 

Best regards

Serge
End of sergedornseiffer's quote

Quoting tonym3, reply 14

I can confirm 5.5 has fixed my issue as well
End of tonym3's quote

It is hard to express how much this pleases us to read.  Thank you both very much for the feedback, time, and support.

Sean Drohan
Stardock Product Lifecycle Manager