<?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: Monitor Profile Detection Bug</title>
<atom:link href="https://www.displayfusion.com/Discussions/RSS/?TopicID=88719c54-0eee-4b53-a3e5-11fa0c2a932c" rel="self" type="application/rss+xml" />
<link>https://www.displayfusion.com/Discussions/RSS/?TopicID=88719c54-0eee-4b53-a3e5-11fa0c2a932c</link>
<description>DisplayFusion RSS: Monitor Profile Detection Bug</description>
<lastBuildDate>Fri, 22 May 2026 22:39:54 GMT</lastBuildDate>
<language>en</language>
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<generator>https://www.displayfusion.com/Discussions/RSS/?TopicID=88719c54-0eee-4b53-a3e5-11fa0c2a932c</generator>
<item>
<title>RE: Monitor Profile Detection Bug</title>
<link>https://www.displayfusion.com/Discussions/View/monitor-profile-detection-bug/?ID=88719c54-0eee-4b53-a3e5-11fa0c2a932c#5</link>
<pubDate>Wed, 05 Jul 2023 17:25:38 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/monitor-profile-detection-bug/?ID=88719c54-0eee-4b53-a3e5-11fa0c2a932c#5</guid>
<category>DisplayFusion</category>
<description><![CDATA[We've released a new beta that might fix this up. Can you try it out and let me know your results? Here's the link: https://www.displayfusion.com/Download/Beta/]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
We've released a new beta that might fix this up. Can you try it out and let me know your results? Here's the link: <a href="https://www.displayfusion.com/Download/Beta/" target="_blank" rel="nofollow"><b>https://www.displayfusion.com/Download/Beta/</b></a>
</div>
]]></content:encoded>
<media:thumbnail url="https://www.displayfusion.com/Discussions/Download/?ID=c44ddfe1-a55a-466a-b619-c9e60bc9a467"/>
</item>
<item>
<title>RE: Monitor Profile Detection Bug</title>
<link>https://www.displayfusion.com/Discussions/View/monitor-profile-detection-bug/?ID=88719c54-0eee-4b53-a3e5-11fa0c2a932c#4</link>
<pubDate>Wed, 07 Jun 2023 14:01:00 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/monitor-profile-detection-bug/?ID=88719c54-0eee-4b53-a3e5-11fa0c2a932c#4</guid>
<category>DisplayFusion</category>
<description><![CDATA[We have some ideas here to fix this up, so we'll let you know when we have a beta to test out.
Thanks!]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
We have some ideas here to fix this up, so we'll let you know when we have a beta to test out.<br/>
<br/>
Thanks!
</div>
]]></content:encoded>
<media:thumbnail url="https://www.displayfusion.com/Discussions/Download/?ID=c44ddfe1-a55a-466a-b619-c9e60bc9a467"/>
</item>
<item>
<title>RE: Monitor Profile Detection Bug</title>
<link>https://www.displayfusion.com/Discussions/View/monitor-profile-detection-bug/?ID=88719c54-0eee-4b53-a3e5-11fa0c2a932c#3</link>
<pubDate>Wed, 17 May 2023 08:48:52 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/monitor-profile-detection-bug/?ID=88719c54-0eee-4b53-a3e5-11fa0c2a932c#3</guid>
<category>DisplayFusion</category>
<description><![CDATA[I have removed the manually edited profile again for the issue to reappear. Here you go. MonitorConfigFixed.reg (in 1st post) will fix that again. Actually, even after quitting DF, adding MonitorConfigFixed.reg to registry and starting DF again, the currently active profile (which should be ident...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I have removed the manually edited profile again for the issue to reappear. Here you go. MonitorConfigFixed.reg (in 1st post) <del>will fix that again.</del> Actually, even after quitting DF, adding MonitorConfigFixed.reg to registry and starting DF again, the currently active profile (which should be identified as "1xM27Q 120 Hz") is still detected as "TV 120 Hz 1440p" (since that was the profile selected before quitting DF, I guess). Clicking on "1xM27Q 120 Hz" then selects the correct profile and otherwise does nothing (which is OK, the correct monitor/resolution/etc is already set) and afterwards everything works perfectly: After setting "2xM27Q 120 Hz" and then manually disabling the secondary monitor in Windows display settings DF will correctly detect current profile as "1xM27Q 120 Hz", not as "TV 120 Hz" as before the registry intervention, setting the profile manualy to the TV 1440p in Windows display settings will end up in correctly detecting the "TV 120 Hz 1440p" profile and so on.
</div>
]]></content:encoded>
<media:thumbnail url="https://www.displayfusion.com/Discussions/Download/?ID=c44ddfe1-a55a-466a-b619-c9e60bc9a467"/>
</item>
<item>
<title>RE: Monitor Profile Detection Bug</title>
<link>https://www.displayfusion.com/Discussions/View/monitor-profile-detection-bug/?ID=88719c54-0eee-4b53-a3e5-11fa0c2a932c#2</link>
<pubDate>Mon, 15 May 2023 14:38:50 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/monitor-profile-detection-bug/?ID=88719c54-0eee-4b53-a3e5-11fa0c2a932c#2</guid>
<category>DisplayFusion</category>
<description><![CDATA[Could you send me a copy of your troubleshooting info? Here are the steps:
Open the Settings  Troubleshooting tab
Click the "Export Info to File" button
Reply with the file attached]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Could you send me a copy of your troubleshooting info? Here are the steps:<br/>
<br/>
<ul class="ListBullet">
<li>Open the Settings > Troubleshooting tab</li>
<li>Click the "Export Info to File" button</li>
<li>Reply with the file attached</li></ul>
</div>
]]></content:encoded>
<media:thumbnail url="https://www.displayfusion.com/Discussions/Download/?ID=c44ddfe1-a55a-466a-b619-c9e60bc9a467"/>
</item>
<item>
<title>Monitor Profile Detection Bug</title>
<link>https://www.displayfusion.com/Discussions/View/monitor-profile-detection-bug/?ID=88719c54-0eee-4b53-a3e5-11fa0c2a932c</link>
<pubDate>Mon, 15 May 2023 09:37:38 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/monitor-profile-detection-bug/?ID=88719c54-0eee-4b53-a3e5-11fa0c2a932c</guid>
<category>DisplayFusion</category>
<description><![CDATA[I have 2 monitors (M27Q) and a TV. I want to have a profile for 2560x1440/120 Hz/100% scaling on my primary monitor and another profile with the same resolution/refresh/scaling combination also for the TV. However there is a bug (tested on latest v10 stable and also tried the latest v10.1b3 beta)...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I have 2 monitors (M27Q) and a TV. I want to have a profile for 2560x1440/120 Hz/100% scaling on my primary monitor and another profile with the same resolution/refresh/scaling combination also for the TV. However there is a bug (tested on latest v10 stable and also tried the latest v10.1b3 beta) that detects 2560x1440/120 Hz/100% on the monitor as the TV profile (if the TV profile already exists) and vice versa (so 2560x1440/120 Hz/100% on the TV is detected as the monitor profile if it already exists). Selecting the already the already selected/highlighted profile from the tray menu correctly sets the profile, so it seems there is just some kind of bug in detecting distinct (multi)monitor profiles.<br/>
<br/>
Since you have removed the "Save as..." functionality for profiles in v10, the only workaround is to create a new profile tha differs e.g. in scaling for the monitor (2560x1440/120 Hz/125%), save it, close DisplayFusion and correct the profile in registry (HKEY_CURRENT_USER\Software\Binary Fortress Software\DisplayFusion\MonitorConfig\PROFILEGUID\Monitor0_Json). Once the profiles are correctly set, everything works - so having 2560x1440/120 Hz/100% on the monitor/TV is detected as the correct monitor/TV profile.
</div>
]]></content:encoded>
<media:thumbnail url="https://www.displayfusion.com/Discussions/Download/?ID=c44ddfe1-a55a-466a-b619-c9e60bc9a467"/>
</item>
</channel>
</rss>