This is a peculiar bug that I had noticed while I am running different apps thru the DF taskbars.

When I had set the apps to force full-screen, when I launch these programs, they always launch in the primary display where DF is not active. This appears to be particularly problematic when the program is a WindowsApp and DF remembers its fullscreen state. When it isn't fullscreen, it is fine. However, Fullscreen apps, especially when it is set to "Force application to start on same monitor as taskbar" always launches in primary.

DF seems to think for fullscreen apps that the taskbar display is primary and only primary.

I believe that a key source of the problem on my end is the fact that no matter what I do, the prmary display (or display that I need to be primary) is never registered as Display #1 on Windows. It is always Display #2, period and end of story. I have no resolution on that issue.

I hope you guys have a viable workaround.

this happens with apps such as Inkscape, Blender, Paint.NET, Krita, Visual Studio Code and many others. I should note that in my observation this affects programs installed trough AppX, or in simple terms Windows Store.

This is a rather irritating bug that i've had to endure. There has to be some way to stop or prohibit the action.

No, this problem appears to be exclusive to the presence of Displayfusion. Attempting to open Windows Taskbar shortcuts I find to be too limiting for my liking.

I should repeat that i suspect that the root of my issue is a primary-display mismatch on my end that i can do nothing to resolve.

Is there anything in DF that determines the main screen via Windows primary display or display numbers?