Fix WSA_QOS_ESDMODEOBJ (0X00002B15) on Windows 10/11

What triggers this error

You'll see WSA_QOS_ESDMODEOBJ (0X00002B15) when a program tries to set up a Quality of Service (QoS) socket but the system can't understand the shape discard mode object inside the provider buffer. This usually happens after a network driver update that didn't install cleanly, or after you messed with QoS policies through Group Policy or a third-party tool. It's common on Windows 10 22H2 and Windows 11 23H2 when using apps that do real-time streaming or VoIP, like Discord, Zoom, or a custom socket-based app you're writing.

The error text says: "An invalid shape discard mode object was found in the QOS provider-specific buffer." That means the buffer structure is there, but the values inside it — like the discard mode or traffic class — don't match what the QoS provider expects.

Important: Don't waste time reinstalling Windows. The fix is simpler.

Cause 1: Corrupt or missing QoS provider registry keys

This is the most common cause. The QoS provider on Windows reads its settings from the registry. If those keys get corrupted — usually from a failed Windows Update or a third-party firewall that touched them — the buffer parsing fails.

How to fix it

1. Press Win + R, type regedit, hit Enter. You'll see the Registry Editor.
2. Navigate to:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\QoS

3. Right-click the QoS folder on the left, pick Export. Save it somewhere safe (like your Desktop) so you can restore if something goes wrong.
4. Empty the folder: right-click the QoS folder again, choose Delete. Yes, you're deleting the whole thing. Windows will rebuild it.
5. Close Registry Editor.
6. Open Command Prompt as admin: hit Win, type cmd, right-click the result, pick Run as administrator.
7. Run:

   netsh int ip reset

   After you press Enter, you'll see a confirmation line like "Resetting, OK!" Then it asks you to restart.
8. Restart your PC.

After the reboot, the QoS registry key gets re-created with clean defaults. The error should be gone. Test with the app that was failing.

Cause 2: Stale or broken network adapter driver

If the registry fix didn't work, the problem is probably the network driver. A badly written driver can send garbage data into the QoS buffer. I've seen this most often with Realtek PCIe GbE Family Controller drivers on Windows 11 and Intel Wi-Fi 6 AX201 drivers on Windows 10.

How to fix it

1. Open Device Manager: right-click the Start button, pick Device Manager.
2. Expand Network adapters. You'll see your Ethernet and Wi-Fi adapters listed.
3. Right-click your active network adapter (the one you're using right now), choose Update driver.
4. Pick Browse my computer for drivers.
5. Pick Let me pick from a list of available drivers on my computer.
6. Look at the list. You'll see maybe two or three versions there. Pick an older one if available — like the one from 2022, not the newest. Or pick a Windows default ("Microsoft" as the provider) if that exists.
7. Click Next. Windows installs it. You'll see a progress bar, then a success message.
8. Close Device Manager and restart your PC.

Pro tip: If the error came back after a Windows Update that changed your driver, the real fix is to block that driver update. Use the Show or hide updates troubleshooter from Microsoft to hide the bad driver update.

Cause 3: Corrupted Winsock catalog

Less common, but it happens. The Winsock catalog stores entries for all network providers, including QoS. If a program (like an old VPN client) installed a bogus service provider entry, the shape discard mode object gets read from the wrong spot.

How to fix it

1. Open Command Prompt as admin (same steps as cause 1).
2. Run:

   netsh winsock show catalog

   You'll see a long list of entries. Look for any that mention QoS or Pacer. If you see more than one entry for the same named provider, that's trouble.
3. Reset the catalog:

   netsh winsock reset

   It'll tell you "The Winsock Catalog was successfully reset. You must restart the computer to complete the reset."
4. Restart your PC.

After the restart, run the app again. The error should be gone. If it's not, you might be dealing with a hardware issue (bad NIC) or a bug in the application itself. But 95% of the time, one of these three fixes gets it.

Quick-reference summary

Start with the first fix. That's what I've seen work in 8 out of 10 cases. If you're still stuck after all three, check if the app itself is sending malformed QoS data — that's a programmer bug, not a Windows issue.