How to Reset the TCP/IP Stack With netsh in Windows

When the TCP/IP stack itself is the problem

Most connectivity failures live at the edges: the router, the driver, the DNS server. The TCP/IP reset targets the middle — the configuration of the protocol stack itself, which accumulates damage from VPN clients with their virtual adapters, from security suites that unhook and re-hook the stack, from malware and from botched manual configurations. When the stack is sick, the symptoms turn paradoxical: the adapter reports media connected, DHCP never delivers an address, and the machine falls back to a 169.254.x.x APIPA address even though the same cable works on the laptop next to it.

The reset works by rewriting the registry entries of TCP/IP and its companion services back to their first-install values. Nothing of yours is deleted — files, drivers and Wi-Fi profiles stay put — but everything the stack had been told to remember about this machine's network identity is forgotten. That is both its power and its cost: any static configuration will need to be re-entered afterwards.

Running the reset, and the companion commands

Open an elevated command line: press Win+X and pick Terminal (Admin), or search for cmd and choose Run as administrator. Type netsh int ip reset and press Enter — the command quietly resets a batch of registry keys and reports where it logged the details; appending a path, as in netsh int ip reset C:\resetlog.txt, lets you choose where that log lands. If your network runs on IPv6, run netsh int ipv6 reset as well. Neither command shows any visible effect until you restart, because the stack is only rebuilt during the boot.

The reset is usually one move in a sequence. A sensible order for a stubborn machine: netsh winsock reset to rebuild the socket catalog, then netsh int ip reset and netsh int ipv6 reset for the stack, one restart for all of it, and ipconfig /flushdns once you are back. Windows 11 also offers a GUI equivalent — Settings → Network & internet → Advanced network settings → Network reset — but it goes further: it reinstalls every network adapter and removes all known Wi-Fi networks, while the netsh route leaves your wireless profiles intact.

• netsh winsock reset — rebuilds the Winsock socket catalog
• netsh int ip reset — returns the IPv4 stack to factory defaults
• netsh int ipv6 reset — the same for the IPv6 stack
• ipconfig /release then ipconfig /renew — requests a fresh DHCP lease after the reboot
• ipconfig /flushdns — clears the resolver cache so old answers do not linger

After the reboot: what to reconfigure and what to try next

Once the machine is back, reconnect to your network and let DHCP do its work. Anything you had configured statically — a fixed IP for port forwarding, custom DNS servers, a manual IPv6 setup — is gone and needs re-entering in Settings → Network & internet or in the adapter's properties. VPN clients should be started once so they reinstall their virtual adapters cleanly, and security suites that filter traffic sometimes want a repair run before they trust the fresh stack.

If connectivity is still dead after all this, the software layers are exonerated: look to the adapter driver in Device Manager (uninstall it, then reboot so Windows reinstalls it), to the router, or to the hardware itself. And once the network behaves, the deep repairs are done — there is nothing to schedule here. A tool like Kleaner PRO belongs at the other end of maintenance: its scheduled cleanup of temp files, caches and update leftovers keeps the general clutter down, while the stack you have just rebuilt is best left alone.

Questions and Answers

Read next

All articles · FAQ