<?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: Bind Failure after Windows 10 November update</title>
<atom:link href="https://www.displayfusion.com/Discussions/RSS/?TopicID=63f29729-b81d-4e49-b041-a72eb43c38dd" rel="self" type="application/rss+xml" />
<link>https://www.displayfusion.com/Discussions/RSS/?TopicID=63f29729-b81d-4e49-b041-a72eb43c38dd</link>
<description>DisplayFusion RSS: Bind Failure after Windows 10 November update</description>
<lastBuildDate>Thu, 30 Apr 2026 03:35:18 GMT</lastBuildDate>
<language>en</language>
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<generator>https://www.displayfusion.com/Discussions/RSS/?TopicID=63f29729-b81d-4e49-b041-a72eb43c38dd</generator>
<item>
<title>RE: Bind Failure after Windows 10 November update</title>
<link>https://www.displayfusion.com/Discussions/View/bind-failure-after-windows-10-november-update/?ID=63f29729-b81d-4e49-b041-a72eb43c38dd#9</link>
<pubDate>Tue, 17 Nov 2015 19:54:43 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/bind-failure-after-windows-10-november-update/?ID=63f29729-b81d-4e49-b041-a72eb43c38dd#9</guid>
<category>DisplayFusion</category>
<description><![CDATA[Thanks for posting the solutions guys! Unfortunately Windows has registered that key combination for itself now, so we've removed it in 7.3.2. Feel free to set the key combination to something else if you need that function]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Thanks for posting the solutions guys! Unfortunately Windows has registered that key combination for itself now, so we've removed it in 7.3.2. Feel free to set the key combination to something else if you need that function <img src="https://www.displayfusion.com/MediaCommon/SVGs/FontAwesome/face-smile.light.svg" alt=":)" style="box-sizing:border-box;position:relative;overflow:hidden;vertical-align:middle !important;width:16px;height:16px;" HelpButtonData=":)" HelpButtonDataAlign="BelowMiddle" />
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Bind Failure after Windows 10 November update</title>
<link>https://www.displayfusion.com/Discussions/View/bind-failure-after-windows-10-november-update/?ID=63f29729-b81d-4e49-b041-a72eb43c38dd#8</link>
<pubDate>Sun, 15 Nov 2015 21:26:52 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/bind-failure-after-windows-10-november-update/?ID=63f29729-b81d-4e49-b041-a72eb43c38dd#8</guid>
<category>DisplayFusion</category>
<description><![CDATA[Right click on the tray icon &gt; Settings &gt; Functions tab on left &gt; look for "Move Window to Previous Monitor and Maximize" &gt; Click on it and hit "Edit" at the top &gt; set shortcut accordingly.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Right click on the tray icon &gt; Settings &gt; Functions tab on left &gt; look for "Move Window to Previous Monitor and Maximize" &gt; Click on it and hit "Edit" at the top &gt; set shortcut accordingly.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Bind Failure after Windows 10 November update</title>
<link>https://www.displayfusion.com/Discussions/View/bind-failure-after-windows-10-november-update/?ID=63f29729-b81d-4e49-b041-a72eb43c38dd#7</link>
<pubDate>Sun, 15 Nov 2015 21:25:30 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/bind-failure-after-windows-10-november-update/?ID=63f29729-b81d-4e49-b041-a72eb43c38dd#7</guid>
<category>DisplayFusion</category>
<description><![CDATA[HI thanks for the info to solve the issue, would you be kind enough to post the steps and where we go to change it. Thanks,.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
HI thanks for the info to solve the issue, would you be kind enough to post the steps and where we go to change it. Thanks,.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Bind Failure after Windows 10 November update</title>
<link>https://www.displayfusion.com/Discussions/View/bind-failure-after-windows-10-november-update/?ID=63f29729-b81d-4e49-b041-a72eb43c38dd#6</link>
<pubDate>Sun, 15 Nov 2015 21:12:36 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/bind-failure-after-windows-10-november-update/?ID=63f29729-b81d-4e49-b041-a72eb43c38dd#6</guid>
<category>DisplayFusion</category>
<description><![CDATA[Workaround for now is apparently to remove the "Win" key from the bind. Seems like the Nov 10th update made Win + E (open This PC) a system-level keybind that apps won't be able to bind over.
I set mine to shift + ctrl + alt + E and the issue went away.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Workaround for now is apparently to remove the "Win" key from the bind. Seems like the Nov 10th update made Win + E (open This PC) a system-level keybind that apps won't be able to bind over.<br/>
<br/>
I set mine to shift + ctrl + alt + E and the issue went away.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Bind Failure after Windows 10 November update</title>
<link>https://www.displayfusion.com/Discussions/View/bind-failure-after-windows-10-november-update/?ID=63f29729-b81d-4e49-b041-a72eb43c38dd#5</link>
<pubDate>Sun, 15 Nov 2015 21:10:43 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/bind-failure-after-windows-10-november-update/?ID=63f29729-b81d-4e49-b041-a72eb43c38dd#5</guid>
<category>DisplayFusion</category>
<description><![CDATA[Yep I get the same thing. Is there a FIX What do we do??]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Yep I get the same thing. Is there a FIX<img src="https://www.displayfusion.com/MediaCommon/SVGs/FontAwesome/face-grimace.light.svg" alt="???" style="box-sizing:border-box;position:relative;overflow:hidden;vertical-align:middle !important;width:16px;height:16px;" HelpButtonData="???" HelpButtonDataAlign="BelowMiddle" /> What do we do??
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Bind Failure after Windows 10 November update</title>
<link>https://www.displayfusion.com/Discussions/View/bind-failure-after-windows-10-november-update/?ID=63f29729-b81d-4e49-b041-a72eb43c38dd#4</link>
<pubDate>Sun, 15 Nov 2015 09:21:38 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/bind-failure-after-windows-10-november-update/?ID=63f29729-b81d-4e49-b041-a72eb43c38dd#4</guid>
<category>DisplayFusion</category>
<description><![CDATA[I get this too, on every boot of windows.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I get this too, on every boot of windows.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Bind Failure after Windows 10 November update</title>
<link>https://www.displayfusion.com/Discussions/View/bind-failure-after-windows-10-november-update/?ID=63f29729-b81d-4e49-b041-a72eb43c38dd#3</link>
<pubDate>Sun, 15 Nov 2015 07:10:30 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/bind-failure-after-windows-10-november-update/?ID=63f29729-b81d-4e49-b041-a72eb43c38dd#3</guid>
<category>DisplayFusion</category>
<description><![CDATA[I got this error too. I rebound the key to ctrl-shift-e and the error went away.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I got this error too. I rebound the key to ctrl-shift-e and the error went away.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Bind Failure after Windows 10 November update</title>
<link>https://www.displayfusion.com/Discussions/View/bind-failure-after-windows-10-november-update/?ID=63f29729-b81d-4e49-b041-a72eb43c38dd#2</link>
<pubDate>Sat, 14 Nov 2015 17:07:53 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/bind-failure-after-windows-10-november-update/?ID=63f29729-b81d-4e49-b041-a72eb43c38dd#2</guid>
<category>DisplayFusion</category>
<description><![CDATA[Yup, I'm having the same issue. Changing it to another key binding doesn't help either, it gives me the error no matter what binding it's set to.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Yup, I'm having the same issue. Changing it to another key binding doesn't help either, it gives me the error no matter what binding it's set to.
</div>
]]></content:encoded>
</item>
<item>
<title>Bind Failure after Windows 10 November update</title>
<link>https://www.displayfusion.com/Discussions/View/bind-failure-after-windows-10-november-update/?ID=63f29729-b81d-4e49-b041-a72eb43c38dd</link>
<pubDate>Sat, 14 Nov 2015 14:22:20 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/bind-failure-after-windows-10-november-update/?ID=63f29729-b81d-4e49-b041-a72eb43c38dd</guid>
<category>DisplayFusion</category>
<description><![CDATA[After an update to the November Windows 10 update I am consistently seeing an error with binding "Ctrl + Win + E" during startup. I don't recall ever going in and assigning any key, so this should be a default problem. Here is the error text:
HotKey Bind Failed:
• Move Window to Previous Monito...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
After an update to the November Windows 10 update I am consistently seeing an error with binding "Ctrl + Win + E" during startup. I don't recall ever going in and assigning any key, so this should be a default problem. Here is the error text:<br/>
<br/>
HotKey Bind Failed:<br/>
 • Move Window to Previous Monitor and Maximize "Ctrl + Win + E"<br/>
<br/>
Key combination might already be in use. There are a few reasons why this can fail:<br/>
- Another hotkey is already using this key combination<br/>
- Another application is already using this key combination<br/>
- A built-in Windows function is using this key combination
</div>
]]></content:encoded>
</item>
</channel>
</rss>