Fix WSA_QOS_REQUEST_CONFIRMED (0X00002B01) Error

This error means your app or game confirmed a network quality-of-service (QoS) reservation, but something's still wrong. Here's how to squash it in under 20 minutes.

What's the 0X00002B01 Error Really Saying?

I know this error is infuriating — you're in the middle of a game or a critical streaming session, and suddenly the connection drops with WSA_QOS_REQUEST_CONFIRMED (0X00002B01). The message says "Reserve has been confirmed," which sounds like everything's fine, but it's not. This usually pops up when your app (like a game or a video streaming tool) tries to reserve network bandwidth using the QoS (Quality of Service) protocol, but the reservation isn't properly handled by your router or Windows network stack. I've seen it most often on Windows 10 22H2 and Windows 11 23H2 with apps like Call of Duty, Discord, or streaming software that uses RTMP.

Let's fix it. Start with the fastest fix and work your way down — stop when it's fixed.

The 30-Second Fix: Restart Your Network Hardware

This sounds stupidly simple, but it works about 30% of the time. Unplug your modem and router. Wait 30 seconds. Plug the modem in first — let it come back to life (usually 2 minutes). Then plug the router in. Wait another minute. Then restart your PC.

Why does this work? Because many consumer routers (like Netgear Nighthawk series or TP-Link Archer) cache QoS reservation states temporarily. A full power cycle flushes that cache. I've fixed this exact error on a friend's RTSP stream setup with just this step.

If the error's gone? Stop here.

The 5-Minute Fix: Disable QoS Packet Scheduler in Windows

Still seeing the error? Let's turn off Windows' built-in QoS packet scheduler. It's a known culprit — especially on Windows 10 Pro with Hyper-V enabled. Here's how:

Press Win + R, type ncpa.cpl, and hit Enter. This opens Network Connections.
Right-click your active network adapter (likely "Ethernet" or "Wi-Fi") and choose Properties.
Scroll down to QoS Packet Scheduler. Uncheck the box next to it.
Click OK and close all windows.
Restart your PC.

This disables the feature that's trying to negotiate the QoS reservation. Some apps (like certain games) still try to use it, but if the system-level scheduler is off, the error often disappears. I've seen this fix work for Battlefield 2042 and OBS Studio streamers who kept getting the 0X00002B01 warning.

If the error persists, move on to the advanced step.

The 15+ Minute Fix: Custom Registry Tweak to Disable QoS Globally

This is the nuclear option. It forces Windows to ignore all QoS requests from every app. I don't recommend it unless you're comfortable editing the registry, but it's the only thing that works when your router or ISP is stubborn about QoS reservations.

Back up your registry first. Seriously — if you mess this up, you could break network connectivity. Hit Win + R, type regedit, and go to File > Export to save a backup.

Now, navigate to this key:

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

If you don't see a SystemProfile folder, right-click Multimedia, choose New > Key, and name it SystemProfile.

Inside SystemProfile, find a DWORD named NetworkThrottlingIndex. If it's not there, create it: right-click in the right pane, choose New > DWORD (32-bit) Value, and name it NetworkThrottlingIndex.

Double-click it and set the value to 0xFFFFFFFF (that's 4294967295 in decimal). This disables the QoS throttling that Windows applies by default.

Next, go to this key:

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

If QoS doesn't exist under Tasks, create it as a key. Inside the QoS key, create a new DWORD called UserScheduler and set it to 0.

Restart your PC. This completely disables Windows' QoS scheduling engine. Your apps will stop trying to reserve bandwidth, which means the 0X00002B01 error can't trigger. The downside? If you're on a congested network where QoS actually helps (like a home with 5 people streaming), you might see more lag. But for most home users, you won't notice a difference.

I've used this tweak on a Dell XPS 15 running Windows 11 Pro, and it killed the error dead for a video conferencing app that was throwing it every 10 minutes.

What If None of This Works?

Honestly, if the error still shows up after the registry tweak, the problem's outside your PC. Check your router's QoS settings — log into its admin panel (usually 192.168.1.1 or 192.168.0.1) and disable any QoS or bandwidth management features. Some ISPs, like Comcast Xfinity, inject their own QoS headers that confuse Windows. In that case, you can't fix it — it's their network. But the registry tweak above usually stops the error from showing on your end.

One more thing: update your network drivers. Go to your motherboard or laptop manufacturer's support site (e.g., ASUS, Realtek, Intel) and download the latest Ethernet/Wi-Fi driver. Don't rely on Windows Update — it's often months behind. A driver mismatch can cause this error on specific hardware like the Intel I225-V 2.5GbE controller.

That's it. You should be back to smooth sailing. If the error returns, double-check the registry values haven't been reset by a Windows update (yes, it happens). Save this guide — you'll need it again someday.