<?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 not enabling bug, profiles becoming 'damaged'</title>
<atom:link href="https://www.displayfusion.com/Discussions/RSS/?TopicID=a496646e-d330-406b-ba7b-9e2f8d411817" rel="self" type="application/rss+xml" />
<link>https://www.displayfusion.com/Discussions/RSS/?TopicID=a496646e-d330-406b-ba7b-9e2f8d411817</link>
<description>DisplayFusion RSS: Monitor not enabling bug, profiles becoming 'damaged'</description>
<lastBuildDate>Sat, 16 May 2026 21:05:27 GMT</lastBuildDate>
<language>en</language>
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<generator>https://www.displayfusion.com/Discussions/RSS/?TopicID=a496646e-d330-406b-ba7b-9e2f8d411817</generator>
<item>
<title>RE: Monitor not enabling bug, profiles becoming 'damaged'</title>
<link>https://www.displayfusion.com/Discussions/View/monitor-not-enabling-bug-profiles-becoming-damaged/?ID=a496646e-d330-406b-ba7b-9e2f8d411817#8</link>
<pubDate>Wed, 29 Mar 2017 00:49:38 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/monitor-not-enabling-bug-profiles-becoming-damaged/?ID=a496646e-d330-406b-ba7b-9e2f8d411817#8</guid>
<category>DisplayFusion</category>
<description><![CDATA[@S.ALT255: Your post gave us an idea on something to try. I'll be following-up after we've had a chance to make a couple of changes in DF.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
@S.ALT255: Your post gave us an idea on something to try. I'll be following-up after we've had a chance to make a couple of changes in DF.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Monitor not enabling bug, profiles becoming 'damaged'</title>
<link>https://www.displayfusion.com/Discussions/View/monitor-not-enabling-bug-profiles-becoming-damaged/?ID=a496646e-d330-406b-ba7b-9e2f8d411817#7</link>
<pubDate>Tue, 28 Mar 2017 17:06:24 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/monitor-not-enabling-bug-profiles-becoming-damaged/?ID=a496646e-d330-406b-ba7b-9e2f8d411817#7</guid>
<category>DisplayFusion</category>
<description><![CDATA[Quote:
@Christian: Can you post some more details? How many monitors, connection types, which profiles you're switching from/to when you get an error, etc.
Thanks!
Didn't see your reply, sorry!
I created a new thread with my issue.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
<div class="BackGrey"><div class="Text"><div><b>Quote:</b></div>@Christian: Can you post some more details? How many monitors, connection types, which profiles you're switching from/to when you get an error, etc.<br/>
<br/>
Thanks!</div></div><br/>
<br/>
Didn't see your reply, sorry! <br/>
<br/>
I created a new thread with my issue.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Monitor not enabling bug, profiles becoming 'damaged'</title>
<link>https://www.displayfusion.com/Discussions/View/monitor-not-enabling-bug-profiles-becoming-damaged/?ID=a496646e-d330-406b-ba7b-9e2f8d411817#6</link>
<pubDate>Wed, 22 Mar 2017 23:04:04 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/monitor-not-enabling-bug-profiles-becoming-damaged/?ID=a496646e-d330-406b-ba7b-9e2f8d411817#6</guid>
<category>DisplayFusion</category>
<description><![CDATA[I generally found this problem was due to me having monitors entirely powered off, it hasn't come up in a while for me personally. I don't do ANY display fusion actions, without all monitors in a turned on state - even if it's standby.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I generally found this problem was due to me having monitors entirely powered off, it hasn't come up in a while for me personally. I don't do ANY display fusion actions, without all monitors in a turned on state - even if it's standby.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Monitor not enabling bug, profiles becoming 'damaged'</title>
<link>https://www.displayfusion.com/Discussions/View/monitor-not-enabling-bug-profiles-becoming-damaged/?ID=a496646e-d330-406b-ba7b-9e2f8d411817#5</link>
<pubDate>Wed, 22 Mar 2017 16:27:26 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/monitor-not-enabling-bug-profiles-becoming-damaged/?ID=a496646e-d330-406b-ba7b-9e2f8d411817#5</guid>
<category>DisplayFusion</category>
<description><![CDATA[@Christian: Can you post some more details? How many monitors, connection types, which profiles you're switching from/to when you get an error, etc.
Thanks!]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
@Christian: Can you post some more details? How many monitors, connection types, which profiles you're switching from/to when you get an error, etc.<br/>
<br/>
Thanks!
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Monitor not enabling bug, profiles becoming 'damaged'</title>
<link>https://www.displayfusion.com/Discussions/View/monitor-not-enabling-bug-profiles-becoming-damaged/?ID=a496646e-d330-406b-ba7b-9e2f8d411817#4</link>
<pubDate>Sat, 18 Mar 2017 07:26:43 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/monitor-not-enabling-bug-profiles-becoming-damaged/?ID=a496646e-d330-406b-ba7b-9e2f8d411817#4</guid>
<category>DisplayFusion</category>
<description><![CDATA[Still still doesn't seem to be fixed :/
Is there nothing one can do?]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Still still doesn't seem to be fixed :/<br/>
<br/>
Is there nothing one can do?
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Monitor not enabling bug, profiles becoming 'damaged'</title>
<link>https://www.displayfusion.com/Discussions/View/monitor-not-enabling-bug-profiles-becoming-damaged/?ID=a496646e-d330-406b-ba7b-9e2f8d411817#3</link>
<pubDate>Fri, 06 Nov 2015 23:54:13 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/monitor-not-enabling-bug-profiles-becoming-damaged/?ID=a496646e-d330-406b-ba7b-9e2f8d411817#3</guid>
<category>DisplayFusion</category>
<description><![CDATA[Yeah I extracted the settings, but I didn't get the exe - I'll do that next time  definitely.
Thanks.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Yeah I extracted the settings, but I didn't get the exe - I'll do that next time  definitely.<br/>
Thanks.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Monitor not enabling bug, profiles becoming 'damaged'</title>
<link>https://www.displayfusion.com/Discussions/View/monitor-not-enabling-bug-profiles-becoming-damaged/?ID=a496646e-d330-406b-ba7b-9e2f8d411817#2</link>
<pubDate>Fri, 06 Nov 2015 20:42:09 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/monitor-not-enabling-bug-profiles-becoming-damaged/?ID=a496646e-d330-406b-ba7b-9e2f8d411817#2</guid>
<category>DisplayFusion</category>
<description><![CDATA[Is this still happening with 8.0 Beta 1? (I assume so, just wanted to double-check). The following info would be helpful:
Export of the settings when it's broken
The output from this test program when it's broken: https://www.binaryfortress.com/Files/DisplayFusion/CustomerTest.exe
Export of th...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Is this still happening with 8.0 Beta 1? (I assume so, just wanted to double-check). The following info would be helpful:<br/>
<ul class="ListBullet">
<li>Export of the settings when it's broken</li>
<li>The output from this test program when it's broken: <a href="https://www.binaryfortress.com/Files/DisplayFusion/CustomerTest.exe" target="_blank" rel="nofollow"><b>https://www.binaryfortress.com/Files/DisplayFusion/CustomerTest.exe</b></a></li>
<li>Export of the settings when you've fixed it</li>
<li>The output from this test program when you've fixed it: <a href="https://www.binaryfortress.com/Files/DisplayFusion/CustomerTest.exe" target="_blank" rel="nofollow"><b>https://www.binaryfortress.com/Files/DisplayFusion/CustomerTest.exe</b></a></li></ul>
<br/>
Thanks!
</div>
]]></content:encoded>
</item>
<item>
<title>Monitor not enabling bug, profiles becoming 'damaged'</title>
<link>https://www.displayfusion.com/Discussions/View/monitor-not-enabling-bug-profiles-becoming-damaged/?ID=a496646e-d330-406b-ba7b-9e2f8d411817</link>
<pubDate>Fri, 06 Nov 2015 07:11:57 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/monitor-not-enabling-bug-profiles-becoming-damaged/?ID=a496646e-d330-406b-ba7b-9e2f8d411817</guid>
<category>DisplayFusion</category>
<description><![CDATA[I have an issue where at times, I enable my 3 monitors and the right one won't initialise.
It's strange because if I switch to my "middle and right" profile, DF can still enable the right monitor.
It's as if the "all 3 monitor" profile has become either corrupt or the "monitorid#" or whatever u...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I have an issue where at times, I enable my 3 monitors and the right one won't initialise.<br/>
It's strange because if I switch to my "middle and right" profile, DF can still enable the right monitor.<br/>
It's as if the "all 3 monitor" profile has become either corrupt or the "monitorid#" or whatever unique code you have for it, is getting lost?<br/>
<br/>
I can go into significantly more detail, suffice to say this is a regular occurrence and quite annoying. Been going on for at least a month now (so a couple of beta versions)<br/>
This is fixed by manually going into monitor configuration, re-setting up a profile and re-saving it for "all 3 monitor".<br/>
<br/>
What I'd like to do, is save / collect some data from my machine next time the error occurs, then fix it and compare the saved data, see what's broken.<br/>
<br/>
Is an export of my settings enough?
</div>
]]></content:encoded>
</item>
</channel>
</rss>