About 10 days ago, my monitor profiles stopped working altogether, and I couldn't invoke them via the menu or through key combinations (I had set them up several years ago and not changed them). Now, since 9.6.1 some of them are working but not the one to clone screens. Instead I get:

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

Now, when I try to set up cloned screens manually I get the same error. I can set the screens to the same resolution and the same colour depth, but not the same refresh rate. This is because my Surface Pro 6 now has two possible refresh rates 59.959hz and 60.019hz.

Thanks,

Tim

Thanks Keith. I was at 9.6.2 Beta 1 already - attached is my log.

Regards,

Tim

I have the same error (Failed to call SetDisplayConfig. [HR: 87], [System.Exception]) as well. Might be the same issue or might be something different.

Created DisplayFusionDebugInfo.zip with v9.6.1 and attached them.

Sorry Keith,

I am still an Error 87 error on Beta 6 for one of my monitor cofigurations:

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

This configuration calls for both monitors to be 1920 x 1080 and cloned. I can manually set these monitoirs to this resolution, but when I try and make Monitor cloned with monitor 1 I get this error.

I appreciate your efforts to run this to ground.

Regards,

Tim

For me the first during the first test the beta version seems to work (only a couple of times tested). However, even with v9.6.1 there were times when DisplayFusion was working without any problems and then there were times during which the monitor configuration was only working, if set manually.

If I see get the HR 87 error again, I’ll post another DebugInfo file.

I did reboot several times and so far, it is still working. As far as the bug in the old v9.6.1 concerned rebooting was one issue. However, in my case also seemed to be important if the display, which was only enabled in the profile i wanted to switch to, was turned on during the power up of the pc. If this was the case, it was more likely (but not guaranteed) that the profile switching was working.

I am having a similar bug where I can't switch profiles, I downgraded to 9.7 Beta 4 and it works better.

Keith, yes, I did recreate and save this as a new profile.

Hi Keith,

Here's the file attached - thank you!

Tim

I'm having a related (maybe same) issue on Beta 10. I have a Surface Pro 5 and a UHD 28" monitor. I can mirror the display from the Surface to the monitor through the Windows settings but when i try to clone them through DisplayFusion I'm getting the error 87. This was happening in the previous version as well.

I've attached my log. I can't get the cloning to work no matter what I try. It always results in the same HR:87 error indicated above. This is on the latest beta (10).

It's the same issue in both cases

I have gotten this same issue if I change the ports on my GPU. For example if I have monitor profiles set with Displayport 1 on my GPU, then switch the monitor to DP 2 none of my monitor profiles work anymore and I get the same error as in OP.

So for some reason they seem to be tied to the port used rather than DF just detecting which port is using display with a specific EDID or something.

@Keith

No that doesn't work either. I can switch to "Duplicate These Displays" in the Windows Settings, then when I go into the DisplayFusion monitor configuration, it recognizes the current settings as "Cloned" but i can't save the profile. I get the same error.

This was fixed in a few previous betas, now it is broken on the latest again.

Sent, thanks

@Keith --- done.

I am having the same issue as of a few days ago. Looks like a recent update. Log file attached.

On this clue I set up the monitor profiles again and saved them over the old profiles. They now work correctly. I had changed one of the ports on one of the monitors.

Problem solved for now but might be worth tying the saved profiles to something dynamic.

Hello,
I am facing the same issue, but sometimes happen with my first monitor, sometimes in my second and sometimes, my TV. In attachment I put the log when the error occurred on my second monitor.

Find the attachment. Thanks !

Here is another one, this time, with my second monitor.

The first file has a error on my TV, the second one, with my second monitor (I have three : Primary (1920x1080p, 144hz), secondary (1366x768, 60hz) and TV (2560x1440, 120hz).

There's something I can do about my video card (RTX 2060 Super 8gb) ?

Yes, I do. When can we check this out?

Hello, I seem to be having the same error thrown whenever I try and move from one profile to the next or load my second profile. "An error has occurred while applying your new Monitor configuration.
Please check your settings and try again.
Error: Failed to call SetDisplayConfig. [HR: 87]
[System.Exception]" I am trying to basically have two PC monitors side by side extended as profile A and an LG C1 by itself as profile B, but while it normally works to do manually through windows settings, this profile management seems to cause the issue. I'm on 9.9 by the way and windows 10. Please help

I'm having the same issue! Even posted a couple days ago on this topic.

I hope they'll sort it out soon!

As requested here is the debug info! Sorry for the slow response.

Sorry I had reconfigured it at the time of the file dump, here is a replacement that should show all three.

It is fine when I'm creating the different monitor configurations, but any time I try and move from one profile to another I'm seeing the error. My main reason for this purchase was to be able to in a single keyboard shortcut quickly pivot from work > play essentially by enabling my TV and disabling my desktop monitors.

I keep getting this error too no matter what I do. I've tried deleting and recreating profiles, tried disconnecting monitors to see if one was the problem, nothing. It just won't change profiles without error 87 coming up. I've even reverted back to version 9.9 and that had no effect. This was working for me only a couple weeks ago, and now it's not, and absolutely nothing has changed except that I updated my bios and some drivers.

So, funny story...after a ton of troubleshooting, going back to previous restore points, etc, I finally found out that it was due to Nvidia Image Scaling, which I had turned on a couple days ago and didn't realize it caused a problem. No idea why NIS would cause monitor profiles to fail to load, but there you have it. It took me installing Monitor Profile Switcher and have a similar error with that to realize that something else was going on and it wasn't a DisplayFusion specific problem. I can now replicate the problem perfectly by enabling NIS, and then the problem goes away immediately after disabling it. I'll attach the troubleshooting info and my log file anyway just in case you want to look into it.