The fastest way to fix a Windows PC that won’t stay online is to work from the smallest repair to the largest, and Windows’ built-in Network reset sits at the far end of that ladder. It removes every installed network adapter, reinstalls each one with default settings, and returns Winsock and TCP/IP to their original state after a restart.
To reset network settings in Windows 11, open Settings > Network & internet > Advanced network settings > Network reset > Reset now; in Windows 10, the same button lives under Settings > Network & Internet > Status. Both paths restart your PC and clear custom configuration, so VPN clients, proxy entries, static IPs, and saved Wi-Fi passwords need attention afterward.
That trade-off is why the order of operations counts. Many network connectivity issues come from a stale DNS cache, an expired DHCP lease, or one misbehaving driver, and each of those has a narrower fix that leaves the rest of your configuration alone. PacketTools builds its free diagnostics and network troubleshooting guidance around that same habit from production networks: confirm the fault, apply the smallest repair, then verify the result from outside the machine.
Use Windows Settings for a Full Reset
A full reset through Windows Settings takes about two minutes of clicking plus one restart, and it wipes adapter-level configuration on every interface at once. Record your custom settings first, then follow the path for your Windows version and plan for reconnection work after the reboot.
What Should You Save Before Proceeding?
Anything you configured by hand disappears, so capture it before you click Reset now. Open an elevated Command Prompt and run ipconfig /all > %USERPROFILE%Desktopnetconfig.txt to save a text snapshot of every adapter.
Check this list against your machine:
- Static IP details: address, subnet mask, default gateway, and custom DNS servers for each adapter.
- Saved Wi-Fi passwords: run
netsh wlan show profilesto list networks, and confirm you know the password for any you depend on. - VPN connections: server addresses, authentication method, and any installer or configuration file your VPN client needs.
- Proxy settings: proxy address, port, and any setup script URL from Settings > Network & internet > Proxy.
- Virtual switches: Hyper-V, WSL, or lab adapters you created yourself.
- Driver installer: a copy of your Wi-Fi and Ethernet driver from the PC maker’s site, saved locally.
If you troubleshoot on a corporate laptop, check with your IT team before resetting. A remote machine that loses its VPN loses its path back to management tools.
Windows 11: Find Network Reset Under Advanced Network Settings
To reset network settings in Windows 11, follow these steps:
- Press Windows + I to open Settings.
- Select Network & internet in the left pane.
- Scroll down and choose Advanced network settings.
- Under More settings, select Network reset.
- Read the description, then select Reset now.
- Confirm with Yes.
You can jump straight to step 4 by running start ms-settings:network-advancedsettings from Command Prompt or the Run dialog. Save open work before confirming, because Windows signs you out and restarts on its own after a short warning.
Windows 10: Find Network Reset Under Status
To reset network settings in Windows 10, the option sits on the Status page:
- Open Start > Settings.
- Select Network & Internet.
- Choose Status in the left pane.
- Scroll to the bottom and select Network reset.
- Select Reset now, then Yes.
Network reset arrived with the Windows 10 Anniversary Update (version 1607), so any supported Windows 10 build has it. If you can’t find the link, confirm you’re on the Status page; on smaller screens it sits below the Advanced network settings group.
What Changes After Windows Restarts?
Expect to come back to a PC with no active connection. Your network adapters have been removed and reinstalled, so Wi-Fi shows nearby networks and waits for you to pick one and enter its password again.
Here’s what to check in the first few minutes:
| Item | Status after reset | What you do |
|---|---|---|
| Wired Ethernet with DHCP | Reconnects on its own | Confirm you have an IP address |
| Saved Wi-Fi networks | Need reconnecting | Select the network, enter the password |
| Static IP or custom DNS | Reverted to automatic | Re-enter from your saved notes |
| VPN clients and virtual switches | Need reinstalling or reconfiguring | Run the installer or import the profile |
| Proxy settings | Cleared | Re-enter address and port |
| Network profile | May switch to Public | Set it back to Private on trusted networks |
Test plain connectivity before you reinstall VPN software. That way you know whether the reset itself fixed the fault or whether the VPN layer was the trigger.
Could a Less Disruptive Fix Restore Your Connection?
Yes, in most cases a targeted fix brings you back online without touching the rest of your configuration. Start by deciding whether the fault belongs to your PC at all, then let Windows diagnose itself, then restart just the adapter that’s failing.
Check Whether the Fault Affects One PC or Every Device
Grab your phone or a second laptop and connect it to the same network. If every device struggles, the problem sits upstream at the router, modem, or ISP, and resetting Windows changes nothing.
For an upstream fault, power-cycle the modem and router: unplug both, wait at least 30 seconds, plug the modem in first, and wait for its lights to settle before powering the router. You can also log in to your router’s IP address and check the WAN status page for an ISP connection.
If only your PC fails, narrow it further:
- One network only: forget it under Settings > Network & internet > Wi-Fi > Manage known networks, then reconnect.
- Every network fails: the problem lives in this Windows installation, so keep going down this guide.
- Connected icon, nothing loads: that pattern points at DNS or routing, covered in the guide to Wi-Fi connected but no internet.
- Wi-Fi keeps disconnecting: try the other band (2.4 GHz or 5 GHz) to rule out interference before blaming Windows.
Run the Windows Network Troubleshooter
The built-in troubleshooter catches ordinary misconfigurations, such as a disabled adapter or Airplane mode left on, in under a minute. On Windows 11, Microsoft puts it first: open the Get Help app, search for connect to network and internet, and run the Network and Internet diagnostics.
On Windows 10, right-click the network icon in the taskbar and choose Troubleshoot problems. Note anything the troubleshooter reports even if it says it couldn’t fix the issue; messages like “DNS server isn’t responding” tell you exactly which component to target next.
Restart One Wi-Fi or Ethernet Adapter Without Resetting Everything
Disabling and re-enabling a single adapter clears a stuck interface while leaving its configuration intact. In administrator PowerShell, run:
Get-NetAdapter
Restart-NetAdapter -Name "Wi-Fi"
Replace Wi-Fi with the name shown in the first command. Prefer the GUI? Press Windows + R, type ncpa.cpl, right-click the adapter in Network Connections, choose Disable, wait ten seconds, then choose Enable.
This step resets the network adapter’s link state only. Your static IP, DNS servers, and saved profiles all survive, which makes it the right move when connectivity drops after sleep or a dock change.
Repair Specific Network Components With Commands
Command-line repairs let you fix the exact layer that’s broken, whether that’s name resolution, the socket catalog, the IP stack, or address assignment. Microsoft’s own Wi-Fi guidance runs netsh winsock reset, netsh int ip reset, ipconfig /release, ipconfig /renew, and ipconfig /flushdns in that order, but you can also run each one alone when you know the symptom.
Open Search, type Command Prompt, choose Run as administrator, and approve the prompt before running any of the commands below.
Clear the Local DNS Cache With ipconfig /flushdns
Run ipconfig /flushdns when some sites load and others fail, or when a site moved servers and your PC still points at the old address. The command empties cached lookups, including cached failures, and leaves your configured DNS server addresses untouched.
PowerShell users can run Clear-DnsClientCache, which does the same job, so there’s no need to run both. A full walkthrough for every platform sits in the guide on how to flush your DNS cache.
Flushing takes effect instantly with no restart. If the same site fails right after a flush, the bad answer is coming from your DNS server itself.
Reset Winsock With netsh winsock reset
Run netsh winsock reset when apps report socket errors, or when connectivity broke after you uninstalled a VPN, firewall, or security suite. Those products install Layered Service Providers into the Winsock catalog, and a leftover entry can block every app from opening a connection.
The reset rebuilds the catalog to defaults. Restart Windows afterward; the change doesn’t apply until you do. Any security product that depended on its own LSP needs a reinstall or repair once you’re back online.
Restore TCP/IP Defaults With netsh int ip reset
Run netsh int ip reset when the IP stack itself looks damaged: adapters show odd addresses, routes go missing, or ipconfig reports settings you never configured. The command rewrites TCP/IP registry values to their defaults.
Two cautions from experience:
- It clears static IP assignments on affected interfaces, so have your saved
ipconfig /alloutput ready. - An “Access is denied” line for one registry key is common and harmless; check whether the rest of the output reports success.
Restart after this command too. If you plan to run both netsh resets, run them back to back and restart once.
Renew a DHCP Lease Only When Automatic Addressing Is Enabled
ipconfig /release followed by ipconfig /renew asks your router for a fresh address. It helps when your PC shows a 169.254.x.x address or holds a lease from a network you’ve left. If DHCP is new territory, the short version is that your router hands out addresses automatically, and these commands restart that exchange.
Skip these commands on an adapter with a static IP; they won’t help and can leave the interface without an address. To target one adapter, add its name: ipconfig /renew "Wi-Fi". For DHCPv6, use ipconfig /release6 and ipconfig /renew6.
Run release and renew from a local session. Releasing the address on a remote machine cuts off your own connection.
When Should You Repair the Network Adapter Driver?
Repair the driver when the adapter itself misbehaves: it disappears, shows an error, or failed right after a Windows or driver update. Device Manager tells you which case you’re in, and a saved offline installer keeps the repair from stranding you.
Check Device Manager for Adapter Errors
Press Windows + X and choose Device Manager, then expand Network adapters. Look for these signs:
- Yellow triangle: the driver loaded with an error. Double-click the adapter and read the Device status box for a code such as Code 10 or Code 43.
- Down arrow: the device is disabled. Right-click and choose Enable device.
- Adapter missing: select View > Show hidden devices, then Action > Scan for hardware changes.
- Unknown device under Other devices: Windows has no driver at all.
A clean entry with no warning points you back toward configuration fixes. An error code points at the network adapter driver.
Choose Between Updating, Rolling Back, and Reinstalling the Driver
Match the action to how the fault started:
| Situation | Action | Where |
|---|---|---|
| Fault began after a driver update | Roll back | Properties > Driver > Roll Back Driver |
| Old driver, intermittent drops | Update | Install the latest from the PC or chipset maker |
| Error code, corrupted install | Reinstall | Uninstall device, then restart |
To reinstall the network driver, right-click the adapter, choose Uninstall device, tick Attempt to remove the driver for this device, and restart. Microsoft notes that Windows automatically installs the driver again after the restart in most cases. For vendor-specific steps, the guide on how to update network drivers covers Intel, Realtek, and Qualcomm adapters.
Prefer the manufacturer’s driver over the generic Windows Update version for Wi-Fi cards; vendor builds carry roaming and power-management fixes the inbox driver lacks.
Keep an Offline Driver Installer Before Removing Anything
Download the correct driver before you uninstall anything, because a PC without a working adapter can’t fetch one. Note your PC maker and model number (run wmic csproduct get name or check the sticker underneath), then grab the Wi-Fi and Ethernet drivers from the maker’s support page.
Save the installers to the local drive and to a USB stick. If the current machine is already offline, download them on another computer. With that copy in hand, a failed automatic reinstall costs you five minutes instead of an afternoon.
Verify Recovery and Isolate Any Remaining Fault
Confirm recovery from the inside out: local addressing first, then the wider internet, then your custom configuration. If something still fails, the checks below give you the evidence to pinpoint where.
Confirm the Local IP Address, Gateway, and DNS Configuration
Run ipconfig /all and read the entry for your active adapter. A healthy DHCP client shows:
- An IPv4 address in your LAN range, such as 192.168.1.x (a 169.254.x.x address means DHCP failed).
- A default gateway, usually your router.
- One or more DNS servers.
- DHCP Enabled: Yes, unless you deliberately run a static IP address.
Then run ping against the gateway address. Replies with low single-digit millisecond times mean your PC reaches the router. If the gateway answers but websites don’t, test name resolution with nslookup packettools.com.
Use PacketTools to Check Public IP, DNS, and External Reachability
Local checks prove your PC reaches the router; browser-based tests prove traffic leaves your network correctly. PacketTools runs these checks in real time with no sign-in, and it doesn’t log or store your IP, queries, or test data.
Work through them in order:
- What Is My IP: confirms your public address and shows whether traffic exits through a VPN or your ISP.
- DNS Lookup: confirms domains resolve to the expected addresses. If they don’t, the steps to troubleshoot DNS issues pick up from there.
- Ping test: measures reachability and latency to a host.
- Traceroute: shows where packets stop. Learning how to trace a route helps you tell an ISP hop failure from a local one.
Restore Required VPN Settings and Review the Network Profile
Once basic connectivity tests clean, bring back the custom layers one at a time. Reinstall or reconfigure your VPN client, connect, and repeat the public IP check to confirm traffic routes through the tunnel.
Re-enter proxy settings under Settings > Network & internet > Proxy if your organization uses one. Then open your Wi-Fi or Ethernet properties and check the network profile: a reset can leave it on Public, which blocks file sharing and network discovery on your home or office LAN. Set trusted networks to Private.
If connectivity breaks the moment the VPN connects, the VPN layer is your fault source, and resetting Windows again won’t keep it fixed.
Escalate Persistent Failures With Useful Diagnostic Evidence
When nothing above holds, hand your ISP or IT team evidence they can act on. For Wi-Fi faults, run netsh wlan show wlanreport from an elevated prompt; it generates an HTML report of recent sessions and disconnect reasons.
Collect these before you escalate:
- Exact times of each failure.
- Adapter model, driver version, and driver date from Device Manager.
- Windows build and recent update history.
ipconfig /alloutput and traceroute results.- What you already tried, in order.
A reset that you have to repeat every few days points at something reintroducing the bad state, such as a driver, security agent, or policy, and that detail helps the next person most.
Choose the Smallest Fix That Restores Reliable Connectivity
Start with the repair that touches the least and move up only when it fails. Check whether other devices share the fault, run the troubleshooter, restart the single adapter, then use the targeted commands for DNS, Winsock, TCP/IP, or DHCP.
Move to the driver when Device Manager shows errors or the fault followed an update. Save the full option to reset network settings for cases where every adapter-level fix has failed or networking broke across multiple networks, and record your static IPs, VPN details, and driver installer before you press Reset now. After any fix, confirm your gateway, DNS, and public IP before restoring VPN and proxy settings one at a time.
Leave a Reply