https://www.displayfusion.com/Discussions/RSS/?TopicID=9f12abf7-d90b-4010-b051-5227da48660b DisplayFusion RSS: Failed to call SetDisplayConfig. [HR: 31] Sun, 19 Apr 2026 18:04:34 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=9f12abf7-d90b-4010-b051-5227da48660b https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#14 Wed, 13 Jan 2021 22:10:46 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#14 DisplayFusion Ok, thanks! If you could create a second set of profiles with the current version and then send me a new copy of the troubleshooting info, that would be great

Thanks! ]]> https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#13 Tue, 12 Jan 2021 21:09:58 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#13 DisplayFusion What I was trying to say in my last post was:
I believe the upload in this thread's first post contains "port 1". While the second upload in this thread contains the same profile names, but configured on "port 2". I'm writing this out of office from mobile, so maybe what I allready have uploaded has the data you need?

But maybe it falls short since created in the previous version, but log was extracted from beta 10? ]]> https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#12 Tue, 12 Jan 2021 16:25:35 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#12 DisplayFusion Those 3 profiles only work on one of the ports though, right? Do you have another 3 profiles that were saved while the dock was connected to the other port? ]]> https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#11 Thu, 07 Jan 2021 22:47:20 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#11 DisplayFusion I overwrote all the existing profiles when updating from 9.7.1(?) to beta 10. I have named my profiles 0 - 3. So If you compare ie. the one named "3" in my first diagnostic upload with my latest? ]]> https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#10 Thu, 07 Jan 2021 20:21:16 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#10 DisplayFusion There actually might be a way to do this actually. Can you send me the names of the two monitor profiles? (the main profile and the backup profile that was created for the other port?) ]]> https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#9 Wed, 06 Jan 2021 19:33:37 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#9 DisplayFusion I don't believe there actually is a way to trap the error, the script just blindly calls the function to load a profile. I will see if there's a way we could add some error handling in there. ]]> https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#8 Fri, 01 Jan 2021 07:39:41 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#8 DisplayFusion Not sure if it's allright to expand this thread further. Let me know if I should start a new one.
Since I have 3 profiles allready hotkeyed, I would need 3 new hotkeys, unless I change the hotkeys to run functions instead.
I browsed and seached through your help page about script functions, but couldn't find anything about error trapping. Could you lend me a hand on how to structure an IF sentence that checks if the profile change returned an error, THEN apply the correct "rescue profile"?

Or would it be easier to identify both ports, then check which port is active and activate the relevant profile?

I'm pretty OK with Visual Basic, so writing in VB would be preferable. ]]> https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#7 Thu, 31 Dec 2020 15:12:03 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#7 DisplayFusion Ah, yep, that would probably do it! Unfortunately there isn't a way to save a profile that works with both ports, but you could have two profiles saved, then just load whichever one you need. ]]> https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#6 Wed, 30 Dec 2020 07:02:15 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#6 DisplayFusion Hmmm. I think I may have found the issue...

I use a laptop with 2 USB-C ports next to eachother

I connect screen, keyboard and mouse through a USB-C multi adaptor (not the original docking).

When the adaptor has been disconnected and re-connected, I have not paid attention to which of the 2 USB-C ports I connected. I switched input just now and it started working again!

This probably makes sense...But if I were to be lazy and want both of them to work, do you have any idea if that's possible with the current release?

One monitor profile with splits working on both ports of my laptop. ]]> https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#5 Wed, 30 Dec 2020 02:19:30 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#5 DisplayFusion Ok, strange! Does anything specific seem to make it stop working? (system reboot, driver update, etc?) ]]> https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#4 Tue, 29 Dec 2020 21:28:06 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#4 DisplayFusion Hi, just got the same error message again.
I had the beta 10 when I got the error, I updated to the newest 9.7.1, no change.

It will probably work again if I set up the monitor profiles a third time, but maybe something's off here? ]]> https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#3 Thu, 24 Dec 2020 18:07:18 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#3 DisplayFusion The beta saves some more info with the monitor profiles to help with errors like this, so if you've recreated the profile using the beta, you should hopefully not get this error any more in the future

Thanks! ]]> https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#2 Wed, 23 Dec 2020 12:02:42 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b#2 DisplayFusion I was able to get passed the error by configuring my profile/splits from scratch and overwrite the saved profiles. So it's working at the moment, but maybe you'll find something in my debug info? ]]> https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b Wed, 23 Dec 2020 08:39:59 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/failed-to-call-setdisplayconfig-hr-31/?ID=9f12abf7-d90b-4010-b051-5227da48660b DisplayFusion An error has occurred while applying your new Monitor configuration.
Please check your settings and try again.
Error: Failed to call SetDisplayConfig. [HR: 31]
[System.Exception]

Hi. This worked well for a week, then I got this error on profile change.
Now I can't set splits manually through the monitor settings or through saved profiles.

I was running 9.7 when this error occured, updated to beta 10 and got same error.

attached debug info. ]]>