<h1 dir="auto">Environment</h1>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Windows build number: Microsoft Windows [Version 10.0.19042.330]  
PowerToys version: v0.19.1
PowerToy module for which you are reporting the bug (if applicable): FancyZones"><pre class="notranslate"><code class="notranslate">Windows build number: Microsoft Windows [Version 10.0.19042.330]  
PowerToys version: v0.19.1
PowerToy module for which you are reporting the bug (if applicable): FancyZones
</code></pre></div>
<h1 dir="auto">Steps to reproduce</h1>
<ol dir="auto">
<li>Requires 2 monitors<br>
1a. May require using a non-admin account</li>
<li>Show taskbar buttons on: Taskbar where window is open</li>
<li>Open Windows Terminal and use FancyZones to "snap" to zone on non-default monitor</li>
<li>Reboot computer (or possibly just sign out and back in)</li>
<li>Open Windows Terminal</li>
</ol>
<h1 dir="auto">Expected behavior</h1>
<p dir="auto">Windows Terminal taskbar button and window will both appear on the non-default monitor. Window will be "snapped" to same zone as before.</p>
<h1 dir="auto">Actual behavior</h1>
<p dir="auto">Windows Terminal taskber button appears on the default monitor while the window will be "snapped" to the correct zone on the non-default monitor.</p>
<p dir="auto">By default new windows are opened on primary monitor (some application introduce their own special positioning). If we have zone history for some application on secondary monitor, and that monitor is active, application window will be opened there, otherwise we fallback to default windows behavior and that window is opened on primary monitor.<br>
Even if we don't have app history for that application on active monitor, we should open it there, with respect of window width and height.</p>