Title

Message

Confirm

Want to earn a free DisplayFusion Pro license? We're looking for DisplayFusion translators!
<< DiscussionsReply

Error: Failed to call SetDisplayConfig. [HR: 87]

Avatar from Gravatar.com
Joakim Nilsson
4 discussion posts
I have been using displayfusion for a few years now and its worked fine but yesterday i started getting this error when trying to switch monitor profiles:

"An error has occurred while applying your new Monitor configuration. Please check your settings and try again. Error: Failed to call SetDisplayConfig. [HR: 87]"

Only thing i can think off that might be setting it off is either the new beta build (rolling back doesnt fix it) or a new display driver.

EDIT: Seems to have something to do with the 3rd monitor. All profiles without this one seems to work. I can manually start it through CCC which is weird.
Nov 25, 2014 (modified Nov 25, 2014)  • #1
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Interesting! Are you able to enable the third monitor using the Windows Screen Resolution settings, or does it error out there too?
Nov 26, 2014  • #2
Avatar from Gravatar.com
Joakim Nilsson
4 discussion posts
Enabling it through Windows Screen Resolution works fine but i need to restart the monitor after a failed profile switch. Tried to manually redo all the profiles with no effect. Im starting to wonder if it has something to do with the new amd beta drivers.
Nov 27, 2014  • #3
Avatar from Gravatar.com
James Stansell
10 discussion posts
anyone ever find a solution to this? i seem to be having the same problem. it's not AMD beta drivers, i'm using the stable release. i'm currently running DF beta 10 (downgrading from 11 didnt help), start8, modernmix. was using windowfx which i uninstalled but that didn't help the issue. i'll try uninstalling all the stardock apps and report
Dec 5, 2014  • #4
Avatar from Gravatar.com
James Stansell
10 discussion posts
it is almost certainly an issue with a 3rd monitor connected. physically unplugging the 3rd monitor made the issue disappear.
Dec 5, 2014  • #5
Keith Lammers (BFS)'s profile on WallpaperFusion.com
That's interesting! Which AMD video card are you guys using?
Dec 8, 2014  • #6
Avatar from Gravatar.com
Joakim Nilsson
4 discussion posts
I have a sapphire r9 290.For me the problem seems to be that when i activate a profile with the monitor that DF calls 3 which i connected to my 2nd DVI port i wont work. I can however activate it through windows own manager but sometimes i need to restart the monitor to make windows find it correctly. Then it will work fine. I can switch from to a profile using the 3rd monitor to the one on the other dvi (2) or/and my tv (1). But trying to switch back breaks it. Tried uninstalling Amd control center but no dice. Gonna try a full reset of DF aswell

As i said before this just randomly started happening.

EDIT: Full reinstall did not fix this for me.
Dec 8, 2014 (modified Dec 8, 2014)  • #7
Avatar from Gravatar.com
James Stansell
10 discussion posts
might not even be an issue with DF but with ATI drivers or the cards themselves. i'm running a 7970 and R9 280X in crossfire (same cards pretty much). not sure whats going on but now just plugging in the hdmi cuts off the two displayport monitors. my monitors are 2160p, 1440p, and 1080p. who knows.
Dec 9, 2014  • #8
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Yeah, that's strange. I have the same monitor setup here as you James, but with a GTX 765m instead, and I don't have any issues loading the profile that enables all three monitors. I'll see if I can scrounge up an AMD card to test with though as well.
Dec 9, 2014  • #9
Keith Lammers (BFS)'s profile on WallpaperFusion.com
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!
Dec 12, 2014  • #10
Keith Lammers (BFS)'s profile on WallpaperFusion.com
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
Dec 16, 2014  • #11
Avatar from Gravatar.com
James Stansell
10 discussion posts
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.
Dec 16, 2014  • #12
Avatar from Gravatar.com
HavocHQ
3 discussion posts
I've started having the exact same problem with my third monitor after updating my AMD drivers today. Was a fix ever found?
Jan 10, 2015  • #13
Avatar from Gravatar.com
David322
4 discussion posts
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.
Feb 8, 2017  • #14
Keith Lammers (BFS)'s profile on WallpaperFusion.com
@David: Are you switching using hotkeys?
Feb 9, 2017  • #15
Avatar from Gravatar.com
David322
4 discussion posts
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).
Feb 9, 2017  • #16
Keith Lammers (BFS)'s profile on WallpaperFusion.com
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?
Feb 9, 2017  • #17
Avatar from Gravatar.com
David322
4 discussion posts
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.
Feb 19, 2017  • #18
Avatar from Gravatar.com
Barry Johnson
1 discussion post
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.
Feb 20, 2017 (modified Feb 20, 2017)  • #19
Keith Lammers (BFS)'s profile on WallpaperFusion.com
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.
Feb 23, 2017  • #20
Avatar from Gravatar.com
David322
4 discussion posts
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
Feb 23, 2017  • #21
Avatar from Gravatar.com
Joao Thomazini Neto521913
1 discussion post
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.
• Attachment [protected]: screenshot_2018-05-25 15.23_01.png [147,070 bytes]
May 25, 2018  • #22
Keith Lammers (BFS)'s profile on WallpaperFusion.com
We've just released 9.2.2 that should fix this up for good. Could you update again and let me know?
May 25, 2018  • #23
Avatar from Gravatar.com
David Snow
3 discussion posts
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.
• Attachment [protected]: Capture.PNG [81,873 bytes]
May 26, 2018 (modified May 26, 2018)  • #24
Keith Lammers (BFS)'s profile on WallpaperFusion.com
@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
May 28, 2018  • #25
Avatar from Gravatar.com
David Snow
3 discussion posts
Here you go.
• Attachment [protected]: DisplayFusionDebugInfo.zip [22,830 bytes]
May 29, 2018  • #26
Avatar from Gravatar.com
border
4 discussion posts
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.
May 29, 2018  • #27
Keith Lammers (BFS)'s profile on WallpaperFusion.com
@border: You mentioned 9.2.1, are you still having this issue in 9.2.2 as well?
May 29, 2018  • #28
Avatar from Gravatar.com
border
4 discussion posts
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
May 30, 2018  • #29
Keith Lammers (BFS)'s profile on WallpaperFusion.com
@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!
Jun 1, 2018  • #30
Avatar from Gravatar.com
David Snow
3 discussion posts
I just installed the 9.2.4 (beta 1) released on June 1 and my problem appears to have been fixed. Thanks!
Jun 5, 2018  • #31
Avatar from Gravatar.com
Ludovic Blanchard92229
2 discussion posts
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.
Jun 19, 2018  • #32
Keith Lammers (BFS)'s profile on WallpaperFusion.com
@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
Jun 21, 2018  • #33
Avatar from Gravatar.com
Ludovic Blanchard92229
2 discussion posts
Thank you for the answer. I'll keep searching for the source of the problem.
Jun 25, 2018  • #34
Was this helpful?  Login to Vote(1)  Login to Vote(1)
<< DiscussionsReply