This is a comment about my new installation of 10.1 beta 3.
It is a good news comment.
I noted on the upgrade to v10 the following issue... I usse Open-Shell Menu 4.4.170 to replace the windows 10 start menu / button, a stable situation for several years. The Windows taskbar is on both primary and secondary monitor, and it is managed by DisplayFusion.
With the v10, the OpenShell start menu button on the secondary monitor would open to the menu - but just in a flash - it would then immediately disappear. on th primary monitor it works normally.
Now, however, with the current beta3 both start menus funtional normally.
Of course I cannot state for sure this was all about Display Fusion but I'm going to give the benefit of the doubt to beta3 and not something else that I had transiently done to my system.....

I installed beta 3 and now I am unable to open Firefox, Chrome and Edge.
If I try to open them, it displays a "Not Responding" message, and anything I type on my keyboard comes out garbled.
I opened notepad and pressed the "q" key repeatedly, and got "123456" as output.
I exited DisplayFusion and everything started working again.
I have uninstalled Beta 3 and am installing Beta 2 to see if that still works.
I will update this message as to the functionality of Beta 2.
Very strange behaviour indeed.
--------- ADDED
Well, I reinstalled DisplayFusion via Steam (that's where I bought it originally) and now it refuses to start.
Rather disappointing, to say the least.
I will restart my machine and see if that makes a change or a difference.
---------- UPDATE
A restart helped.
I had to go into the DisplayFusion settings to enable multi-monitor taskbars again, but that was minor.
It is running now and all is well again.
I will skip Beta 3 for now as it seems to be doing strange things with the keyboard and Chrome, Firefox and Edge.

I have no similar problems with Beta 3... All the other windows programs work normally. I'll wait for the experts to opine but I think I would likely look elsewhere for the blame. Keyboard controls?

This one broke Destiny 2 for me. Major FPS drops and BattlEye (anticheat for Destiny) reporting issues with display fusion dlls. Screenshot attached. Exiting DisplayFusion brings FPS back to max. Haven't tried any other games yet but I can if needed.

Also, don't know when this changed or if it's a DF issue, but when I switch to my living room tv monitor profile, I use a custom resolution to force 1080p 120hz. It used to just switch fine, but at some point it stopped working and only shows a very small window instead of filling up the screen, and defaults to 4k. I have to open the Nvidia Control panel and select/apply the custom resolution.

The 10.1 Beta 3 update broke the setting Taskbar > Taskbar Mode > All taskbars show relevant windows.
Some apps are still displayed in the main monitor's taskbar despite being displayed in a secondary monitor.

Downgrading back to Beta 2 fixes the issue.

I've noticed it with a couple of different apps so far, but they are private and I unfortunately can't share them (work-related).

---

My sister just noticed the same issue with another app she uses to read manga though. You can get the latest 2.0.31.0 version from here: https://github.com/dazedcat19/FMD2/releases

She's using the file fmd_2.0.31.0_x86_64-win64.7z.

Hi Owen

I went through a stupid process of uninstalling DisplayFusion, reinstalling it (via a download) realising that my DisplayFusion is via Steam, uninstalling and finally reinstalling. (My stupidity!)

I will update to Beta 3 and see if the same thing happens, and if it does I will get the file and send it through.

That looks to have done the trick but I'll know more later when I get to play play instead of just launching the title screen (Which had bad mouse lag before I made this change).

Added:
BEService.exe
destiny2.exe
destiny2launcher.exe

Tried just launcher and BEService but what worked was just adding the destiny2.exe. That alone appears to have stopped the issue.

As far as the custom resolution:

Deleted all monitor profiles.
Set custom resolution again in Nvidia Control Panel with correct config (single screen, 4k tv set to 1080p with CVT Reduced Blank, 120hz, HDR off), confirmed this shows correct in Display Fusion then saved monitor profile again. Recreated other 2 profiles (single screen pc monitor for gaming/vr, dual display for daily use).

Edit: Just realized you wanted the DF troubleshooting info. Apologies! Will run and get that to you.

I was incorrect stating it defaults to 4k. It actually defaults to 1080/60 which a supported resolution and not the custom one that I have configured in Nvidia Control panel. Just ran the cycles and grabbed the file which is attached. Thank you for your assistance!

It appears only in the Windows taskbar in the main monitor. I'll add also that the program's icon is pinned to the DF taskbar in the secondary monitor.

Clicking on the icon (with the option to force the app to open in the same monitor as the taskbar) opens it properly, but the taskbar entry shows in the wrong location (Windows taskbar) as mentioned above.

I believe it was working as far into Beta 10. It was only in the last few weeks that I noticed it stopped and I keep auto updates on. I should have said something sooner but figured it was just because I was using a custom res and it might not be fully supported. I figured once it started impacting my gaming sessions I had to reach out lol. No issues in destiny now that the main exe was added to compatibility so thanks for that!

Will do! Thank you!

While i fixed this by going to the stable releases(and therefore cant provide support files rn) i can install the beta again and provide files for it:
basically, since installing Beta 3, if its open, Destiny 2 performance degraded: mouse stutters, dropping frames, etc. While their anti cheat solution always flagged the hook for displayfusion, it never caused any problems.
Either closing it or installing the stable version did the trick, and performance is back to normal.

Beta 3 was the first time it started flagging the hook for me. Didn't happen with previous versions. Weird.

First attempt was successful!

Removed latest with Revo uninstalling purging all leftovers.
Restarted.
Installed provided version and configured monitor profiles. Did the shift and it set the custom res

Will update you if anything changes. Set auto update to off for now.

Gave it a try and found desktop windows slowed to a crawl after a bit of use - uninstalled it.
Might try again at a later date;

Asus Crosshair VIII Hero
AMD Ryzen 5800X3D
G.SKILL Ripjaws V Series 32GB
AMD XTX 7900

Tri-monitor Config: 32" Center + 2x24" Portrait
Single desktop background image spanning all monitors

Bios all defaults, no XMP/OC profiles

My screen saver seems to have changed behaviour with this new update. So I have 2 monitors that pull random photos from a folder to display when the screen saver is on. It has tens of thousand of images, yet now I see the same 20 or so images every time, they also seem sequential, where before it would simply pull a random picture for both monitors.

Titlebar button Minimize Window to Tray is buggy. For multiple Chrome windows, only the most recently minimized-to-tray Chrome window appears in the system tray. Others are mysteriously in limbo. A restart of Chrome restores them, but only the most recently added minimized-to-tray window icon appears in the tray. I've been driving myself nuts wondering what happend to them, or cursing myself for "accidentally closing them".
Debug info attached. Thanks for all you guys do!!

thanks! i shouldve read the thread more throughly. sorry for cluttering it.

Thank you for the help! Everything is working well, dont even need the fix for Battleye!

Done!

Sorry, not possible. I'm under a strict NDA that I can't share anything about those apps. Not even debug logs. However, as long as you guys fixed the issue with the FMD2 app I linked above, it should fix all these others, too.

In case those still won't work after the next beta with a fix for it, I'll see what I can do.

I'll give the new beta a try either later today or tomorrow.

@Owen The taskbar issue is fixed in Beta 4. It works for the Manga app I linked and also for all the private apps I mentioned before.