bug#18745:

[Eli Zaretskii]

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Thu, 29 Oct 2015 04:38:47 +0100
> Cc: 18745@debbugs.gnu.org
> 
> Well, mystery solved. It's not a bug or change in Windows 10, it's an 
> incompatibility between CMD.EXE and TCC.EXE (the TakeCommand shell). I 
> usually run everything from inside TakeCommand, so COMSPEC points to TCC.EXE, 
> not CMD.EXE.
> 
> Not sure how to fix it. I suppose "nothing to do, just run the tests with the 
> right COMSPEC" is an option. OTOH, the test is supposed to check for a 
> CreateProcess "deficiency". And certainly 4DOS/4NT/TCC is a quite popular 
> shell.

The CreateProcess deficiency we test there has nothing to do with
trailing whitespace, btw.

Anyway, does it work to put "ComSpec=%windir%\system32\cmd.exe" into
process-environment before running that code?