Build Windows network reset commands - winsock, TCP/IP, flush DNS.
When a Windows PC connects to Wi-Fi but cannot load pages, gets stuck on a stale IP, or fails after a VPN or malware cleanup, resetting the network stack often fixes it. This builder gives you the precise commands for the specific layer that is broken — from a quick DNS flush to a full Winsock and TCP/IP reset — so you do not over-reset and lose custom settings unnecessarily.
| Task | Command | Reboot? |
|---|---|---|
| Flush DNS cache | ipconfig /flushdns | No |
| Release + renew IP | ipconfig /release then ipconfig /renew | No |
| Reset Winsock | netsh winsock reset | Yes |
| Reset TCP/IP stack | netsh int ip reset | Yes |
| Clear DNS (PowerShell) | Clear-DnsClientCache | No |
ipconfig /flushdns clears cached DNS records. Use it when a site moved servers or a domain resolves to the wrong (old) address.ipconfig /release + /renew drops the current DHCP lease and asks the router for a fresh IP — the fix for an APIPA 169.254.x.x address or an IP conflict.netsh winsock reset rebuilds the Winsock catalog, the layer Windows apps use to talk to the network. This clears out broken LSPs left behind by VPNs, proxies, or malware.netsh int ip reset rewrites the TCP/IP stack settings to default, fixing corrupted protocol configuration.netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdnsRun these from an elevated (Administrator) prompt, then reboot — the Winsock and TCP/IP resets only take full effect after a restart. This sequence is the standard last-resort fix when smaller steps do not work.
From an elevated Command Prompt, run netsh winsock reset, then netsh int ip reset, then ipconfig /release, /renew, and /flushdns, and finally reboot. The reboot is required because the Winsock and TCP/IP resets only complete after a restart.
It rebuilds the Winsock catalog, the component Windows applications use to access network services. This removes broken layered service providers left behind by VPNs, proxies, or malware, which often restores connectivity. A reboot is required to finish the reset.
ipconfig /flushdns only clears cached DNS lookups and needs no reboot, fixing cases where a domain resolves to an old address. A full reset rebuilds Winsock and the TCP/IP stack and requires Administrator rights and a reboot, so try the DNS flush first.
A 169.254.x.x address means the PC could not reach a DHCP server and assigned itself an APIPA address. Run ipconfig /release followed by ipconfig /renew to request a fresh lease from the router. If that fails, check the cable, Wi-Fi, and the router DHCP service.