As the title indicates, since moving to Windows 11, nothing seems to work under Monitor Configuration. Any attempt to change any setting for a monitor results in the error:
Error
Failed to call UpdateModesAndPathsWithMonitorsTHROWS.
[System.Exception]
Attempting to split a monitor looks ok, but when I click apply it just reverts my changes.
I'm currently on DF Pro 10.0 Beta 6, but the problem existed before this version as well.
This was the main feature I wanted from Display Fusion so any help would be greatly appreciated.

As a follow up I cranked up the logging and found this:
2021/10/25 11:44:08.5823##_##WARN:L1##_##displayfusionsettings.exe:26464##_##BFMonitorEnumWin10:GetMonitorsRaw:110##_##-##_##[GetMonitorsUITHREADONLY:BFPublicData:Constructor:GetMonitors] Monitors have changed [NoPathCache], processing.##_##-
2021/10/25 11:44:08.5878##_##FAIL:L1##_##displayfusionsettings.exe:26464##_##BFMonitorEnumWin10:GetMonitorsRaw:293##_##-##_##GetMonitorsUITHREADONLY:BFPublicData:Constructor:GetMonitors, Unknown OutputTechnology: 17, [System.Exception]##_##-
2021/10/25 11:44:08.5878##_##FAIL:L1##_##displayfusionsettings.exe:26464##_##BFMonitorEnumWin10:GetMonitors:663##_##-##_##Reason: GetMonitorsUITHREADONLY:BFPublicData:Constructor, Failed to call GetMonitorsRaw., [System.Exception]##_##-
2021/10/25 11:44:08.5878##_##WARN:L1##_##displayfusionsettings.exe:26464##_##BFMonitorEnumWorker:GetMonitorsUITHREADONLY:42##_##-##_##[BFPublicData:Constructor] TimerUpdateFail: Start##_##-
2021/10/25 11:44:08.5883##_##FAIL:L1##_##displayfusionsettings.exe:26464##_##BFMonitorEnumWorker:GetMonitorsUITHREADONLY:83##_##-##_##Reason: BFPublicData:Constructor, Monitors is NULL., [System.Exception]##_##-
It looks like one or more of my monitors are causing some sort of issue for DF.

Attached as requested

Yes. It started right after the upgrade. The setup was the same under Windows 10 but everything worked fine. I'm guessing Windows 11 is returning some extra information that the program doesn't recognize (like some new flag.)

Updated to the latest NVIDIA drivers. Same result. Logs attached.

No, no compatibility settings and I even tried a clean install to make sure there were no bad settings lingering around.

Attached

Good News! I finally figured out how to fix this.

I wrote a test app of my own to enumerate the display devices and saw a "Virtual Display Adapter".

Going into device manager and enabling show hidden devices revealed that indeed such a device was present. Disabling that device caused DisplayFusion to start working properly again.

Attached are updated logs from the BTCustomerTest. In the future you may want to do something to skip bad devices like this.

Correction: I have not installed TeamViewer (wasn't what I thought).