DisplayFusion RSS: Failed to call SetDisplayConfig. [HR: 31] when Re-enabling monitor

DisplayFusion RSS: Failed to call SetDisplayConfig. [HR: 31] when Re-enabling monitor https://www.displayfusion.com/Discussions/RSS/?TopicID=ad2b4fd6-dd74-4900-b9fd-e941d409baeb DisplayFusion RSS: Failed to call SetDisplayConfig. [HR: 31] when Re-enabling monitor Thu, 09 Apr 2026 11:10:26 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=ad2b4fd6-dd74-4900-b9fd-e941d409baeb RE: Failed to call SetDisplayConfig. [HR: 31] when Re-enabling monitor https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31-when-re-enabling-monitor/?ID=ad2b4fd6-dd74-4900-b9fd-e941d409baeb#10 Thu, 01 Dec 2022 19:24:39 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31-when-re-enabling-monitor/?ID=ad2b4fd6-dd74-4900-b9fd-e941d409baeb#10 DisplayFusion Hello,

We've made some changes to our monitor configuration code that should fix this up in our latest beta, as described here: https://www.displayfusion.com/Discussions/View/monitor-configuration-backend-completely-revamped-in-displayfusion-100-beta-18/?ID=b17dacd1-0611-48c1-a29c-3a3e5046812a

Please let me know if you run into any issues after updating.

Thanks! ]]> RE: Failed to call SetDisplayConfig. [HR: 31] when Re-enabling monitor https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31-when-re-enabling-monitor/?ID=ad2b4fd6-dd74-4900-b9fd-e941d409baeb#9 Tue, 22 Nov 2022 03:13:15 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31-when-re-enabling-monitor/?ID=ad2b4fd6-dd74-4900-b9fd-e941d409baeb#9 DisplayFusion FYI, this exact thing has happened to me for the 5+ years I've been using DF, I've just never taken the time to submit a forum post about it. I can't believe I found this article 6 days after your message about a backend updating happening soon. Here is hoping!! ]]> RE: Failed to call SetDisplayConfig. [HR: 31] when Re-enabling monitor https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31-when-re-enabling-monitor/?ID=ad2b4fd6-dd74-4900-b9fd-e941d409baeb#8 Tue, 15 Nov 2022 20:02:57 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31-when-re-enabling-monitor/?ID=ad2b4fd6-dd74-4900-b9fd-e941d409baeb#8 DisplayFusion We've got some major backend changes coming to the monitor config code for the next beta that should fix this up. We'll follow-up as soon as it's available to try out.

Thanks! ]]> RE: Failed to call SetDisplayConfig. [HR: 31] when Re-enabling monitor https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31-when-re-enabling-monitor/?ID=ad2b4fd6-dd74-4900-b9fd-e941d409baeb#7 Tue, 15 Nov 2022 02:24:10 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31-when-re-enabling-monitor/?ID=ad2b4fd6-dd74-4900-b9fd-e941d409baeb#7 DisplayFusion Was this issue resolved? I am seein the same error and experiencing this. My guess is maybe some issues with identifying the monitor when off? ]]> RE: Failed to call SetDisplayConfig. [HR: 31] when Re-enabling monitor https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31-when-re-enabling-monitor/?ID=ad2b4fd6-dd74-4900-b9fd-e941d409baeb#6 Wed, 02 Mar 2022 16:17:31 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31-when-re-enabling-monitor/?ID=ad2b4fd6-dd74-4900-b9fd-e941d409baeb#6 DisplayFusion Hi André,

Thanks for sending that over. DisplayFusion uses the Windows API to set the monitor configuration, so if it works through the Windows display settings, it should be working through DisplayFusion too.

Could you send me over a debug log? Here are the steps:

On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
Reproduce the issue and note the time so we'll know where to check in the log file
Click the "Export Info to File" button on the Settings > Troubleshooting tab
Reply with the file attached
Disable debug logging after sending the log

Open the Settings > Troubleshooting tab
Click the "Export Info to File" button
Reply with the file attached

Thanks! ]]> RE: Failed to call SetDisplayConfig. [HR: 31] when Re-enabling monitor https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31-when-re-enabling-monitor/?ID=ad2b4fd6-dd74-4900-b9fd-e941d409baeb#3 Fri, 25 Feb 2022 19:48:21 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31-when-re-enabling-monitor/?ID=ad2b4fd6-dd74-4900-b9fd-e941d409baeb#3 DisplayFusion Yes
When I disable it is under option "only on monitor 1"
then I change back to "extend to both monitors" and it works. ]]> RE: Failed to call SetDisplayConfig. [HR: 31] when Re-enabling monitor https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31-when-re-enabling-monitor/?ID=ad2b4fd6-dd74-4900-b9fd-e941d409baeb#2 Fri, 25 Feb 2022 19:15:29 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31-when-re-enabling-monitor/?ID=ad2b4fd6-dd74-4900-b9fd-e941d409baeb#2 DisplayFusion Hi André,

Are you able to manually enable that monitor through the Windows Display Settings?

Thanks! ]]> Failed to call SetDisplayConfig. [HR: 31] when Re-enabling monitor https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31-when-re-enabling-monitor/?ID=ad2b4fd6-dd74-4900-b9fd-e941d409baeb Fri, 25 Feb 2022 16:57:15 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31-when-re-enabling-monitor/?ID=ad2b4fd6-dd74-4900-b9fd-e941d409baeb DisplayFusion I am able to disable a second monitor and stick with one screen.
However I can't use DisplayFusion (manually or via profiles) to re-enable that screen.

Some insane flickering happens for a few secs and then I get the error message "Failed to call SetDisplayConfig. [HR: 31]" forcing me to switch back to only one monitor enabled.

Is this a known issue? How can I make it work inside DisplayFusion?
Turnaround I found was re-enable it on Nvidia CPanel then re-apply the DF profiles.

Setup:
Windows 11
Software v9.9 (Steam)
RTX 3070
1 - DELL S2722DGM on DP @1440p 165hz
2 - ASUS VG278 on DP @1080p 165hz
Both w/ GSYNC active (Dell is not certified, while ASUS is) ]]>