Command Prompt (cmd.exe) - Starts with no output on start after typing a character

When using cmd.exe (Path: C:\Windows\System32\cmd.exe), when you open the integrated terminal, everything is fine until you type on character, then the ouput bugs out for a second. This isnt a huge problem, but still annoys me.

When i open the integrated terminal (notice the missing block cursor as indication of this bug possibly):

After typing approximately 1 character:

>inb4 use powershell, loser

• VSCode Version: 1.33.1
• OS Version: Windows 10 1809

Steps to Reproduce:

1. type "cls"
   OR
2. run your command like normal, trigger your OCD instead

Does this issue occur when all extensions are disabled?: Yes/No

[Tyriar]

This is a bug in Windows 10 1809, unfortunately we have no way to work around the issue so you will need to wait until you get the next version of Windows 10 (1903).

/duplicate #57803

Alright, thank you!