title: Named Pipes no longer a thing in Windows 10 version 1709?
body: <p>I was trying to work with Named Pipe as a communication channel between injected stubs in various processes.</p>
  
  <p>I was <a href="https://msdn.microsoft.com/en-us/library/windows/desktop/mt595898(v=vs.85).aspx" rel="noreferrer">reading</a> and it states</p>
  
  <blockquote>
    <p>Process Isolation</p>
    
    <p>Sandboxing the application kernel objects, the AppContainer environment prevents the application from influencing, or being influenced by, other application processes. This prevents a properly contained application from corrupting other processes in the event of an exception.</p>
  </blockquote>
  
  <p>It also states <a href="https://msdn.microsoft.com/en-us/library/windows/desktop/aa365146(v=vs.85).aspx" rel="noreferrer">here</a> that</p>
  
  <blockquote>
    <p>Windows 10, version 1709:  Pipes are only supported within an app-container; ie, from one UWP process to another UWP process that's part of the same app. Also, named pipes must use the syntax "\.\pipe\LOCAL\" for the pipe name.</p>
  </blockquote>
  
  <p>Does this mean I can no longer access kernel objects from <code>NtFsControlFile (FSCTL_PIPE_LISTEN, FSCTL_PIPE_WAIT, FSCTL_PIPE_DISCONNECT)</code> to communicate with pipes in other processes than my own App Container? Or is it simply saying that the semantics of this operation changed?</p>
  
  <p>My question is, does this change implicate an actual problem, or can I still use one named pipe from one process to talk with another; but it's not advised to do so?</p>