<p dir="auto">On: <code class="notranslate">Microsoft Windows [Version 10.0.17763.134]</code></p>
<p dir="auto">I have implemented conpty in my terminal emulator:<br>
<a href="https://github.com/wez/wezterm">https://github.com/wez/wezterm</a></p>
<p dir="auto">I can successfully run <code class="notranslate">target\debug\wezterm.exe</code> to spawn console applications such as <code class="notranslate">cmd.exe</code>  <code class="notranslate">powershell.exe</code> and <code class="notranslate">bash</code>.</p>
<p dir="auto">The issue I'm seeing is that when I launch bash, either indirectly via <code class="notranslate">cmd.exe</code> or directly via the bash launcher, conpty seems to swallow the mouse reporting escape sequences; I don't see them being received by my terminal parser, and thus <code class="notranslate">vim</code> has no effective mouse support despite being configured with <code class="notranslate">set mouse=a</code>.</p>
<p dir="auto">Running the same WSL install via <code class="notranslate">wsl-terminal</code> does have working mouse support, and <code class="notranslate">wezterm</code> has been my daily driver on Linux for about a year with working mouse support, so we can rule out an obvious misconfiguration with <code class="notranslate">vim</code> and the parser in <code class="notranslate">wezterm</code>.</p>
<p dir="auto">I've also tried <code class="notranslate">echo -e "\e[?1000h"</code> to manually enable mouse reporting from the shell; normally (on linux and via wsl-terminal) this causes clicks in the terminal to send data to the shell (which appears as garbage input), but when running my terminal with conpty, these are also swallowed up somewhere.</p>
<p dir="auto">Is there something special needed for the apps that I spawn into my pty to be able to work with the mouse?</p>
<p dir="auto">In case you want to double check the key portion of the code, the relevant file is:<br>
<a href="https://github.com/wez/wezterm/blob/master/src/winpty.rs">https://github.com/wez/wezterm/blob/master/src/winpty.rs</a><br>
The flow is to <code class="notranslate">CreatePipe</code> a pair of pipes, <code class="notranslate">CreatePseudoConsole</code>, and then pass that to a spawned child via the threadproc attributes, as the samples in the MSDN docs and this repo also do.</p>
<h1 dir="auto">Environment</h1>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Windows build number: 10.0.18362.267
Windows Terminal version (if applicable): Windows Store version (latest)

Windows Terminal (Dev Build)"><pre lang="none" class="notranslate"><code class="notranslate">Windows build number: 10.0.18362.267
Windows Terminal version (if applicable): Windows Store version (latest)

Windows Terminal (Dev Build)
</code></pre></div>
<h1 dir="auto">Steps to reproduce</h1>
<p dir="auto">I have build Terminal from source and am using it successfully, but I would like to try the version from the Windows Store. I have downloaded it, but when I try to launch it, it immediately terminates without any other error.</p>
<p dir="auto">The exact sequence is:</p>
<blockquote>
<p dir="auto">Start Menu<br>
Click on "Windows Terminal (Preview)"</p>
</blockquote>
<h1 dir="auto">Expected behavior</h1>
<p dir="auto">I expect both versions to run on the same instance of Windows, if the manual build runs, then the pre-compiled should also run?</p>
<h1 dir="auto">Actual behavior</h1>
<p dir="auto">I get a quick flash of a terminal window - it is not blank (as reported elsewhere). It is a quick flash and then immediately it terminates. Nothing on the taskbar, nothing in the process list, no error messages, etc.</p>
<h1 dir="auto">Additional Information</h1>
<p dir="auto">There are no updates pending on the Windows Store, and the Dev Build version runs fine.</p>
<p dir="auto">I looked at <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="472052836" data-permission-text="Title is private" data-url="https://github.com/microsoft/terminal/issues/2073" data-hovercard-type="issue" data-hovercard-url="/microsoft/terminal/issues/2073/hovercard" href="https://github.com/microsoft/terminal/issues/2073">#2073</a> because the symptoms are the same, but I am not running with elevated privileges "Run as administrator" (ie, right-click on the icon).</p>