Dustin L. Howett (MSFT)

> Why should the Windows Terminal window be any less capable of working with the current desktop refresh rate? Because of a bug that we're still trying to pin down.

> > > @MartinMa that's an entirely different thing than the existing conhost.exe, if you tried to run OpenConsolePackage (which is the OSS conhost) you should still have the issue....

If you launch cmd, does powershell start working? I have a theory, but this will help me narrow it down.

Okay, I bet condrv (our kernel driver) isn't being loaded. This is extremely rare, and only happens when no other console applications have been spawned on startup.

I've got an idea how to fix this, but the workaround is simple (launch a commandline app, or be on a non-stripped-out Windows); triaging into 1.x (not backlog), p2

This will best be handled by some combination of #555 and #626.

@hassanuz might be interested in this.

This is something you can do today with a bit of finagling; we'll be looking at what it means to remember SSH connections. The main point of contention is that...

@oising The answer to that depends on how you're reading the console. I think that `ENABLE_VIRTUAL_TERMINAL_INPUT | ENABLE_WINDOW_INPUT` requires you to [`ReadConsoleInput`](https://docs.microsoft.com/en-us/windows/console/readconsoleinput). You'll get different types of [`INPUT_RECORD`](https://docs.microsoft.com/en-us/windows/console/input-record-str): key events...

FWIW: You can find the path to `defaults.json` fairly easily with `Get-AppxPackage`. It won't work well for the unpackaged launch scenario, but it's not one we're really officially supporting. ```powershell...