Windows pipes appear to still be second-class citizens. Look at this mess: http://stackoverflow.com/questions/34504970/non-blocking-rea...

The eventual solution using SetNamedPipeHandleState isn't really supported: https://msdn.microsoft.com/en-us/library/windows/desktop/aa3... "Note that nonblocking mode is supported for compatibility with Microsoft LAN Manager version 2.0 and should not be used to achieve asynchronous input and output (I/O) with named pipes."