Why can I use named pipes to connect to SQL Server even if it's been disabled? Why can I still use named pipes to connect to SQL Server even if it's been disabled? I'm on SQL Server 2016 doing the testing. I have recorded my operation in this youtube video: https://www.youtube.com/watch?v=4lvkbwsspZc Hope someone can point me the right direction.
Check the SQL Server error log for the named pipes provider messages.  With named pipes enabled, you should see messages like those below and be able to connect both locally and remotely over named pipes:

Server local connection provider is ready to accept connection on (named pipe)
Server named pipe provider is ready to accept connection on (named pipe)

With named pipes disabled, you should see only local connection provider message(s).  You'll still be able to connect locally via named pipes (over shared memory) but not remotely via named pipes.