<?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: Changing monitor profile messed up Monitor IDs - Forcing Windows to rediscover monitors</title>
<atom:link href="https://www.displayfusion.com/Discussions/RSS/?TopicID=4dc6013f-235b-4b37-b73f-6ebec5178ef1" rel="self" type="application/rss+xml" />
<link>https://www.displayfusion.com/Discussions/RSS/?TopicID=4dc6013f-235b-4b37-b73f-6ebec5178ef1</link>
<description>DisplayFusion RSS: Changing monitor profile messed up Monitor IDs - Forcing Windows to rediscover monitors</description>
<lastBuildDate>Fri, 15 May 2026 21:22:37 GMT</lastBuildDate>
<language>en</language>
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<generator>https://www.displayfusion.com/Discussions/RSS/?TopicID=4dc6013f-235b-4b37-b73f-6ebec5178ef1</generator>
<item>
<title>RE: Changing monitor profile messed up Monitor IDs - Forcing Windows to rediscover monitors</title>
<link>https://www.displayfusion.com/Discussions/View/changing-monitor-profile-messed-up-monitor-ids-forcing-windows-to-rediscover-monitors/?ID=4dc6013f-235b-4b37-b73f-6ebec5178ef1#4</link>
<pubDate>Mon, 21 Aug 2017 09:05:06 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/changing-monitor-profile-messed-up-monitor-ids-forcing-windows-to-rediscover-monitors/?ID=4dc6013f-235b-4b37-b73f-6ebec5178ef1#4</guid>
<category>DisplayFusion</category>
<description><![CDATA[I detailed some of what I did in another post: https://www.displayfusion.com/Discussions/View/monitor-profiles-fix/?ID=5cd32989-e5fd-4636-a12e-84c49bf84cfc#1
I considered forcing the monitor IDs in the registry as you have done but for me a few of the programs open on the correct monitor, but mo...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I detailed some of what I did in another post: <a href="https://www.displayfusion.com/Discussions/View/monitor-profiles-fix/?ID=5cd32989-e5fd-4636-a12e-84c49bf84cfc#1" target="_blank" rel="nofollow"><b>https://www.displayfusion.com/Discussions/View/monitor-profiles-fix/?ID=5cd32989-e5fd-4636-a12e-84c49bf84cfc#1</b></a><br/>
<br/>
I considered forcing the monitor IDs in the registry as you have done but for me a few of the programs open on the correct monitor, but most others are on the "wrong" one.<br/>
<br/>
Keith has said there is a program bug: <a href="https://www.displayfusion.com/Discussions/View/some-issues-with-programs-opens-in-wrong-monitor/?ID=9f05b02a-d6b4-4a69-b047-73be6e886e1f#15" target="_blank" rel="nofollow"><b>https://www.displayfusion.com/Discussions/View/some-issues-with-programs-opens-in-wrong-monitor/?ID=9f05b02a-d6b4-4a69-b047-73be6e886e1f#15</b></a><br/>
<br/>
That was a week ago. Hopefully the next beta will be coming out soon.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Changing monitor profile messed up Monitor IDs - Forcing Windows to rediscover monitors</title>
<link>https://www.displayfusion.com/Discussions/View/changing-monitor-profile-messed-up-monitor-ids-forcing-windows-to-rediscover-monitors/?ID=4dc6013f-235b-4b37-b73f-6ebec5178ef1#3</link>
<pubDate>Mon, 21 Aug 2017 00:35:46 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/changing-monitor-profile-messed-up-monitor-ids-forcing-windows-to-rediscover-monitors/?ID=4dc6013f-235b-4b37-b73f-6ebec5178ef1#3</guid>
<category>DisplayFusion</category>
<description><![CDATA[I had the same problem as you and I had tried that previously.
I've reached out in my own long post with lots of info and I was hoping to hear that at least someone was taking a look at it or that it was acknowledged as a problem.
How are you connecting your monitors? Mine are through a Display...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I had the same problem as you and I had tried that previously.<br/>
<br/>
I've reached out in my own long post with lots of info and I was hoping to hear that at least someone was taking a look at it or that it was acknowledged as a problem. <br/>
<br/>
How are you connecting your monitors? Mine are through a DisplayLink USB 3 dock. I have the same issue *sometimes* when directly connected to my laptop.<br/>
<br/>
I've had to resort to a workaround that is as unelegant as they come. I manually edited the monitor IDs in the registry for my profile. I swapped the numbers of Monitor1_ID and Monitor 2_ID. The thing is, everytime after I apply the profile, the numbers switch back to the values. So I have to keep swapping them.<br/>
<br/>
I can do either 2 things. Lock the registry key which I haven't tried. The second is I wrote a powershell script to import a registry key with the proper IDs. These are the steps it takes to properly apply a profile (even though DF still reads the numbers wrong, the profile is now correct).<br/>
<br/>
Import registry key<br/>
apply monitor profile that extends all 3 monitors<br/>
Import registry key again<br/>
apply desired monitor profile<br/>
<br/>
Then it works. I spent hours figuring this out. I can't even begin to tell you the frustration. I keep hearing and reading that DF just reads whatever Windows does. Well, it doesn't in all cases. Sometimes it will randomly work out of the blue and all my profiles don't need this crazy workaround, so whatever is happening, I bet it is something the developer can fix. I just wish someone on the support team would reach out and I would gladly provide any information and any testing needed.<br/>
<br/>
They're even located not too far from me, I could send them a USB dock to work on.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Changing monitor profile messed up Monitor IDs - Forcing Windows to rediscover monitors</title>
<link>https://www.displayfusion.com/Discussions/View/changing-monitor-profile-messed-up-monitor-ids-forcing-windows-to-rediscover-monitors/?ID=4dc6013f-235b-4b37-b73f-6ebec5178ef1#2</link>
<pubDate>Sun, 20 Aug 2017 22:58:27 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/changing-monitor-profile-messed-up-monitor-ids-forcing-windows-to-rediscover-monitors/?ID=4dc6013f-235b-4b37-b73f-6ebec5178ef1#2</guid>
<category>DisplayFusion</category>
<description><![CDATA[Unfortunately this doesn't help the DF monitor profile problem.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Unfortunately this doesn't help the DF monitor profile problem.
</div>
]]></content:encoded>
</item>
<item>
<title>Changing monitor profile messed up Monitor IDs - Forcing Windows to rediscover monitors</title>
<link>https://www.displayfusion.com/Discussions/View/changing-monitor-profile-messed-up-monitor-ids-forcing-windows-to-rediscover-monitors/?ID=4dc6013f-235b-4b37-b73f-6ebec5178ef1</link>
<pubDate>Sun, 13 Aug 2017 07:53:52 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/changing-monitor-profile-messed-up-monitor-ids-forcing-windows-to-rediscover-monitors/?ID=4dc6013f-235b-4b37-b73f-6ebec5178ef1</guid>
<category>DisplayFusion</category>
<description><![CDATA[As others have commented, sometimes changing monitor profiles in DisplayFusion messes up the ID numbers Windows assigns to the monitors. In my 3-monitor case, some elements stayed with the correct monitor while others got swapped between monitors 2 and 3.
If playing around still doesn't get thin...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
As others have commented, sometimes changing monitor profiles in DisplayFusion messes up the ID numbers Windows assigns to the monitors. In my 3-monitor case, some elements stayed with the correct monitor while others got swapped between monitors 2 and 3. <br/>
<br/>
If playing around still doesn't get things back right, the fix is to force Windows to rediscover the monitors one-by-one. You have to delete two registry keys, then plug-in the monitors one at a time and restart. Apparently this is a known problem in Windows and has been since Vista. Here are links to read more about it along with step-by-step instructions.<br/>
<br/>
See last post in this 7-year-old thread!:<br/>
<a href="https://social.technet.microsoft.com/Forums/office/en-US/30b16266-cbc6-4759-8c30-8d10b46fb7c6/changing-monitor-identities" target="_blank" rel="nofollow"><b>https://social.technet.microsoft.com/Forums/office/en-US/30b16266-cbc6-4759-8c30-8d10b46fb7c6/changing-monitor-identities</b></a><br/>
<br/>
And this one:<br/>
<a href="http://support.displaylink.com/knowledgebase/articles/736116-windows-display-properties-identify-numbers-are" target="_blank" rel="nofollow"><b>http://support.displaylink.com/knowledgebase/articles/736116-windows-display-properties-identify-numbers-are</b></a>
</div>
]]></content:encoded>
</item>
</channel>
</rss>