Show a more descriptive error message when the ConptyConnection fails to start for some reason

[RufusJWB]

Description of the new feature/enhancement

Show a speaking error message, when it is necessary to run Terminal with admin privileges. See #4272 for the problem

Proposed technical implementation details (optional)

[KalleOlaviNiemitalo]

How about just displaying the error message that matches the error code, like so:

[error 0x800702e4 when launching `C:\Program Files\PowerShell\6\pwsh.exe']
The requested operation requires elevation.

Or does Windows Terminal have to recognize the 0x800702e4 code specifically and display something more verbose?

[RufusJWB]

I think displaying the error message would be perfectly fine. I had to google it. With the error message, this wouldn't have been necessary.

[KalleOlaviNiemitalo]

Could even extend that to process exit codes that look like NTSTATUS error codes:

[process exited with code 3221225786]
The application terminated as a result of a CTRL+C.

That would have a greater risk of false matches, though.

[zadjii-msft]

This isn't a bad idea, and I bet @DHowett thought about something like this when he first added the error codes

[DHowett]

Yeah, we can definitely do better with these error messages!

[zadjii-msft]

For those who'd like to try this themselves, I added a similar kind of error message in #10045.

Collected relevant error messages:

Symbolic Name	Error Description	Header
ERROR_ELEVATION_REQUIRED	The requested operation requires elevation.	winerror.h
STATUS_CONTROL_C_EXIT	{Application Exit by CTRL+C} The application terminated as a result of a CTRL+C.	ntstatus.h
MSG_DIR_BAD_COMMAND_OR_FILE	'%1' is not recognized as an internal or external command, operable program or batch file.	cmdmsg.h