WSA_QOS_SENDERS (0X00002AFE) Fix – Path Arrived Error on Windows

When You See This Error

You're trying to print a PDF from a shared folder on a Windows 10 machine, or maybe you're copying files over the network to a server running Windows Server 2019. Suddenly, the job fails, and you get the error: WSA_QOS_SENDERS (0X00002AFE) – At least one path has arrived. I've seen this most often when using SMB file sharing or with old HP LaserJet printers that use TCP/IP direct printing. The network seems fine—ping works, other machines connect—but the specific app gives this cryptic QoS (Quality of Service) error.

What's Really Going On

This error comes from the Windows socket API, specifically the QoS extensions. Windows tries to set up a guaranteed bandwidth path for the app, but something on the network—usually a misconfigured switch, a bad network driver, or a Windows update that changed the QoS policy—causes the path setup to "arrive" in a broken state. The app gets confused because it sees a network path but can't use it. The fix is to either disable QoS for that app, reset the network stack, or clean up the driver.

Fix 1: Disable QoS in Group Policy (Quick Win)

This works for most people. It's a local group policy change. Open Group Policy Editor: Win + R, type gpedit.msc.

1. Go to Computer Configuration > Administrative Templates > Network > QoS Packet Scheduler
2. Double-click Limit reservable bandwidth
3. Set it to Enabled, then change the Bandwidth limit % to 0
4. Hit Apply and OK
5. Reboot your machine

I've had a client last month whose entire print queue died because the default Windows QoS policy reserved 20% bandwidth for apps like Remote Desktop. Setting it to 0 fixed the error immediately.

Fix 2: Reset Winsock and TCP/IP Stack

If group policy doesn't work, the network stack itself is corrupted. Open Command Prompt as Administrator (Win + X > Command Prompt (Admin)).

netsh winsock reset
netsh int ip reset
ipconfig /flushdns

Then restart. This clears the QoS provider list and resets the socket layer. I've fixed dozens of 0X00002AFE errors this way. After the reset, you'll need to reboot for changes to take effect.

Fix 3: Update or Roll Back Network Drivers

Bad drivers cause this. Go to Device Manager (Win + X > Device Manager). Expand Network adapters. Right-click your active network card (usually Realtek or Intel) and pick Update driver. If you already have the latest, try Roll Back Driver if that option is available. A client of mine had a Dell laptop that started throwing this error after a driver update from Windows Update. Rolling back to the Dell-provided driver fixed it.

Fix 4: Disable QoS in the App or Registry

For specific apps like a custom printer driver or legacy software, you can disable QoS at the registry level. Open Registry Editor (regedit).

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile

Look for a DWORD called NetworkThrottlingIndex. If it's not there, create it. Set the value to 0xFFFFFFFF (disable throttling). Also check HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Psched. Create a DWORD NonBestEffortLimit and set it to 0. Reboot.

What If It Still Fails?

If none of that works, you've got a deeper issue. Check your router or switch—disable QoS there too. Also, run sfc /scannow in CMD Admin to repair system files. For Windows Server, check if the QoS Packet Scheduler is enabled in the network adapter settings (uncheck it). I've seen a few cases where a third-party firewall like Norton or McAfee was intercepting QoS packets—disable the firewall temporarily to test. And if you're using Wi-Fi, try a wired connection. The last resort is a network reset via Settings > Network & Internet > Advanced network settings > Network reset. This removes all adapters and resets everything. Takes a reboot and you'll need to reconnect to Wi-Fi.