Save up to 50% off any of our desktop apps in our 2021 spring sale, including
DisplayFusion, ClipboardFusion, FileSeek, LogFusion, TrayStatus, and VoiceBot!

Title

Message

Confirm

<< DiscussionsReply

Monitor profiles no longer working

Tim Hill94093
5 discussion posts
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
Jan 3, 2020  • #1
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Could you update to 9.6.2 Beta 1, then send us a debug log?

  • On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
  • Reproduce the error
  • Click the "Export Info to File" button on the Settings > Troubleshooting tab
  • Reply with the file attached
  • Disable debug logging after sending the log

Thanks!
Jan 7, 2020  • #2
Tim Hill94093
5 discussion posts
Thanks Keith. I was at 9.6.2 Beta 1 already - attached is my log.

Regards,

Tim
• Attachment [protected]: DisplayFusionDebugInfo.zip [40,833 bytes]
Jan 9, 2020  • #3
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Thanks Tim! I've added the logs to the open ticket here and we'll be sure to let you know when we've gotten it all fixed up.

Thanks!
Jan 9, 2020  • #4
cs42
6 discussion posts
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.
• Attachment [protected]: DisplayFusionDebugInfo.zip [43,330 bytes]
Jan 31, 2020  • #5
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Hi all!

We've just released a new DisplayFusion Beta version and the Error 87 issue should hopefully be fixed up.

Could you try updating, and if your profiles still throw an Error 87 when trying to load them, try re-saving the profiles?

Please let me know how it works out
Mar 27, 2020  • #6
Tim Hill94093
5 discussion posts
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
Mar 28, 2020  • #7
cs42
6 discussion posts
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.
Mar 28, 2020  • #8
Keith Lammers (BFS)'s profile on WallpaperFusion.com
@Tim: Just to double-check, did you also try re-creating the monitor profile with 9.7 Beta 6, or just try loading the existing one?

@cs42: Glad to hear it's working so far. If you're able to, could you try rebooting the machine and let me know if it still works, or if it breaks after the reboot?
Mar 30, 2020  • #9
cs42
6 discussion posts
Quote:

@cs42: Glad to hear it's working so far. If you're able to, could you try rebooting the machine and let me know if it still works, or if it breaks after the reboot?


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.
Mar 30, 2020  • #10
Keith Lammers (BFS)'s profile on WallpaperFusion.com
@cs42: Ok, thanks! Just keep me posted if the profile breaks again in 9.7 Beta 6
Mar 30, 2020  • #11
EARNEST
11 discussion posts
I am having a similar bug where I can't switch profiles, I downgraded to 9.7 Beta 4 and it works better.
Mar 31, 2020 (modified Mar 31, 2020)  • #12
Keith Lammers (BFS)'s profile on WallpaperFusion.com
@Earnest: What error are you getting with 9.7 Beta 6?
Mar 31, 2020 (modified Apr 1, 2020)  • #13
Tim Hill94093
5 discussion posts
Keith, yes, I did recreate and save this as a new profile.
Apr 1, 2020  • #14
Keith Lammers (BFS)'s profile on WallpaperFusion.com
@Tim: Could you send me a debug log?

  • On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
  • Try loading the Monitor Profile
  • Click the "Export Info to File" button on the Settings > Troubleshooting tab
  • Reply with the file attached
  • Disable debug logging after sending the log

Thanks!
Apr 1, 2020  • #15
Tim Hill94093
5 discussion posts
Hi Keith,

Here's the file attached - thank you!

Tim
• Attachment [protected]: DisplayFusionDebugInfo.zip [430,885 bytes]
Apr 2, 2020  • #16
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Thanks! I'll pass this over to our devs.
Apr 2, 2020  • #17
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Thanks! Could I get a couple more things from you?

  • Download this tool and extract it somewhere on your computer: https://www.binaryfortress.com/Files/DisplayFusion/BFCustomerTest.zip
  • Try to load the profile
  • Open the BFCustomerTest tool, copy the info to a text document and save it, then close the tool
  • Setup the monitor configuration with the Windows display settings
  • Open the BFCustomerTest tool and save the info again
  • Send me both copies of the info

Thanks!
Apr 2, 2020  • #18
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Hi all!

We've just released a new DisplayFusion Beta version and the Error 87 issue should hopefully be fixed up.

Could you try updating, and if your profiles still throw an Error 87 when trying to load them, try re-saving the profiles?

Please let me know how it works out
Apr 18, 2020  • #19
Nick Nadgauda
5 discussion posts
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.
Apr 23, 2020  • #20
Nick Nadgauda
5 discussion posts
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).
• Attachment [protected]: DisplayFusion.log [5,255,512 bytes]
Apr 24, 2020  • #21
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Are you trying to clone it using a saved profile, or just manually through the Monitor Configuration window?
Apr 24, 2020  • #22
Nick Nadgauda
5 discussion posts
It's the same issue in both cases
Apr 28, 2020  • #23
Keith Lammers (BFS)'s profile on WallpaperFusion.com
If you clone it using the Windows display settings, then save it as a new Monitor Profile in DF, are you able to load that one?
Apr 28, 2020  • #24
laxu
10 discussion posts
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.
May 5, 2020 (modified May 5, 2020)  • #25
Nick Nadgauda
5 discussion posts
@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.
May 5, 2020  • #26
EARNEST
11 discussion posts
This was fixed in a few previous betas, now it is broken on the latest again.
May 10, 2020  • #27
Keith Lammers (BFS)'s profile on WallpaperFusion.com
@laxu: It is somewhat tied to the ports. We may be able to add some kind of fallback though, I've added it to our list to investigate further.

@Nick: Would you be able to send us a support request for this using Help > Support Request in the DisplayFusion Settings window? We'll have some more troubleshooting steps for you to do.

@Earnest: Could you also send us a support request using Help > Support Request in the Settings window?

Thanks!
May 12, 2020  • #28
EARNEST
11 discussion posts
Sent, thanks
May 16, 2020  • #29
Nick Nadgauda
5 discussion posts
@Keith --- done.
May 19, 2020  • #30
Gareth Bristow38509
2 discussion posts
I am having the same issue as of a few days ago. Looks like a recent update. Log file attached.
• Attachment [protected]: DisplayFusionDebugInfo.zip [64,777 bytes]
Jan 12, 2021  • #31
Gareth Bristow38509
2 discussion posts
Quote:
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.


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.
Jan 12, 2021  • #32
Was this helpful?  (1)  
<< DiscussionsReply