<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.18362.418]
Windows Terminal version (if applicable): Version: 0.6.2951.0"><pre lang="none" class="notranslate"><code class="notranslate">Windows build number: Microsoft Windows [Version 10.0.18362.418]
Windows Terminal version (if applicable): Version: 0.6.2951.0
</code></pre></div>
<h1 dir="auto">Steps to reproduce</h1>
<p dir="auto">1.) Set the initialRows value to 30, and open a new wt instance<br>
2.) Shrink the window to approximately half the size vertically (Drag the bottom up)<br>
3.) Spam a few invalid commands (asd, &lt;Enter&gt;, asd, &lt;Enter&gt;, asd, &lt;Enter&gt;, asd, &lt;Enter&gt;, asd, &lt;Enter&gt;, asd, &lt;Enter&gt;) until the scrollbar appears (It will appear later than expected)<br>
4.) Note that you unable to scroll to the current input location</p>

<h1 dir="auto">Expected behavior</h1>
<p dir="auto">You are able to scroll to the current input location</p>
<h1 dir="auto">Actual behavior</h1>
<p dir="auto">You are unable to scroll to the current input location without resizing. The scrollbar also only appears when the lines exceed the initialRows value and ignore the actual window height.</p>
<p dir="auto">Similar to <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="459617028" data-permission-text="Title is private" data-url="https://github.com/microsoft/terminal/issues/1494" data-hovercard-type="issue" data-hovercard-url="/microsoft/terminal/issues/1494/hovercard" href="https://github.com/microsoft/terminal/issues/1494">#1494</a>, but that one deals more with the scroll bar not working at all more so than the scrollbar scrolling to the incorrect location / appearing later than expected.</p>
<h1 dir="auto">Environment</h1>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Windows build number: 18972

Any other software?: WSL installed"><pre lang="none" class="notranslate"><code class="notranslate">Windows build number: 18972

Any other software?: WSL installed
</code></pre></div>
<h1 dir="auto">Steps to reproduce</h1>
<ul dir="auto">
<li>Sign out of Windows</li>
<li>Sign back in</li>
<li>Start Terminal really quickly and open up a WSL instance</li>
<li>The WSL instance does not have Windows file paths connected to it (e.g: typing in <code class="notranslate">cmd.exe</code> fails)</li>
</ul>

<h1 dir="auto">Expected behavior</h1>
<ul dir="auto">
<li>Even if you open up WSL quickly it should add Windows paths correctly.</li>
</ul>

<h1 dir="auto">Actual behavior</h1>
<ul dir="auto">
<li>Opening WSL quickly from Windows Terminal upon signing in does not add in Windows file paths correctly</li>
</ul>

<h1 dir="auto">Additional notes</h1>
<p dir="auto">We (the WSL team) don't think this is a WSL specific issue since we use environment variables to add the Windows path. If you open up a CMD window and run <code class="notranslate">wsl</code> very quickly upon startup you still get the correct Windows paths added. This seems to be an issue with how Windows Terminal treats environment variables.</p>