In Windows 10, one of the new features was the ability to cycle between multiple desktops/workspaces. I could have general web browsing and such on one setup, and then hit Win + Tab to look at the various workspace possibilities. In regular Windows 10, a workspace is assigned to the entirety of your dual/tri/whatever-monitor setup. So, I would be able to be browsing Facebook on one monitor, and playing Minecraft on the other. When I would hit Ctrl + Win + Right Arrow, it would bring me to workspace #2 where I have my programming IDE and such running. However, when I launch DisplayFusion, it appears as if it "breaks" this workspace feature on my second monitor, as the the two workspaces are identical now. This is shown in the attachment and posted image here.

So when can we expect this fix?

Just replying to get a notification when the issue gets addressed.

2017... still an issue.

2017... still an issue.

2018, still an issue.

After 3 years, I'm guessing the devs never intend to fix this.

This is a huge issue for me as well and a deal breaker. Until now I wasn't using MultiDesktop, but now it is crucial for my work.
After I was this thread years ago I was hoping it will get resolved.
If I knew DisplayFusion cannot and won't ever resolve this issue I would've gone with a different solution. This is very crucial feature of windows and just cannot be left like this.

For me, Keith's suggestion actually enhanced my usage of DisplayFusion. Doing so allows me to use the Windows taskbar on my primary monitory as a sort of home base, showing every item regardless of location. Then all other monitors using DisplayFusion taskbars only show relevant items.

Since you appear to be at the mercy of Microsoft, here's some other options ya'll could implement for "All taskbars show relevant windows".

Since the bug only occurs on multiple desktops where DisplayFusion taskbars are used, you could have an option to only use DF Taskbars on one desktop of the users choice (or just default to the primary desktop). You'd only have DF functionality on the first desktop, but at least you get multi-desktop back. This is assuming it's possible to differentiate desktops programmatically.

Another alternative might be to disable the Windows taskbar entirely, so you don't have to perform the offending API call to remove buttons from it. From what little I've read, doing so requires replacement of File Explorer and other shell functionality, and surely ya'll would have done this already were it a simple operation.

Just some thoughts. Cheers