DisplayFusion RSS: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/RSS/?TopicID=b4c58b2d-d636-485e-8606-23a79b1659f9 DisplayFusion RSS: Error: Failed to call SetDisplayConfig. [HR: 87] Thu, 30 Apr 2026 16:50:49 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=b4c58b2d-d636-485e-8606-23a79b1659f9 RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#34 Mon, 25 Jun 2018 15:40:23 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#34 DisplayFusion Thank you for the answer. I'll keep searching for the source of the problem. ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#33 Thu, 21 Jun 2018 18:38:26 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#33 DisplayFusion @Ludovic: We likely can't do anything there, as it sounds like an issue with the drivers and/or Windows not detecting the display properly :( ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#32 Tue, 19 Jun 2018 16:37:23 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#32 DisplayFusion Hello, I've had that problem for a a few month now.
I have 3 screens plugged on my graphic card : 2 monitors and a TV. I use hotkeys to switch setups. If I turn the computer with the TV off and turn it on later, I have that error. I can for force the detection with Nvidia control pannel but then the TV sound output is not detected.
The only fix I have found is to reboot the computer with the TV on.

I've tried reinstalling Display Fusion and Windows 10 but nothing worked. I have the latest version of Display Fusion through Steam. ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#31 Tue, 05 Jun 2018 12:44:44 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#31 DisplayFusion I just installed the 9.2.4 (beta 1) released on June 1 and my problem appears to have been fixed. Thanks! ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#30 Fri, 01 Jun 2018 13:09:09 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#30 DisplayFusion @David: Your issue will be fixed in the next beta, which we're hoping to release today :)

@border: Could you send us a support request using DisplayFusion (Settings > Help > Support Request) for this issue?

Thanks! ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#29 Wed, 30 May 2018 16:06:24 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#29 DisplayFusion
Quote:
@border: You mentioned 9.2.1, are you still having this issue in 9.2.2 as well?


Yeah, problem persists in 9.2.2 ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#28 Tue, 29 May 2018 18:38:31 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#28 DisplayFusion @border: You mentioned 9.2.1, are you still having this issue in 9.2.2 as well? ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#27 Tue, 29 May 2018 14:07:04 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#27 DisplayFusion Just thought I would chime in to say that I am having the same issue since 9.2.1 using Nvidia. I don't really have much more to add though unfortunately. It happens with hotkeys and manually switching profiles, and the only way I have found to fix it is to enable all three monitors through windows first. ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#26 Tue, 29 May 2018 00:33:37 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#26 DisplayFusion Here you go. ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#25 Mon, 28 May 2018 15:00:54 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#25 DisplayFusion @David: Could you attach a copy of your troubleshooting info?
  • Open the Settings > Troubleshooting tab
  • Click the "Export Info to File" button
  • Reply with the file attached
]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#24 Sat, 26 May 2018 18:24:44 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#24 DisplayFusion For me, 9.2.2 created the problem.

I've been using DisplayFusion for years on VirtualBox headless VMs accessed via Remote Desktop. These are Windows 10 Pro (version 1803) guests running on Windows 10 hosts with the same OS. Display Fusion has always worked just fine. Yesterday I ran the update to 9.2.2. and it broke. If I run the VM in standard (not headless) mode, DisplayFusion works fine. But under remote desktop, Wallpaper profiles stopped working. All options on the Desktop Wallpaper settings app are greyed out. The taskbar manager still seems to work OK.

My Virtualbox VM is configured for one screen, and I have the remote desktop connection configured to span across all monitors. The VMs are running the Oracle VirtualBox Display Driver.

I've attached a screen capture of what I'm seeing. ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#23 Fri, 25 May 2018 19:46:45 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#23 DisplayFusion We've just released 9.2.2 that should fix this up for good. Could you update again and let me know? ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#22 Fri, 25 May 2018 19:25:13 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#22 DisplayFusion I am having the same issue now after the last update yesterday 05/24/2018.

The update ran while I was connected to the computer using TeamViewer. ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#21 Thu, 23 Feb 2017 20:17:40 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#21 DisplayFusion This is even worse. After that I see 2 more displays in display panel. And they have uncorrect resolution. After few try to switch active display desktop stop responding and I need to restart PC. I will change the displays manualy it would be faster than type here ;) ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#20 Thu, 23 Feb 2017 18:29:38 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#20 DisplayFusion If you guys enable the "Monitor Configuration: Use Classic Get/Set Functions" option in the Settings > Advanced Settings window, does that help at all? You might need to re-save the profiles after enabling that setting. ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#19 Mon, 20 Feb 2017 20:41:44 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#19 DisplayFusion Have received this message today when switching between profiles. Laptop running Intel graphics, second monitor is usb powered (AOC brand). Also have had issues with the windows task bar not auto hiding and DF not opening when clicking the task bar button. Can't change it in MM either.
Let me add originally using hotkeys - when first set up switched to profile for extending monitor, but got this error message when trying the hotkey to go back to clone profile. ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#18 Sun, 19 Feb 2017 21:25:22 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#18 DisplayFusion I resaved the profile, tried to switch via "DisplayFusion Monitor Configuration" and it worked. But after restart it is same. I must switch it via Nvidia panel to the 120Hz monitor. When I to switched back to 21:9@60hz monitor it switch but shows me the same error. And after it want switch back via shortcut or DisplayFusion Monitor Configuration. ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#17 Thu, 09 Feb 2017 21:29:09 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#17 DisplayFusion Ok, if you re-save the profiles, then try switching using the Load Profile button in the DisplayFusion Monitor Configuration (instead of the hotkey or tray icon menu), does that make any difference? ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#16 Thu, 09 Feb 2017 19:22:30 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#16 DisplayFusion I tried both, hotkey and panel from taskbar. It only give me the error if I go from 21:9@60hz to 16:9@120hz. In oposite direction is ok (hotkey and panel). ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#15 Thu, 09 Feb 2017 19:03:06 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#15 DisplayFusion @David: Are you switching using hotkeys? ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#14 Wed, 08 Feb 2017 16:02:36 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#14 DisplayFusion Hi I recieved the same error "Failed to call SetDisplayConfig. [HR: 87]". I have one monitor 2560x1080 21:9 @ 60Hz and the second is 1920x1080 16:9 @ 120Hz. When I change it from the ultrawide to fast monitor I recieved the error. Please help. ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#13 Sat, 10 Jan 2015 19:54:13 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#13 DisplayFusion I've started having the exact same problem with my third monitor after updating my AMD drivers today. Was a fix ever found? ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#12 Tue, 16 Dec 2014 19:08:49 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#12 DisplayFusion very shortly i will have a second GPU installed. since it wont be crossfired (it's staying in for folding@home) i'll just connect my 3rd monitor to that one. once i do that i'll report back with my findings. obviously getting a 2nd video card isnt a great option for most users, but maybe i can shed some more light on the problem if nothing else. i seem to be able to reproduce the issue even with DF uninstalled, so it's certainly a driver or hardware issue.

on another, possibly related note, i've had installation of the newest drivers fail on me several times. every time it went to detect the displays it would crash and install would fail. once it even BSOD and restarted on me. eventually just installed in safe mode with one monitor plugged in. ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#11 Tue, 16 Dec 2014 19:01:04 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#11 DisplayFusion Ok, we were indeed able to reproduce this issue here, but it definitely seems to be an issue with the AMD drivers. When we tried to enable the third monitor with the Windows screen resolution settings, it seemed like it applied (it was showing the "Would you like to revert to the previous settings" dialog and everything), but the monitor didn't actually get enabled. The only way to reliably enable it was through the Catalyst Control Center :( ]]> RE: Error: Failed to call SetDisplayConfig. [HR: 87] https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#10 Fri, 12 Dec 2014 20:26:11 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=b4c58b2d-d636-485e-8606-23a79b1659f9#10 DisplayFusion I think we were able to reproduce this here (at least, we were able to reproduce the same error under similar circumstances), and it definitely seems to be related to the AMD drivers. We're still investigating, but we'll definitely let you know when we're able to get this fixed up.

Thanks guys! ]]>