Windows Network Reset Commands: Fix Your Connection

Last Updated on: June 22, 2026

TL;DR — Key Takeaways

The core Windows network reset commands are ipconfig, netsh winsock reset, and netsh int ip reset.
Run them in order, least to most invasive, and recheck your connection after each step.
Start with ipconfig /flushdns and ipconfig /renew. They are safe and fix most everyday faults.
Step up to netsh winsock reset and netsh int ip reset only if that fails, then restart.
The Network reset button is the last resort. It reinstalls every adapter and forgets saved Wi-Fi networks.
Always run these in an administrator Command Prompt, or they fail without warning.

When your connection breaks, the right Windows network reset commands fix it faster than any reboot loop. The trick is knowing which command does what, and running them in the right order.

Most people paste a random command from a forum and hope. That often skips the easy fix or jumps straight to the most drastic one. There is a smarter sequence.

This is a clean reference to the commands that actually repair Windows networking. It covers what each one does, the order to run them, the PowerShell versions, and the mistakes to avoid.

Windows network reset commands: the order to run them

Run the commands from least to most invasive. Start with ipconfig to flush DNS and renew your address. Step up to netsh winsock reset and netsh int ip reset only if that fails. Save the full Network reset button for last.

Order matters because each step is more disruptive than the last. A DNS flush costs you nothing. A full Network reset wipes your saved Wi-Fi. Working upward means you stop at the smallest fix that works.

Recheck your connection after each step. If a page loads, you are done, and you skip the heavier commands entirely. The sections below follow this exact order.

ipconfig: the everyday network commands

The ipconfig command is your first stop. Its switches view your settings, clear the DNS cache, and force a new IP address from the router. These are safe to run any time, and they fix a large share of everyday connection faults.

Open the Start menu, type cmd, right-click Command Prompt, and choose Run as administrator. The most useful switches are below.

Command	What it does
`ipconfig /all`	Shows your full config, including DNS servers, MAC, and lease.
`ipconfig /flushdns`	Clears the DNS resolver cache of stale name records.
`ipconfig /release`	Drops the current IP address lease.
`ipconfig /renew`	Requests a fresh IP address from the router.
`ipconfig /registerdns`	Re-registers the device with the DNS server.

The common repair sequence is three commands in a row. This clears the cache, drops the old address, and pulls a new one.

ipconfig /flushdns
ipconfig /release
ipconfig /renew

An address that starts with 169.254 means the renew failed and DHCP never answered. Our guide on the 169.254.x.x APIPA address covers that case in full.

netsh winsock reset: rebuild the Winsock catalog

netsh winsock reset rebuilds the Winsock catalog, the layer that lets apps reach the network. Malware, old VPN clients, and broken updates corrupt it. Resetting clears the damage and restores a clean state. Restart the computer afterward for the change to apply.

Winsock is the interface between Windows programs and the network stack. When it is damaged, browsers and apps lose internet even though the connection looks fine. This command is the standard fix.

netsh winsock reset

You will see a message that the catalog was reset. Restart the computer before testing, or the change will not fully take hold.

netsh int ip reset: rebuild the TCP/IP stack

netsh int ip reset rewrites the TCP/IP stack back to its defaults. Use it when an address renew and a Winsock reset both fail. It can clear manual static IP or DNS entries, so note those first. A restart is required after you run it.

This command resets the core protocol settings that carry your traffic. It is more invasive than a Winsock reset, so it sits later in the order.

netsh int ip reset

If you set a static IP or manual DNS, write those values down before running it. The reset returns those settings to automatic, and you may need to re-enter them.

Restart the network services

Some faults come from a stopped service, not a bad setting. Three services matter most: DNS Client, DHCP Client, and WLAN AutoConfig. Restarting them forces name resolution, address requests, and Wi-Fi to start fresh. You can do this from the Services console in seconds.

Press Win + R, type services.msc, and press Enter. Find each service below, right-click it, and choose Restart.

DNS Client: handles name resolution and the local DNS cache.
DHCP Client: requests and renews your IP address.
WLAN AutoConfig: manages wireless connections.

If a service will not start, that points to a deeper system fault. The network reset below usually clears it.

Network reset: the last-resort button

Network reset is the button that does everything at once. It removes and reinstalls every network adapter, then reverts all settings to defaults. It also forgets saved Wi-Fi networks and VPNs, so keep your passwords handy. Use it only when the targeted commands have failed.

This is the graphical version of the resets above, bundled into one action. Because it wipes saved networks, it belongs at the end of the order, not the start.

Open Settings → Network & internet → Advanced network settings → Network reset. Click Reset now and confirm. Windows reinstalls your adapters and restarts in about five minutes.

The PowerShell equivalents

PowerShell can do most of the same jobs with clearer command names. Clear-DnsClientCache flushes DNS, and Set-DnsClientServerAddress sets your resolver. Restart-NetAdapter cycles an adapter without a reboot. Winsock and stack resets still use netsh, which PowerShell runs without any problem.

If you prefer PowerShell, the cmdlets below cover the everyday tasks. Run PowerShell as administrator first.

Clear-DnsClientCache
Get-NetIPConfiguration
Restart-NetAdapter -Name "Wi-Fi"

To set a public DNS server, use Set-DnsClientServerAddress with your adapter name. PowerShell still calls netsh for the Winsock and TCP/IP resets, so keep those commands handy.

What not to do

A few habits cause more harm than help. Running resets without administrator rights fails quietly. Skipping the restart after a Winsock or stack reset leaves the job half done. Reaching for Network reset first wastes the saved Wi-Fi you did not need to lose.

Do not skip the admin prompt. Without it, the reset commands fail silently and nothing changes.
Do not forget the restart. Winsock and TCP/IP resets only apply after a reboot.
Do not start with Network reset. It forgets your saved Wi-Fi, so try the smaller commands first.
Do not trust registry-cleaner tools. The built-in commands are safer than third-party network fixers.

Related Tools & Resources

NetworkCheckr hosts the free tools that pair with these commands. After a flush or renew, confirm the result here instead of guessing. Use the tools below to check your IP and DNS. The guides fix the specific errors these commands address.

Frequently Asked Questions

Short answers to the questions people ask most about Windows network reset commands. Each one expands on a point above. They cover what each command does, the safe order, and when to use Network reset.

What is the command to reset network settings on Windows?

The quickest single fix is ipconfig /flushdns, run in an admin Command Prompt. For a deeper repair, run netsh winsock reset and netsh int ip reset, then restart. The most complete option is the Network reset button under Settings. It reinstalls every network adapter on the machine.

What does netsh winsock reset do?

It rebuilds the Winsock catalog, the component that lets Windows apps use the network. Malware, old VPN clients, and failed updates can corrupt it, which breaks connectivity. Resetting clears those bad entries and returns Winsock to a clean state. You must restart the computer for the reset to take effect.

In what order should I run network reset commands?

Work from least to most invasive. Start with ipconfig /flushdns and ipconfig /renew. If that fails, run netsh winsock reset and netsh int ip reset, then restart. Use the Network reset button only as a last step, because it forgets your saved Wi-Fi networks.

Does netsh int ip reset delete anything?

It does not delete your files or apps. It rewrites the TCP/IP stack settings in the registry back to their defaults. That can clear custom static IP or DNS entries you set manually, so note those first. You must restart the computer after running it.

What is the difference between flushdns and network reset?

Flushing DNS clears only the cache of recent name lookups, with the command ipconfig /flushdns. It is quick and safe. A Network reset is far broader. It removes and reinstalls every network adapter and reverts all networking to defaults, so try flushdns first.

How do I reset network settings without commands?

Open Settings, then Network and internet, then Advanced network settings, and choose Network reset. Click Reset now and confirm. Windows removes and reinstalls your adapters, then restarts in a few minutes. It is the GUI version of the command-line resets, and it forgets saved Wi-Fi networks.

References

Primary sources for the commands and settings above. These are the official Microsoft references for ipconfig, netsh, the PowerShell DNS cmdlets, and the Windows network reset feature. Each link points to first-party documentation.

Microsoft Learn — ipconfig Command Reference
Microsoft Learn — netsh Command Reference
Microsoft Learn — Clear-DnsClientCache (PowerShell)
Microsoft Support — Fix Wi-Fi Connection Issues in Windows