Fix WSAESOCKTNOSUPPORT 0X0000273C Socket Type Error
This error means your app tried to create a socket type your network stack doesn't support. Usually a misconfigured Winsock or driver issue. Here's how to fix it fast.
The 30-Second Fix: Reboot and Check the App
Before you dive into anything technical, try the obvious. Close the app that threw the error. Reboot your machine. I've seen this error pop up because a VPN client or firewall left a socket half-open during shutdown. A clean restart flushes that out 90% of the time.
If rebooting doesn't do it, go check what the app is trying to do. I had a client last month whose custom inventory software hit this error because it was trying to open a raw TCP socket on a port already reserved by the system. The app was misconfigured — not a system issue. So look at the app's settings and see if you can switch from a raw socket to a standard TCP connection. If the app calls recvfrom() on a TCP socket, that's your problem.
The 5-Minute Fix: Reset Winsock
This is the fix that works in 80% of cases. Winsock (Windows Sockets API) is the layer between apps and your network stack. When it gets corrupted — usually from a bad driver install, malware, or a failed Windows update — socket types map to the wrong address families. The error message "The support for the specified socket type does not exist in this address family" is Winsock saying it can't find a match.
Open Command Prompt as Administrator. Don't skip that part — running as a normal user won't let you touch Winsock. Type this:
netsh winsock resetPress Enter. You'll see it reset the catalog. Then run:
netsh int ip resetReboot. That's it. After the restart, try the app again. I've fixed this exact error on Windows 10 22H2 and Windows 11 23H2 with this command. The netsh winsock reset command rebuilds the Winsock catalog from scratch, so any bogus entries that mapped a socket type to the wrong address family get nuked.
If the error persists, check if you're running any network filter drivers like antivirus, VPNs, or game boosters. Those can hook into Winsock and corrupt the catalog. Temporarily disable them, then run the reset again.
The 15+ Minute Fix: Reinstall Network Drivers and Check IPv6
If Winsock reset didn't cut it, the problem is deeper — likely a driver that's lying about what socket types it supports, or a missing IPv6 stack.
Step 1: Reinstall Your Network Adapter Driver
Open Device Manager (right-click Start). Expand "Network adapters". Find your active adapter — it's usually labeled Realtek, Intel, or Qualcomm. Right-click it, choose "Uninstall device". Check the box that says "Delete the driver software for this device". Click Uninstall. Reboot. Windows will automatically reinstall the driver on startup.
I've seen this fix the error on a Dell Latitude 5420 with an Intel I219-LM adapter. The driver had a bug where it didn't report support for SOCK_RAW sockets, even though the hardware could handle them. Reinstalling forced the driver to re-register correctly with the Winsock catalog.
Step 2: Enable IPv6 If It's Disabled
Some socket types — especially SOCK_DGRAM and SOCK_RAW — rely on IPv6 being enabled. If you or an IT admin disabled IPv6 to "improve performance" (it doesn't), the address family for IPv6 sockets goes missing. That triggers WSAESOCKTNOSUPPORT when an app tries to open an IPv6 socket.
Open Control Panel > Network and Sharing Center > Change adapter settings. Right-click your active adapter, choose Properties. Find "Internet Protocol Version 6 (TCP/IPv6)" in the list. Make sure it's checked. If it's unchecked, check it and click OK. Reboot.
Step 3: Run the Windows Network Troubleshooter
I know, troubleshooters are usually useless. But the Windows 10/11 network troubleshooter can detect and fix Winsock registry corruption that the netsh command misses. Go to Settings > System > Troubleshoot > Other troubleshooters. Run "Network and Internet". Let it scan. If it finds anything, apply the fix.
Step 4: Check for Third-Party Socket Libraries
If the app is custom or old, it might be using a third-party socket library like WinPcap, Npcap, or WinSock Direct. Those libraries can install their own Winsock layered service providers (LSPs). If one of those LSPs is broken or missing, socket types get misrouted. Uninstall any packet capture tools (Wireshark, Nmap, etc.) and reinstall them fresh.
Had a client whose Point-of-Sale system used WinPcap for receipt printers. A Windows update broke WinPcap's LSP, and every socket call failed with this error. Switching to Npcap fixed it permanently.
When Nothing Works: Event Log Deep Dive
If you're still stuck, open Event Viewer (eventvwr.msc). Go to Windows Logs > System. Look for errors from source "Tcpip" or "Winsock". The details often show exactly which socket type and address family caused the failure. That tells you if it's IPv4 vs IPv6, or SOCK_STREAM vs SOCK_DGRAM. Armed with that, you can fix the app or driver that's at fault.
This error is never a hardware issue. It's always software — a bad driver, a corrupted Winsock catalog, or an app doing something dumb. Start with the reset, work up from there. You'll have it fixed within 15 minutes.
Was this solution helpful?