Installing Beta27 broke something with maximized windows - when opening one that's maximized by default or moving one to another monitor, it first opens/moves as unmaximized and then maximizes itself after.
I've rolled back to Beta26 and the problem still persists, but it definitely started when upgrading to Beta27 and I haven't changed any settings or updated anything else since then.
Could you please check what could cause this?
Thanks!

Just did some further testing and it seems it's actually Beta26 that broke this.
With Beta25, the problem is there but not exactly like this.
Beta26: Opening anything that defaults to maximized or moving any window while maximized opens/moves it first then maximizes it ~1s later.
Beta25: Opening or moving Firefox is totally OK, doesn't get unmaximized. However, moving (but not opening) Total Commander still unmaximizes it first but the subsequent maximizing is a lot faster.

Yes, this problem started for me with beta 26. I mentioned it here: https://www.displayfusion.com/Discussions/View/trouble-pinning-notepad-to-taskbar-in-windows-11/?ID=69658e2f-3b8d-4e21-9828-b37934c8ed76#28

Too bad it's still happening with 10 final. I guess I will stick to beta 25 for now..

It seems similar, but for me it's not only happening for hotkeys but also for moving them with a click (bound to middle-click for me) and when manually dragging them too.
And I'm using the same resolution and same everything on all my monitors.

Yes you are right, I experienced this too. I am also using a click (mouse-button 4), which I called a hotkey. I think we are talking about the same issue.

Here it goes, showing the problem with Beta27 in the second file.
Made one with Beta25 for comparison (19-35-02).

Firefox seems to have been fixed in 10.0.1-Beta1 but Total Commander is still not quite right, and Notepad++ behaves the same (~1s delay). The latter is already like that in Beta25 though (and probably some more apps I haven't tested yet).
I'd rather not try every earlier version to try and figure out when this was introduced, but I'm willing to try some of them if you have an idea about some culprits (and download links for them since I don't seem to be able to find them anymore).

Sure, here you go. Hope this helps.

Sure, there it is.

I'm having a parallel problem with opening program windows maximized - they should open maximized but don't always. This is currently seen in my Eudora program - it opens in 'normal' window then maximizes - but of course while doing so it reorganizes menus/tabs into the position they would be in a 'normal' window, not the maximized. I'm pretty sure as well this is a recent change.

I have attached the file as suggested!
Thanks R

Well, now I'm confused.
It turns out that a similar thing happens with a file management program called Xplorer2 (www.zabkat.com). But not with some of his other programs.
I rolled back to v9.7 and the same thing was happening. But... then I uninstalled the Displayfusion altogether and did a registry scan/clean thing to ensure there was no vestiges.... And the same thing happens!
I don't understand this at all and I do think that it is new, that I would have noticed it before because as I previously mentioned when Eudora opens in this fashion it rearranges the toolbar (too wide for the non-maximum window) and I would surely have noticed that.
So at this point I'm going to take the pointing finger away from DisplayFusion and say that either I'm not so smart and not noticing things, or some other process is interfering with windows in this fashion.
And I'm going to try not to worry about it as it isn't the biggest complaint in the world.
thanks for your help as it is to this point.

Thanks for the update, looking forward to test the new stuff.

Firefox is still OK, but the others are still slow to maximize (not that extremely bad though, they went from a ~1s delay to ~0.5s).

Thanks! I will check and report whenever new versions arrive.

For me, it all seems good with the latest beta

This is still happening and getting worse with every new version.
I'm trying 10.1.2-Beta1 right now and every maximized window moves this way, most of them with a ~0.5s delay while Firefox takes more than a second to maximize after moving.
Is there anything you can do to fix this?

Sure thing, here it is.

Timestamp: 15:47
1. Firefox with keybind: unmaximized and delay to maximize
2. Firefox with middle-click: unmaximized and very big delay to maximize
3. Thunderbird with keybind: unmaximized and (not that very big ) delay to maximize
4. Thunderbird with middle-click: unmaximized with big delay AND delay to maximize
5. Total Commander (both keybind and middle-click): unmaximized and (not that very big) delay to maximize

Everything else I've tried works the same as Total Commander.

Hope this helps!

Yes, unfortunately this is still happening

Attached.
I did the same test as last time:

Timestamp: 18:45
1. Firefox with keybind: unmaximized and delay to maximize
2. Firefox with middle-click: unmaximized and bigger delay to maximize
3. Thunderbird with keybind: unmaximized and (not that very big ) delay to maximize
4. Thunderbird with middle-click: unmaximized and delay to maximize
5. Total Commander (both keybind and middle-click): unmaximized and (not that very big) delay to maximize

I shall note that the delays are now shorter than they were in the previous version so there's definitely progress, but it's still there and pretty annoying.

Hope this helps!

I have not been having the problems recently but I did download and install the new beta - and still not seeing any issues. I've attached my log anyway.
Thanks Richard

Tested this with the new beta and now it's even worse than the previous version.
Symptom is the same as described above, tested with Thunderbird, Firefox and Total Commander. The delay is even bigger than it was in beta3.

Sure, there you go.

Sorry, somehow I downloaded another version earlier. Here is the file from Beta4.

I have disabled every startup app (except ESET which cannot be disabled), restarted the PC and launched DF manually.
Nothing changed.
The behaviour is exactly the same, with Beta4 being significantly worse.

Just tested beta5 and this is now extremely bad, still getting worse with every new version

This is good progress, now we know the cause and you can reproduce it, nice!

Thank you for the update!

This issue is still present in Beta7.

This issue is still present in Beta8.

Still present in Beta10.