Static graph-based restore crashes on systems with alternate console encodings

[jeffkl]

NuGet Product Used

dotnet.exe, MSBuild.exe

Product Version

Visual Studio 17.5

Worked before?

Yes, Visual Studio 17.4

Impact

It's more difficult to complete my work

Repro Steps & Context

In Windows Region settings, enable "Use Unicode UTF-8 for worldwide language support"

This seems to make Console.StandardInput have a 3-byte preamble, causing the logic that read the static graph restore arguments to not work correctly.

Reported by @vlada-shubina

Caused by NuGet/NuGet.Client#4772

This is fixed in 17.6

Workaround

Disable the Windows Region setting and reboot.

Verbose Logs

No response

[jeffkl]

Reopening as the original fix isn't good enough. In some scenarios the STDIN encoding by the code that creates the process sees it as UTF8 while the process itself sees SBSCCodePageEncoding.