<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/">
<channel>
<title>DisplayFusion RSS: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<atom:link href="https://www.displayfusion.com/Discussions/RSS/?TopicID=ac310c84-3dde-4c97-a34b-5f0123206053" rel="self" type="application/rss+xml" />
<link>https://www.displayfusion.com/Discussions/RSS/?TopicID=ac310c84-3dde-4c97-a34b-5f0123206053</link>
<description>DisplayFusion RSS: Error: Failed to call SetDisplayConfig. [HR: 87]</description>
<lastBuildDate>Fri, 22 May 2026 22:01:09 GMT</lastBuildDate>
<language>en</language>
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<generator>https://www.displayfusion.com/Discussions/RSS/?TopicID=ac310c84-3dde-4c97-a34b-5f0123206053</generator>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#108</link>
<pubDate>Fri, 16 Feb 2024 19:12:20 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#108</guid>
<category>DisplayFusion</category>
<description><![CDATA[Re-creating the profiles is recommended. The way 10.1.2 stores and applies the profiles is quite different from 9.9 and we tried to keep them backwards compatible, but that might not work in all cases.
We are adding another fallback for 11 Beta 3, so you could maybe try that before re-creating t...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Re-creating the profiles is recommended. The way 10.1.2 stores and applies the profiles is quite different from 9.9 and we tried to keep them backwards compatible, but that might not work in all cases.<br/>
<br/>
We are adding another fallback for 11 Beta 3, so you could maybe try that before re-creating the profiles if you like.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#107</link>
<pubDate>Thu, 15 Feb 2024 19:20:53 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#107</guid>
<category>DisplayFusion</category>
<description><![CDATA[I just updated to 10.1.2 and I too am now experiencing this error.. older profiles created prior to this version are effected.. new profiles load just fine. Any thoughts on this issue? NVidia setting is not the solution as my scaling is turned off.  I can just delete the few older profiles I have...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I just updated to 10.1.2 and I too am now experiencing this error.. older profiles created prior to this version are effected.. new profiles load just fine. Any thoughts on this issue? NVidia setting is not the solution as my scaling is turned off.  I can just delete the few older profiles I have and create new ones but seems like something is borked with the move from 9.x to 10.x.x
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#106</link>
<pubDate>Wed, 17 May 2023 20:12:51 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#106</guid>
<category>DisplayFusion</category>
<description><![CDATA[You can reply here with them attached. They are protected (viewable only by Binary Fortress staff) by default.
Thanks!]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
You can reply here with them attached. They are protected (viewable only by Binary Fortress staff) by default.<br/>
<br/>
Thanks!
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#105</link>
<pubDate>Mon, 15 May 2023 16:38:58 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#105</guid>
<category>DisplayFusion</category>
<description><![CDATA[@Keith sure thing. Where should I sent the files at?]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
@Keith sure thing. Where should I sent the files at?
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#104</link>
<pubDate>Mon, 15 May 2023 14:24:21 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#104</guid>
<category>DisplayFusion</category>
<description><![CDATA[@Loial: If you could send us a copy of the DF troubleshooting info, as well as the output from this utility before and after re-saving the profile and applying it, that would be great! Note that you need to close and re-open that tool to get it to update the info.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
@Loial: If you could send us a copy of the DF troubleshooting info, as well as the output from <a href="https://www.binaryfortress.com/Data/Download/?DownloadID=495db9ad-a9fe-4bee-a23d-d9cf233a7b1b&Log=0" target="_blank" rel="nofollow"><b>this utility</b></a> before and after re-saving the profile and applying it, that would be great! Note that you need to close and re-open that tool to get it to update the info.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#103</link>
<pubDate>Fri, 12 May 2023 21:37:33 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#103</guid>
<category>DisplayFusion</category>
<description><![CDATA[Hi team,
I've been getting this same error for the past couple of days. EDIT: The error I'm getting is actually "Error: Failed to call SetDisplayConfig. [HR: ERROR_GEN_FAILURE], [System.Exception]"
I don't recall if there was a DisplayFusion update or a Windows update, but likely one of the two...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Hi team,<br/>
<del>I've been getting this same error for the past couple of days</del>. <b>EDIT</b>: The error I'm getting is actually "Error: Failed to call SetDisplayConfig. [HR: ERROR_GEN_FAILURE], [System.Exception]"<br/>
I don't recall if there was a DisplayFusion update or a Windows update, but likely one of the two is the culprit.<br/>
Hardware hasn't changed.<br/>
The monitor profile is extremely simple and I can recreate it no problem, but just wanted to check in this thread to see if there's anything you'd need from me in terms of debugging information?
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#102</link>
<pubDate>Thu, 01 Dec 2022 19:21:04 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#102</guid>
<category>DisplayFusion</category>
<description><![CDATA[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
...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Hello,<br/>
<br/>
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<br/>
<br/>
Please let me know if you run into any issues after updating.<br/>
<br/>
Thanks!
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#101</link>
<pubDate>Fri, 23 Sep 2022 16:19:16 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#101</guid>
<category>DisplayFusion</category>
<description><![CDATA[@brettreichart78045: This thread is getting a bit long so I'd like to continue troubleshooting via our support ticketing system to prevent everyone here from getting notified of every reply. Could you send us a support request through DisplayFusion (Settings  Help  Support Request)? Please link t...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
@brettreichart78045: This thread is getting a bit long so I'd like to continue troubleshooting via our support ticketing system to prevent everyone here from getting notified of every reply. Could you send us a support request through DisplayFusion (Settings > Help > Support Request)? Please link to this thread in the body of the support request as well.<br/>
<br/>
Thanks!
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#100</link>
<pubDate>Fri, 23 Sep 2022 07:10:25 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#100</guid>
<category>DisplayFusion</category>
<description><![CDATA[I just tried to set it with the devices off and still get the error.
@giovs I know I'm on 9.5, since it says so at the top of every window.
Uninstalled and re-installed, and just noticed something. I can't set the TV that I'm having the issues on to 120hz unless I turn it on first. I'm sure tha...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I just tried to set it with the devices off and still get the error.<br/>
<br/>
@giovs I know I'm on 9.5, since it says so at the top of every window.<br/>
<br/>
Uninstalled and re-installed, and just noticed something. I can't set the TV that I'm having the issues on to 120hz unless I turn it on first. I'm sure that is what is causing this issue. I can enable the TV to 60hz, but as soon as I enable it to 120hz, Display Fusion disables it again. Once I turn the TV on, Display Fusion will set it to 120hz automatically.<br/>
<br/>
I just tried the same steps on my 165hz monitor and it's doing the same thing unless I turn the monitor on first. If I turn on every single monitor/TV first, then all my key combinations work, but if any device that is over 60hz is off, then they start messing up.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#99</link>
<pubDate>Thu, 22 Sep 2022 17:19:05 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#99</guid>
<category>DisplayFusion</category>
<description><![CDATA[@brettreichart78045: You're trying to apply a monitor profile that contains settings for monitors that are powered off? What happens if you re-save that profile when those monitors are powered off, so that they're not included in the profile? Does it load correctly then?
@giovs: No guts hating o...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
@brettreichart78045: You're trying to apply a monitor profile that contains settings for monitors that are powered off? What happens if you re-save that profile when those monitors are powered off, so that they're not included in the profile? Does it load correctly then?<br/>
<br/>
@giovs: No guts hating over here! Our job is to find and fix issues, so we always appreciate the feedback <img src="https://www.displayfusion.com/MediaCommon/SVGs/FontAwesome/face-laugh-beam.light.svg" alt=":laugh:" style="box-sizing:border-box;position:relative;overflow:hidden;vertical-align:middle !important;width:16px;height:16px;" HelpButtonData=":laugh:" HelpButtonDataAlign="BelowMiddle" />
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#98</link>
<pubDate>Wed, 21 Sep 2022 19:52:21 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#98</guid>
<category>DisplayFusion</category>
<description><![CDATA[Quote:
I'm having the same issue if my TV/monitors are turned off. Once I turn on all the devices I'm trying to switch to, then it will work fine. It didn't use to be this way until I started broadcasting in 4K 120hz. I have tried both 9.9 and 9.5 versions with no success. Hopefully there is a f...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
<div class="BackGrey"><div class="Text"><div><b>Quote:</b></div>I'm having the same issue if my TV/monitors are turned off. Once I turn on all the devices I'm trying to switch to, then it will work fine. It didn't use to be this way until I started broadcasting in 4K 120hz. I have tried both 9.9 and 9.5 versions with no success. Hopefully there is a fix for this soon assuming you know what the issue is.</div></div><br/>
<br/>
You absolutely sure the downgrade was successfull, m8? Maybe it auto updated it again?<br/>
I've had this problem for years, it was a pain in the nut, I posted so much about this here my man Keith probably hates my guts lol. But after rolling back to 9.5. it started working like a charm, never had the issue anymore.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#97</link>
<pubDate>Wed, 21 Sep 2022 09:44:47 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#97</guid>
<category>DisplayFusion</category>
<description><![CDATA[I'm having the same issue if my TV/monitors are turned off. Once I turn on all the devices I'm trying to switch to, then it will work fine. It didn't use to be this way until I started broadcasting in 4K 120hz. I have tried both 9.9 and 9.5 versions with no success. Hopefully there is a fix for t...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I'm having the same issue if my TV/monitors are turned off. Once I turn on all the devices I'm trying to switch to, then it will work fine. It didn't use to be this way until I started broadcasting in 4K 120hz. I have tried both 9.9 and 9.5 versions with no success. Hopefully there is a fix for this soon assuming you know what the issue is.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#96</link>
<pubDate>Tue, 13 Sep 2022 14:02:07 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#96</guid>
<category>DisplayFusion</category>
<description><![CDATA[If you install the latest version through Steam, then just run the 9.5 installer over top, that will work with your license.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
If you install the latest version through Steam, then just run the 9.5 installer over top, that will work with your license.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#95</link>
<pubDate>Sat, 10 Sep 2022 13:55:27 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#95</guid>
<category>DisplayFusion</category>
<description><![CDATA[Hi, I have a similar problem, but I can't instal your 9.5 version to try because I have a steam licence and it say that it's not valid... Do you have a steam 9.5 link  please?]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Hi, I have a similar problem, but I can't instal your 9.5 version to try because I have a steam licence and it say that it's not valid... Do you have a steam 9.5 link  please?
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#94</link>
<pubDate>Wed, 18 May 2022 19:02:47 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#94</guid>
<category>DisplayFusion</category>
<description><![CDATA[If re-saving the profile in 9.9 doesn't resolve it, can you try rolling back to DisplayFusion 9.5 and then re-saving the profile?]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
If re-saving the profile in 9.9 doesn't resolve it, can you try rolling back to <a href="https://www.binaryfortress.com/Data/Download/?OldVersion=1&DownloadID=468541db-df1d-4c92-9bde-4087c291f656" target="_blank" rel="nofollow"><b>DisplayFusion 9.5</b></a> and then re-saving the profile?
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#93</link>
<pubDate>Mon, 16 May 2022 23:43:49 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#93</guid>
<category>DisplayFusion</category>
<description><![CDATA[I am having this problem as well. And started out of nowhere. Was fine, and then i was not.
This is really annoying, because is literally the feature a use the most. DF became almost useless to me.
I updated to the 10 Beta 16, and this error still persist.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I am having this problem as well. And started out of nowhere. Was fine, and then i was not.<br/>
<br/>
This is really annoying, because is literally the feature a use the most. DF became almost useless to me.<br/>
<br/>
I updated to the 10 Beta 16, and this error still persist.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#92</link>
<pubDate>Mon, 16 May 2022 17:45:50 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#92</guid>
<category>DisplayFusion</category>
<description><![CDATA[I am having the same issue.
An error has occurred while applying your new Monitor configuration.
Please check your settings and try again.
Error: Failed to call SetDisplayConfig. [HR: ERROR_GEN_FAILURE]
[System.Exception]
I have profiles for when I have the laptop lid open (dual monitor) or ...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I am having the same issue. <br/>
<br/>
An error has occurred while applying your new Monitor configuration.<br/>
Please check your settings and try again.<br/>
Error: Failed to call SetDisplayConfig. [HR: ERROR_GEN_FAILURE]<br/>
[System.Exception]<br/>
<br/>
I have profiles for when I have the laptop lid open (dual monitor) or just the laptop when I'm undocked. I can't load or switch monitor profiles. I can  <br/>
reconfigure splits and apply.<br/>
<br/>
This was working under Win 11 until recently (last two weeks or so).
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#91</link>
<pubDate>Wed, 20 Apr 2022 16:29:55 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#91</guid>
<category>DisplayFusion</category>
<description><![CDATA[I'm getting this a lot, usually just unplugging my eGPU is enough to permanantly break the saved monitor profile meaning I have to redo my splits and padding, which gets quite tiresome after a while.
This was an issue on Win10 and has persisted to Win11 (both upgrade install and format&reinstall...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I'm getting this a lot, usually just unplugging my eGPU is enough to permanantly break the saved monitor profile meaning I have to redo my splits and padding, which gets quite tiresome after a while.<br/>
<br/>
This was an issue on Win10 and has persisted to Win11 (both upgrade install and format&reinstall). Upgrading to 10.0b15 has changed the error to HR: ERROR_GEN_FAILURE but otherwise it's the same issue.<br/>
<br/>
It's marginally less irritating in Win11 because the built in snap feature where you can hover over the maximise button and pick from one of six pre-baked layouts actually has one that matches what I set in DisplayFusion, but not all apps support this feature so I'd still rather use DF.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#90</link>
<pubDate>Mon, 04 Apr 2022 03:29:19 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#90</guid>
<category>DisplayFusion</category>
<description><![CDATA[Quote:
Yeah I think something was definitely changed in how DF detects the power state of monitors and TVs since version 9.5. I have still been using the download from the #7 post by Keith.
Whoa interesting... You're not getting this issue at 9.5?
I'm trying this asap!]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
<div class="BackGrey"><div class="Text"><div><b>Quote:</b></div>Yeah I think something was definitely changed in how DF detects the power state of monitors and TVs since version 9.5. I have still been using the download from the #7 post by Keith.</div></div><br/>
<br/>
Whoa interesting... You're not getting this issue at 9.5?<br/>
I'm trying this asap!
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#89</link>
<pubDate>Sun, 03 Apr 2022 23:36:34 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#89</guid>
<category>DisplayFusion</category>
<description><![CDATA[Yeah I think something was definitely changed in how DF detects the power state of monitors and TVs since version 9.5. I have still been using the download from the #7 post by Keith.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Yeah I think something was definitely changed in how DF detects the power state of monitors and TVs since version 9.5. I have still been using the download from the #7 post by Keith.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#88</link>
<pubDate>Sun, 03 Apr 2022 22:54:36 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#88</guid>
<category>DisplayFusion</category>
<description><![CDATA[Hello! Guys, I have some info that might help with the debug.
1. I tried switching profiles a couple of times, with no use. The same error kept appearing. Note: even though the error message says "failed to (...)" the profiles always successfully switches, I can see the new monitor layout on the...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Hello! Guys, I have some info that might help with the debug.<br/>
<br/>
1. I tried switching profiles a couple of times, with no use. The same error kept appearing. Note: even though the error message says "failed to (...)" the profiles always successfully switches, <b>I can see the new monitor layout on the other screens</b>, but as soon as I click OK it reverts to the previous layout (clicking the "x" windows button does the same).<br/>
<br/>
2. But here's the deal... I kept insisting on switching the monitor profiles, and for some unknown reason <b>after a bunch of tries it simply started working properly</b>. Out of the blue, now the profiles are switching properly. I restarted Windows and somehow it was still working!<br/>
<br/>
3. But here's something else. As soon as I turned off my 127v power strip - cutting off the power supply to both the PC and all screens - when I turned it on again the <i>SetDisplayConfig. [HR: 87]</i> error would pop back in. I re-did this a couple of times, and while only turning off/resetting Windows won't affect DisplayFusion, I <b>can confirm cutting off the power always results in DisplayFusion failing to switch profiles afterwards</b>. If I don't cut off the power, the error won't appear. If I do, the next time I boot Windows, it'll give me the <i>Error: Failed to call SetDisplayConfig. [HR: 87]</i>.<br/>
<br/>
4. Lastly, if I keep insisting on switching the profiles randomly on DisplayFusion, at some point the error will be gone and I'll be able to switch them with no issue. As I just did right now.<br/>
<br/>
<b>The debug log is attached.</b><br/>
<br/>
These are the screen specs:<br/>
1. Main Screen: 165hz, 1080p<br/>
2. 2nd Screen: 60hz, 1600p, custom windows color (ICM) Profile<br/>
3. TV: 60hz, 1080p<br/>
<br/>
These are the 4 profiles for my 3 screens:<br/>
• 1 + 2 + 3 (mirrored with main)<br/>
• 1 + 2<br/>
• 1 + 3 (mirrored with main)<br/>
• 3 only<br/>
<br/>
Hope it helps!
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#87</link>
<pubDate>Wed, 23 Mar 2022 20:05:55 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#87</guid>
<category>DisplayFusion</category>
<description><![CDATA[Quote:
So far no issues when testing with NIS enabled in either location
If you re-enable it on yours, can you reproduce the issue still?
Yep, it's still completely repeatable. If I turn image scaling on, then change monitor config, I get the error without fail. Sometimes it does enable/disabl...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
<div class="BackGrey"><div class="Text"><div><b>Quote:</b></div>So far no issues when testing with NIS enabled in either location <img src="https://www.displayfusion.com/MediaCommon/SVGs/FontAwesome/face-frown.light.svg" alt=":(" style="box-sizing:border-box;position:relative;overflow:hidden;vertical-align:middle !important;width:16px;height:16px;" HelpButtonData=":(" HelpButtonDataAlign="BelowMiddle" /><br/>
<br/>
If you re-enable it on yours, can you reproduce the issue still?</div></div><br/>
<br/>
Yep, it's still completely repeatable. If I turn image scaling on, then change monitor config, I get the error without fail. Sometimes it does enable/disable monitors, but usually doesn't set them all up properly.<br/>
<br/>
A couple notes that might help with debugging: I have an ultrawide display (32:9, 5120x1440 @ 120hz), I also have a monitor set in portrait mode. I'm running windows 10 fully updated and using the latest beta release of DF. I was also using the latest Nvidia driver, and just updated to the brand new one, and the issue still persists. Not sure what else might be useful. All I can tell you is that it used to work, and then suddenly stopped working, and I have no idea why. I've attached a screenshot with the error and showing that I have NIS turned on.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#86</link>
<pubDate>Wed, 23 Mar 2022 18:42:53 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#86</guid>
<category>DisplayFusion</category>
<description><![CDATA[So far no issues when testing with NIS enabled in either location
If you re-enable it on yours, can you reproduce the issue still?]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
So far no issues when testing with NIS enabled in either location <img src="https://www.displayfusion.com/MediaCommon/SVGs/FontAwesome/face-frown.light.svg" alt=":(" style="box-sizing:border-box;position:relative;overflow:hidden;vertical-align:middle !important;width:16px;height:16px;" HelpButtonData=":(" HelpButtonDataAlign="BelowMiddle" /><br/>
<br/>
If you re-enable it on yours, can you reproduce the issue still?
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#85</link>
<pubDate>Wed, 09 Mar 2022 15:05:57 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#85</guid>
<category>DisplayFusion</category>
<description><![CDATA[I didn't even know there was an option in GeForce Experience for it so I appreciate you sending that over! I tested with the settings in NVIDIA Control Panel and didn't have any issues, but I'll re-test with GeForce Experience as well.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I didn't even know there was an option in GeForce Experience for it so I appreciate you sending that over! I tested with the settings in NVIDIA Control Panel and didn't have any issues, but I'll re-test with GeForce Experience as well.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Error: Failed to call SetDisplayConfig. [HR: 87]</title>
<link>https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#84</link>
<pubDate>Tue, 08 Mar 2022 23:47:19 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053#84</guid>
<category>DisplayFusion</category>
<description><![CDATA[Here you go @Keith. I'm not sure if you meant the control panel or GeForce Experience, so I included both.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Here you go @Keith. I'm not sure if you meant the control panel or GeForce Experience, so I included both.
</div>
]]></content:encoded>
</item>
</channel>
</rss>