Sorry to hear you are having trouble.
According to you, the problem is not caused by Fences but other software. The reason is that it cannot be reproduced, and it is not widely reported. To be honest, I am disappointed by the ridiculousness of this reply.
First, you not being able to reproduce the issue does not mean I do not encounter this issue.
No one doubts you are seeing this issue, Rdwillemse, nor was it implied that we did. What I can say is that in my nearly 11 years at Stardock, I have never seen a report like yours. There are literally 100s of thousands of installs of Fences 4, again, seemingly all without such an issue.
That does not mean that there is not something within Fences that does not need to be looked at, it just means that we need to know what very unique settings \ apps you have that are causing Fences to flip at random like that. That is what basj was doing, using the process of elimination to see if a cause could be found. It's perfectly understandable that you would not want to participate in doing that, but it's also perfectly appropriate for him to ask.
And what if I find software that interferes with Fences? Do you expect me to uninstall that software? If Fences 4 does not work well on laptops with certain software installed, it would have appreciated it when I was informed about this issue before I paid for the update.
Knowing what app may be causing this issue is the priority. When identified, what direction you \ we take would be more clear, yes?
As for your issue....
I would like to start with a Purge \ Reinstall (different than just a regular uninstall):
After, reinstall Fences 4 and see if you can reproduce it.
If you can reproduce...
As you surely know, what causes a Fences to flip is when it detects that its close to a top \ bottom of a monitor, example:
What you seem to be saying is that, randomly, they will just flip, yes? Does that mean you don't even have to be moving them for it to do that, you will just see them flip in use or from a wake?
If there is any app that you can think of that alters monitor scale dynamically, that would be my 1st guess.
Regardless of reproduction steps, does a restart of Windows Explorer work to resolve it?
I will end there for now as knowing that will dictate where we go from here.
Stardock Product Lifecycle Manager