title: START /B with php/node/python script doesn't work as expected
body: <p>I start a shell and I run the following command:</p>
  
  <pre><code>START "" /B php test.php&gt;nul 2&gt;&amp;1
  </code></pre>
  
  <p>For the purposes of this post, test.php consists of 1 line: file_put_contents("test", "test");</p>
  
  <p>You'd expect it to instantly create a file called test, however it doesn't.
  Instead, when I enter the command and hit enter, nothing happens. However, in the same command window, if I hit the enter key once more, the script will run.</p>
  
  <p>I've tried the equivalent command with node, python2 and python3. They all do the same thing, although python3 oiddly enough requires 2 enter key presses before the script is run.</p>
  
  <p>This appears to be a quirk when running START /B with script interpreters. If I ran START /B with an .exe or .bat then it runs as expected.</p>
  
  <p>Now, obviously I don't need to run a background process that creates a file named 'test'. What I need it to do is to start a daemon process written in php and a daemon process written in nodejs, one after the other in the same terminal.</p>
  
  <p>I've also noticed if I write these commands to a batch file and run them by double clicking the batch file instead of calling it from the shell, then it all runs as expected.</p>
  
  <p>Please help. I've been wrestling with this problem for 2 days now.</p>
  
  <p>EDIT:</p>
  
  <p>I've just found that this problem is unique to my computer, running on Windows 10. I tried on Windows 7 and Windows XP and they did not require extra return inputs from me to run the script...</p>
  
  <p>I've just tried booting up in safe mode and clearing my path variables. Still it persists.
  I wonder if this is a bug/feature of Windows 10?
  How the hell do I diagnose and fix this?</p>
  
  <p>EDIT 2:</p>
  
  <p>Just tested the same script on a Windows 8 machine, which unexpectedly does exactly what my Windows 10 machine does. SO it looks like only Windows 8 and Windows 10 have this problem... And using legacy mode makes no difference.
  What the FFFFFFFFFnnngggghhhrrr... I can't find anyone reporting this issue anywhere.</p>
  
  <p>Here's a gif animation of exactly what happens:</p>
  
  <p><a href="https://i.stack.imgur.com/MwbYp.gif" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/MwbYp.gif" alt="enter image description here"></a></p>
  
  <p>Proof that the script is only run on the second return key press.</p>