How to Reset Winsock to Fix Network Issues in Windows

What Winsock is and how its catalog breaks

Winsock — Windows Sockets — is the interface every Windows application uses to open network connections: the API layer between your browser, mail client and messengers on one side and the TCP/IP stack on the other. To let third-party software hook into that traffic, Windows keeps a catalog of providers: antivirus suites, older firewalls, content filters and VPN clients used to register themselves there as layered service providers. Modern Windows 10 and 11 favor a different mechanism, the Windows Filtering Platform, but the catalog still exists — and it can still be left corrupted or out of order.

Damage typically arrives with software removal: an uninstalled VPN, an overhauled security suite or a crash in the middle of an update can leave orphaned entries behind. The result is a machine that associates with Wi-Fi, shows a healthy signal and can even ping IP addresses, while every browser reports that the page cannot be reached. Application logs fill up with Winsock errors 10038, 10050 or 10054 in such cases.

• Wi-Fi shows connected, but every browser says the page cannot be reached
• The trouble started right after removing a VPN, antivirus or firewall product
• Messengers work while browsers fail — or the other way around, a layer-specific symptom
• Applications log socket errors 10038, 10050 or 10054
• A proxy utility was uninstalled and the internet never came back

Running the reset, step by step

Press Win+X and choose Terminal (Admin) — on Windows 10 the entry reads Command Prompt (Admin) — or press Win, type cmd, right-click the result and select Run as administrator. Type netsh winsock reset and press Enter; Windows confirms that the Winsock catalog has been reset and reminds you that a restart is required. You can inspect the current catalog beforehand with netsh winsock show catalog, though in practice the output is long and barely readable — the reset itself acts as the diagnostic.

The reboot is not optional. Only while restarting does Windows re-create the catalog with Microsoft's own providers; logging off or toggling the Wi-Fi switch accomplishes nothing. After the restart, reconnect to your network and test — in the typical case of a one-time corruption, connectivity returns immediately.

What a reset removes — and when to go deeper

The reset drops third-party provider entries and restores the Microsoft defaults; it does not delete Wi-Fi profiles or their passwords, does not touch your IP configuration and does not uninstall anything. Software that genuinely needs its network filter — some VPN clients, parental-control tools and older antivirus suites — may have to be reinstalled or repaired afterwards to get its hook back. If the problem survives the reset, the next layer to try is the TCP/IP stack itself, reset with netsh int ip reset, and after that the adapter driver in Device Manager.

Treat the Winsock reset as a scalpel rather than a routine. There is no reason to run it on a healthy machine or on a schedule — it exists precisely for the aftermath of third-party software gone wrong. If you find yourself resetting it monthly, the real culprit is whatever keeps corrupting the catalog, usually the leftovers of an installer or two security products fighting over the same layer.

Questions and Answers

Read next

All articles · FAQ