"This socket is closed" error in Node v7.1.0 (Windows only)

Calling vorpal.show(); in Node v7.1.0 throws the following error:
```sh
events.js:160
throw er; // Unhandled 'error' event
^

Error: This socket is closed
at WriteStream.Socket._writeGeneric (net.js:683:19)
at WriteStream.Socket._write (net.js:734:8)
at doWrite (_stream_writable.js:334:12)
at writeOrBuffer (_stream_writable.js:320:5)
at WriteStream.Writable.write (_stream_writable.js:247:11)
at WriteStream.Socket.write (net.js:661:40)
at Console.log (console.js:43:16)
at UI.prompt (C:\***\Scripts\node_modules\vorpal\dist\ui.js:233:17)
at Vorpal.vorpal._prompt (C:\***\node_modules\vorpal\dist\vorpal.js:612:15)
at UI.attach (C:\***\node_modules\vorpal\dist\ui.js:400:19)
```
In macOS/Node v7.1.0 it works fine.

Reproduce `vorpal.show()` on Windows with Node v7.1.0 and compare the working macOS behavior. The stack points to dist/ui.js around UI.prompt and dist/vorpal.js around _prompt; trace the closed stream and confirm that the interactive prompt starts without an unhandled socket error.

Written by the indexing model from the issue text.