Fix WSA_QOS_TRAFFIC_CTRL_ERROR (0x00002B06) in 3 steps

The 30-Second Fix: Reset the QoS Provider

This is the first thing I try on every machine with this error. The culprit here is almost always a stale or corrupted QoS policy left behind by a VPN client or a failed Windows update. You don't need to restart anything yet.

1. Open a command prompt as Administrator. Hit Start, type cmd, right-click it, choose "Run as administrator".
2. Run this command:

   netsh int ip reset

3. Then run:

   netsh winsock reset

4. Reboot. That's it.

This clears the TCP/IP stack and Winsock catalog. The netsh int ip reset flushes out corrupt QoS flowspec entries tied to network adapters. I've seen this fix the error on Windows 10 22H2 and Windows 11 23H2 after a Cisco AnyConnect disconnect.

The 5-Minute Fix: Delete the QoS Policy from Registry

If the first step didn't work, the error is likely pinned in the registry. A leftover QoS policy from a VPN or a traffic shaping tool can cause 0x00002B06 every time an app tries to set QoS. Here's where to look:

1. Open Regedit as Administrator.
2. Navigate to:

   HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\QoS

3. Delete the entire QoS key. Right-click it and choose Delete.
4. Also check:

   HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Windows\QoS

5. If it exists, delete it too.
6. Close Regedit and reboot.

Don't bother with deleting individual values — just nuke the whole key. It's safer and faster. I've seen this happen with SonicWall NetExtender and Pulse Secure VPNs leaving junk behind.

The 15+ Minute Fix: Full Network Stack Reset and Group Policy Check

If you're still stuck, something deeper is wrong. Either a Group Policy object is forcing a corrupt QoS entry, or the network adapter driver has a bug that's not letting the flowspec reset cleanly.

Step 1: Check Group Policy

Run gpresult /h c:\gp.html in an admin command prompt. Open that HTML file and search for "QoS". If you see a policy enforcing a QoS setting, talk to your IT team. You can't fix that locally — it's pushed from the domain controller.

Step 2: Reset QoS via netsh (forceful)

This wipes all QoS policies, including those set by apps:

netsh qos delete policy

Then reset everything together:

netsh int ip reset c:\resetlog.txt
netsh winsock reset
netsh winhttp reset proxy

Step 3: Restart the QoS service

Some apps disable it. Make sure it's running:

sc config qwave start= demand
net start qwave

Step 4: Update or reinstall the network adapter driver

Go to Device Manager, find your network adapter (usually "Realtek PCIe GbE Family Controller" or "Intel Ethernet Connection"), right-click, choose "Update driver" -> "Browse my computer" -> "Let me pick from a list". If you see multiple drivers, try an older one. Reboot.

I've had one case where a Killer E2500 driver on an MSI board caused this error every time the system resumed from sleep. Rolling back the driver fixed it permanently.

Step 5: Clean boot to isolate third-party software

Use msconfig, select "Selective startup", uncheck "Load startup items". Reboot. If the error disappears, enable startup items one by one until you find the culprit. VPN clients, firewalls (especially ZoneAlarm and Comodo), and traffic shapers (like NetLimiter) are common triggers.

Pro tip: If you're on a laptop that uses both Wi-Fi and Ethernet, this error sometimes appears only on one interface. Test the app that fails — if it's a video game or an RDP client, try disconnecting one adapter. I've seen it happen on Wi-Fi 6 (Intel AX200) while Ethernet worked fine.

One more thing: if you're running Windows Server 2019 or 2022 with Hyper-V, check that the Hyper-V Virtual Switch Extension isn't broken. Disable and re-enable the vSwitch in Hyper-V Manager. That's a niche case, but I've hit it twice.

That's the whole playbook. Start with the netsh reset, then the registry delete, then the heavy lifting. Nine times out of ten, the first step does it.