Reset the Windows network stack with netsh
The nuclear option for broken connectivity: rebuild Winsock and the TCP/IP stack to defaults when adapters show 'no internet' despite everything else working.
01Command
$ netsh winsock reset && netsh int ip reset02What it does
The first command rewrites the Winsock catalog, which third-party software (VPNs, antivirus, proxies) often corrupts with layered service providers; the second resets TCP/IP registry keys under HKLM\SYSTEM\CurrentControlSet\Services\Tcpip. A restart is mandatory — the reset only takes effect on reboot. This wipes static IP and DNS settings back to DHCP, so note them first with `netsh int ip show config`, and it also removes any `netsh interface portproxy` rules you may have set. Before escalating to a reset, try gentler fixes: `ipconfig /flushdns`, `ipconfig /release` + `/renew`, and disabling/re-enabling the adapter.
03Risk
04Undo
✓No undo needed — this command does not change persistent state.
05Sources
- Netsh contexts and commands | Microsoft LearnEvidence: Microsoft documents the netsh winsock and netsh interface contexts, including reset commands that restore their default configurations.
- Netsh - Network Shell - Windows CMDEvidence: SS64 lists netsh commands including 'netsh winsock reset' and 'netsh interface ip reset' for restoring TCP/IP and Winsock defaults.
Last verified: 2026-09-17 · Category: Network
06Related solutions
Use the System File Checker to verify every protected Windows system file against known-good copies and automatically replace the damaged ones.
Diagnose NTFS file system errors and bad sectors on any volume — including the system drive while Windows is running — before committing to a repair.
Use the Deployment Image Servicing and Management tool to detect and repair corruption in the Windows component store, the layer SFC depends on.