Net.Pipe Listener Adapter unavailable in service control manager in Windows Server 2022

Michael Anderson 0 Reputation points
  1. We have .Net Framework 4.8 installed on Windows Server 2022, latest versions of both.
  2. We cannot see Net.Pipe Listener Adapter in the service control manager.
  3. We have tried running the .Net framework repair tool with no luck.
  4. We have tried running the Powershell "Get-Service" command to check if there is a service whose name is like "pipe" with no results.
  5. We have seen the solution in ".Net TNS Listener Adapter is missing Server 2022 and Windows 11" from Microsoft Q&A where you remove .Net Framework 3.5 and 4.8 features and restart the server.
  6. The trouble is that involves uninstalling IIS. We have just set up a number of web applications and don’t want to do that all again.
  7. We have tried just unchecking the "Named Pipe Activation" feature of 4.8 WCF Services and restarting and checking it again with no luck.
  8. Is there any other solution or a patch available, please?


Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,030 questions
Windows Server Setup
Windows Server Setup
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Setup: The procedures involved in preparing a software program or application to operate within a computer or mobile device.
240 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Limitless Technology 43,916 Reputation points

    Hello Bruce,

    Thank you for your question and for reaching out with your question today.

    The issue you’re seeing can be caused by various factors. Here are a few things to consider to help identify and resolve the issue:

    1. While your internet speed is good, latency can still impact remote desktop performance. High latency can result in delayed responses. You might want to run a ping test to the remote server to check for any unusual delays in network response times.
    2. Check if the remote server's resources (CPU, memory, disk) are heavily utilized.
    3. Ensure that your local device has enough resources available (CPU, memory, disk) to handle the remote desktop session smoothly.
    4. Even with good speed, intermittent network disruptions or packet loss can cause lag. Test the connection for stability using tools like continuous ping or network monitoring software.
    5. Sometimes, security software or firewalls can interfere with remote desktop connections. Temporarily disabling such software for testing purposes might help diagnose the issue.
    6. If you're using a VPN or proxy, they could introduce additional latency. Try connecting directly to see if it makes a difference.

    If the reply was helpful, please don’t forget to upvote or accept as answer.