My team have encountered a weird bug with the mintty terminal packaged with MSYS2 when running our Textual app.

The Problem:

• When running our app using MSYS2's mintty terminal, we can't click on any of the buttons in the console.
• This behaviour is present across the wide range of Windows 10 versions we work with (Windows 10 Server 2016 & 2019, Windows 10 Professional & Home).
• This problem is not present in Cygwin's mintty terminal on these same Windows 10 versions; the Textual app's buttons all work as intended.
• This is unique to Windows 10, as users on the MSYS2 Discord channel have not been able to replicate the issue on Windows 11.
• These are externally managed PCs, so updating them is out of the question.

What We've Tried So Far:

• This problem does not occur when MSYS2 in run via Windows Terminal. However, it is not supported for the Windows 10 versions present on the PCs we manage.
• We found a workaround where we run an MSYS2 session in a Command Prompt console.
  • This involved creating a Command Prompt shortcut and pointing to MSYS2 in the "Target" field as follows: cmd.exe /k "C:\msys64\msys2_shell.cmd -defterm -no-start -ucrt64 -shell bash".
  • The Textual app runs in that case; the buttons are clickable, although the UI occasionally displays funny characters.
• However, updating msys2-runtime to >3.5.7-2-x86_64 causes even this Command Prompt console workaround to fail.

Advice on why the Textual app's behaviour on both Cygwin and MSYS2's mintty terminals differ so greatly, and on resolving this issue, would be much appreciated, thanks!