guide · static export
PC

Reset the Network Stack When Wi-Fi Misbehaves

The three commands that clear a corrupted TCP/IP stack, what they silently remove, and how to verify the result afterwards.

by@guidox updated:10/31/26 time:15 min level:Beginner tested on:Windows 11 24H2 works on:Windows 10, Windows 11 tools:Command Prompt as administrator, PowerShell
TL;DR

Reset with **netsh winsock reset** and **netsh int ip reset**, then flush DNS, renew the address and reboot. The reset also drops filter drivers from VPN and firewall tools.

Before you start

Requirements

  • Admin rights
  • Fifteen minutes
  • The VPN or firewall installer at hand
Step by step

Instructions

01

Note what the reset will remove

The reset clears layered service providers and filter drivers. VPN clients, some antivirus network shields and packet tools install exactly those, and they stop working until reinstalled.

Get-NetAdapterBinding | Where-Object Enabled | Select-Object Name,ComponentID
⚠ warningWrite down the third-party entries in that list. They are the pieces you will have to restore.
02

Reset the Winsock catalog

The catalog holds the layered providers every application uses to open a connection. A broken entry there survives reboots and makes name resolution or sockets fail in one app only.

netsh winsock reset
03

Reset TCP/IP itself

This restores the stack to its default state, including the address mode. Static IP addresses and custom routes are dropped and the adapter returns to DHCP.

netsh int ip reset C:\Temp\ipreset.log
⚠ warningThe log file records which keys were rewritten, which is useful when a machine is on a fixed address in an office.
04

Flush the resolver and renew the lease

Fresh DNS cache and a new lease remove the stale entries a reset leaves behind. Without this step the symptoms sometimes survive the repair.

ipconfig /release & ipconfig /renew & ipconfig /flushdns
05

Reboot and check the result

Winsock changes are only active after a restart. Then check the adapter state and one real connection instead of trusting the commands.

Get-NetAdapter | Select-Object Name,Status,LinkSpeed
tipTest an IP and a name separately: Test-NetConnection 1.1.1.1 -Port 443 proves routing, a name lookup proves DNS.
06

Reset one adapter instead of the stack

When only Wi-Fi misbehaves, restarting that adapter clears the driver state without touching the whole stack. Try this before the heavy reset.

Restart-NetAdapter -Name Wi-Fi -Confirm:$false
Troubleshooting

Common issues

There is no network at all afterwards

The adapter has no lease. Run ipconfig /renew in an elevated console, and reinstall the adapter driver if the interface is missing.

The VPN client no longer connects

Its filter driver was removed. Reinstall the client; the profile and the configuration are kept.

A static address was lost

netsh int ip reset sets the interface back to DHCP. Set the fixed address again in the adapter settings.

The problem survives the reset

The cause is outside the stack: a failing adapter, a router with a bad lease table, or a driver. Check the event log for adapter resets.

FAQ

Frequently asked

Does the reset delete saved Wi-Fi networks?

No. The profiles stay; only the stack and the layered providers are rebuilt.

How often is this the actual fix?

Rarely as a first step. It helps after a failed VPN install, a botched antivirus update or malware cleanup that damaged the catalog.

How to undo this

There is no undo: static addresses, custom routes and third-party filters have to be recreated. The ipreset log shows what was rewritten per key.

Changelog · 1 entry
  1. 2026-10-31
    First version
Interactive version: checklist, feedback, related guides →

Free · no account needed · tracks your progress