https://www.displayfusion.com/Discussions/RSS/?TopicID=21e49c6e-a2e3-483a-84a3-6be9b5c55373 DisplayFusion RSS: Window Location with CMD/BAT windows Sat, 18 Apr 2026 08:40:34 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=21e49c6e-a2e3-483a-84a3-6be9b5c55373 https://www.displayfusion.com/Discussions/View/window-location-with-cmdbat-windows/?ID=21e49c6e-a2e3-483a-84a3-6be9b5c55373#4 Thu, 05 Dec 2013 14:14:18 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/window-location-with-cmdbat-windows/?ID=21e49c6e-a2e3-483a-84a3-6be9b5c55373#4 DisplayFusion Awesome, glad to hear it's all good! ]]> https://www.displayfusion.com/Discussions/View/window-location-with-cmdbat-windows/?ID=21e49c6e-a2e3-483a-84a3-6be9b5c55373#3 Thu, 05 Dec 2013 13:44:11 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/window-location-with-cmdbat-windows/?ID=21e49c6e-a2e3-483a-84a3-6be9b5c55373#3 DisplayFusion Yes, it now works. I deleted the original "Windows Location" entry then created it from scratch and it works fine. Don't know what I did initially to break it. Thanks. ]]> https://www.displayfusion.com/Discussions/View/window-location-with-cmdbat-windows/?ID=21e49c6e-a2e3-483a-84a3-6be9b5c55373#2 Wed, 04 Dec 2013 19:06:15 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/window-location-with-cmdbat-windows/?ID=21e49c6e-a2e3-483a-84a3-6be9b5c55373#2 DisplayFusion I was able to have .BAT files launch and move to the specified monitor using Window Location. I've attached a screenshot of the rule I created. Could you give that a try? ]]> https://www.displayfusion.com/Discussions/View/window-location-with-cmdbat-windows/?ID=21e49c6e-a2e3-483a-84a3-6be9b5c55373 Tue, 03 Dec 2013 17:28:06 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/window-location-with-cmdbat-windows/?ID=21e49c6e-a2e3-483a-84a3-6be9b5c55373 DisplayFusion I'm using Windows 7 Pro x64 and DisplayFusion v5.1.1. Calls to .BAT, .CMD, etc. or their shortcuts insist on using monitor 1, even if I set the Window Location and use a delay. However, using the SHIFT+WIN+X key combination does move the CMD window to monitor 2.

Have you found a resolution to this behavior aside from using the hotkey combination?

Calls to PowerShell script initially used monitor 1 but correctly respond to changing the Window Location to monitor 2. I mention this because both CMD and PowerShell invoke a operational "shell" within the Windows environment. ]]>