No keyboard input in Windows Terminal running with "runas /netonly user:<username>" flags from elevated shell

### Windows Terminal version (or Windows build number)

10.0.19042.0, 1.7.1091.0

### Other Software

Guest OS Windows 10 20H2 (10.0.19042.0) inside Oracle VM VirtualBox (6.1.20 r143896). Not in domain
Host Ubuntu 20.04
Windows Terminal 1.7.1091.0

### Steps to reproduce

1. Run cmd (or Windows Terminal) as administrator
2. Run "runas /netonly /user:%username% wt.exe"
*wt.exe linking to Windows Terminal executable
3. Windows Terminal windows opens, but keyboard input is not working

### Expected Behavior

Expecting keyboard to work in Windows Terminal's command promt.
When running not elevated cmd (or Windows Terminal) and launching Windows Terminal via "runas..." (from non elevated shell) everything works fine.

### Actual Behavior

No keyboard input in Windows Terminal launched from elevated shell via "runas...". Mouse selecting and clicking (copy/paste) works fine.

Reproduce the issue in Windows 10 20H2 using an elevated cmd or Windows Terminal, then run `runas /netonly /user:%username% wt.exe` and compare it with the non-elevated case. Investigate why keyboard input fails while mouse selection and copy/paste still work; done means keyboard input works in the elevated-shell scenario without regressing the working case.

Written by the indexing model from the issue text.