Before you wipe your whole system or order a new laptop, hear me out. In 15 years of fixing Windows machines remotely, I'd say a good 80% of network adapter troubleshooting jobs I see come down to a driver issue, a power setting nobody knew existed, or a corrupted networking stack that takes three commands to fix. Rarely is it the hardware. So let's start simple and work up from there.

TL;DR

Network adapter troubleshooting on Windows usually means restarting the adapter in Device Manager, updating or reinstalling the driver, turning off the power-saving setting that kills the adapter, or running a TCP/IP reset in Command Prompt. Hardware failure is the last thing to check, not the first.

⏱️ 13 min read ✅ 85% success rate 📅 Updated July 2026

Key Takeaways

Network adapter troubleshooting starts with the simplest fix: restart the PC and router before anything else.
The power management setting that lets Windows turn off your adapter is responsible for more intermittent drops than most people realise.
Driver corruption and TCP/IP stack issues are the two most common causes of adapters that vanish or refuse to connect.
Safe Mode with Networking is your best tool for separating hardware faults from software ones.
Avoid third-party driver updater tools. They cause more problems than they fix.

At a Glance

Difficulty: Easy to Advanced
Time Required: 5 to 45 mins
Success Rate: 85% of users fixed without hardware changes

What Actually Causes Network Adapter Problems on Windows?

Here's the thing: Windows networking is a stack of layers, and any one of them going wrong produces the same symptoms on screen. You see "No internet" or the adapter disappears from Device Manager, and you have no idea whether it's a driver, a setting, a dodgy update, or the card itself. That's why a structured approach matters. Jumping straight to reinstalling Windows (yes, people do this) when the real fix is a 30-second toggle in Device Manager is, honestly, a bit rubbish for everyone involved.

The five main culprits I see, in rough order of how often they show up:

Corrupted or outdated drivers. The adapter driver is the software that lets Windows talk to the physical hardware. When it goes wrong, the adapter can vanish entirely from Device Manager or show a yellow warning triangle. Windows updates sometimes overwrite a working driver with a generic one that doesn't behave the same way.
TCP/IP stack or Winsock corruption. This is the underlying networking protocol layer. When it gets corrupted (usually after a bad update or malware), you can be connected to Wi-Fi with full signal and still have zero internet. The adapter looks fine. The problem is deeper.
Power management settings. Windows has an option, enabled by default on most machines, that lets it turn off your network adapter to save power. On laptops especially, this causes the adapter to drop intermittently, particularly after the machine wakes from sleep. It's one of those settings that should probably never be on by default, but here we are.
Problematic Windows updates. Microsoft has shipped updates that broke network adapters on specific hardware. It happens. The fix is usually a follow-up patch, a driver update from the manufacturer, or in bad cases, rolling back the update.
Physical hardware failure. The actual NIC (network interface card) dying. Less common than the others, but it does happen, especially on older machines or after physical damage. This is the one you want to rule out last, not first.

For a broader look at how Windows networking components fit together, Microsoft's NDIS documentation is worth a skim if you want the technical detail. And if you're also dealing with slow speeds rather than a dropped connection, see our guide on fixing slow internet on Windows which covers some overlapping ground.

Network Adapter Troubleshooting: Quick Fixes First

Always start here. I know it feels too simple, but these genuinely fix the problem more often than you'd expect. The restart alone sorts maybe a third of the cases I see. Give these five minutes before you go anywhere near Command Prompt.

Restart Everything Easy

Restart your PC
Go to Start > Power > Restart. Not Shut Down and power back on. Restart. Windows does things during a proper restart that a shutdown and boot doesn't always replicate.
Power-cycle your router
Turn it off at the wall (or unplug it), wait a full 30 seconds, then turn it back on. Give it another 60 seconds to fully reconnect before testing.
Verify
Check the taskbar Wi-Fi or Ethernet icon. If the connection is back, you're done.

Connection restored? Brilliant. If it keeps happening, the power management fix in Tier 2 will stop it coming back.

Toggle the Adapter Off and On Easy

Open Device Manager
Right-click the Start button and choose Device Manager from the list.
Find your adapter
Expand the Network adapters section. You're looking for something like "Intel Wi-Fi 6 AX201" or "Realtek PCIe GbE Family Controller" depending on your machine. If there's a yellow triangle next to it, that confirms a driver or initialisation problem.
Disable, wait, enable
Right-click the adapter > Disable device. Wait 15 to 20 seconds. Right-click again > Enable device. Windows will reinitialise the adapter fresh.

The adapter should reconnect within 10 to 15 seconds of being re-enabled. If it does, move on to the power management fix below to stop this recurring.

Run the Network Troubleshooter Easy

Open Settings
Go to Settings > Network and Internet. On Windows 11, look for Advanced network settings near the bottom. On Windows 10, it's right on the Status page.
Run the troubleshooter
Click Network troubleshooter or Network Adapter troubleshooter and follow the on-screen steps. It won't fix everything, but it does catch common misconfigurations and sometimes resets the adapter automatically.

The built-in troubleshooter is hit and miss, but it takes 60 seconds and occasionally finds something useful. Worth doing before the more involved fixes.

Intermediate Network Adapter Troubleshooting Steps

If the quick fixes didn't sort it, this is where most problems actually get resolved. Driver issues and the power management setting between them account for a huge chunk of the cases I deal with. Don't skip the power management one even if it sounds minor. It's caused more "my Wi-Fi keeps dropping" calls than I can count.

Fix the Power Management Setting Easy

Open Device Manager and find your adapter
Right-click Start > Device Manager > expand Network adapters.
Open Properties
Right-click your adapter > Properties. Click the Power Management tab.
Uncheck the power-saving option
Uncheck "Allow the computer to turn off this device to save power". Click OK.
Test
Put the machine to sleep and wake it again. If the adapter was dropping after sleep, this will have fixed it.

This is the fix for intermittent drops, especially after the machine wakes from sleep. Takes 30 seconds and the success rate is very high for that specific symptom. If the drop-outs persist even after this, weak coverage is often the real culprit, and one of the best mesh Wi-Fi systems will fix it for good.

Update the Network Adapter Driver Medium

Check the current driver date
In Device Manager, right-click your adapter > Properties > Driver tab. Note the Driver Date. If it's more than a year old, an update is worth trying.
Try automatic update first
Right-click the adapter > Update driver > Search automatically for drivers. Windows will check its own catalogue. This works sometimes, but the Windows catalogue isn't always up to date.
Check Windows Update
Go to Settings > Windows Update > Check for updates. Optional updates sometimes include driver updates that don't appear in Device Manager. Look for an "Optional updates" or "Driver updates" section.

If Windows says the driver is up to date but the problem persists, that just means it's the latest version Windows knows about. The manufacturer's site may have something newer. See Solution 8 for manual driver download.

Uninstall and Reinstall the Driver Medium

Uninstall the adapter
In Device Manager, right-click your adapter > Uninstall device. If you see a checkbox that says "Attempt to remove the driver for this device", tick it. This removes the driver files too, not just the device entry.
Restart the PC
Windows will detect the adapter on boot and reinstall a fresh driver automatically. This takes a minute or two.
Verify
Once back on the desktop, check Device Manager. The adapter should be listed without any warning icons. Test the connection.

If you are on a desktop with only one network adapter and no Wi-Fi, make sure you have a USB network dongle available before uninstalling. You will be offline briefly during the reinstall process.

Network Reset from Settings Medium

Open Network Reset
Go to Settings > Network and Internet > Advanced network settings > Network reset. On Windows 10, it's Settings > Network and Internet > Status > Network reset at the bottom of the page.
Run the reset
Click Reset now and confirm. The PC will restart. This removes and reinstalls all network adapters and resets all networking components back to defaults.
Reconfigure after restart
You will need to reconnect to Wi-Fi networks and re-enter any VPN or proxy settings. Any saved Wi-Fi passwords are cleared.

Network Reset is more thorough than just reinstalling the driver. It resets Winsock, IP settings, and all adapter configurations in one go. Good option if you have tried the driver fixes and nothing has worked yet.

If you have gone through all of the above and the adapter is still misbehaving, it's time for the more involved fixes. These are the ones that sort the genuinely stubborn cases, including post-update breakage and deep networking stack corruption. And if you are also dealing with a VPN that stopped working after a Windows update, our VPN troubleshooting guide for Windows covers some of the same ground from a different angle.

Advanced Network Adapter Troubleshooting

Right. If you are here, the quick stuff didn't work. That's fine. These fixes are what I reach for when a machine comes to me with a properly broken networking stack or a driver that just won't behave regardless of what you throw at it. They take a bit more time but the success rate is still very good before you start thinking about hardware.

Microsoft's own support documentation on fixing Wi-Fi connection issues in Windows recommends the TCP/IP reset commands below as a core troubleshooting step. So this isn't some obscure trick. It's the official fix for a corrupted networking stack.

Reset TCP/IP, Winsock and DNS Advanced

Open an elevated Command Prompt
Press Windows + R, type cmd, then press Ctrl + Shift + Enter together. Click Yes on the UAC prompt. You need it running as administrator or the commands won't work.
Flush the DNS cache
Type ipconfig /flushdns and press Enter. You should see "Successfully flushed the DNS Resolver Cache".
Reset Winsock
Type netsh winsock reset and press Enter. This resets the Winsock catalogue, which controls how applications communicate with network services. You will see a message saying the reset completed successfully and to restart the computer.
Reset the IP stack (optional but recommended)
Type netsh int ip reset and press Enter. This resets the TCP/IP stack itself. It will log changes to a reset.log file.
Restart the PC
Do not skip this. The changes do not take effect until after a full restart.

This fixes the "connected but no internet" problem in a large proportion of cases where the adapter itself is fine but the networking stack underneath it has gone wrong.

Manual Driver Download from the Manufacturer Advanced

Identify your adapter
In Device Manager, right-click your adapter > Properties > Details tab. Set the dropdown to "Hardware IDs" to get the exact model. Or just note the name shown in Device Manager, like "Intel Wi-Fi 6E AX211".
Download the driver
Go to the manufacturer's support site. For Intel adapters, that's downloadcenter.intel.com. For Realtek, it's realtek.com. For laptop-specific drivers, your laptop manufacturer's support page (Dell, HP, Lenovo, etc.) often has a customised version that works better than the generic one.
Install manually
In Device Manager, right-click the adapter > Update driver > Browse my computer for drivers. Point it to the folder where you downloaded the driver. Follow the installer prompts.
Roll back if needed
If a recent update broke things, go to Properties > Driver tab > Roll Back Driver (if the button is available). This restores the previous driver version.

Do not use third-party driver updater tools for this. Tools like Driver Booster or similar frequently install wrong versions or bundle unwanted software. Go directly to the manufacturer's site every time.

Boot into Safe Mode to Diagnose Hardware vs Software Advanced

Boot into Safe Mode with Networking
Hold Shift and click Restart from Start > Power. Go to Troubleshoot > Advanced options > Startup Settings. Click Restart, then press 5 or F5 to select Enable Safe Mode with Networking.
Test the connection
In Safe Mode, Windows loads only essential drivers. If the adapter works here, the problem is caused by a third-party app, VPN, security tool, or a conflicting driver loaded at normal startup. If it still fails in Safe Mode, you are likely looking at a hardware fault.
Investigate if it works in Safe Mode
Boot back to normal mode and check recently installed software, especially VPNs, firewalls, or network monitoring tools. Uninstall anything added around the time the problem started.

This is the definitive test for hardware versus software. Took three reboots on one machine I worked on before the pattern became obvious. Patience pays off here.

If the adapter fails in Safe Mode and every software fix has been tried, you are into hardware territory. Check the physical port and cable first (swap to a different Ethernet port on the router, try a different cable). Run any OEM diagnostics your PC manufacturer provides. If nothing changes, a USB to Ethernet adapter or a USB Wi-Fi dongle is a cheap way to get back online while you decide whether to replace the internal NIC. For more on diagnosing hardware faults at home, HowToGeek's Wi-Fi troubleshooting breakdown covers the hardware diagnostic side well.

Preventing Network Adapter Problems Coming Back

Sorted the problem? Good. Here's how to stop it happening again, in order of what actually matters most.

First, disable that power management setting on every machine you use regularly. Go to Device Manager > your adapter > Properties > Power Management and uncheck the power-saving option. Do it now if you haven't already. It's the single most preventable cause of recurring adapter drops and it's on by default on most Windows installations.

Keep drivers updated, but do it properly. Check your adapter manufacturer's support site every few months, or set Windows Update to also install optional driver updates. Don't rely on third-party tools. They are consistently worse than going direct to the source, and I've seen them turn a minor driver issue into a complete networking failure more than once.

Create a restore point before any major update or driver change. Go to Control Panel > System > System Protection > Create. Takes two minutes and gives you a clean rollback path if something goes wrong. This is especially useful around major Windows feature updates, which have a history of touching networking components.

Limit how much network software you run at once. Two VPN clients, a corporate firewall, and a third-party DNS tool all fighting over the same adapter is a recipe for exactly the kind of intermittent failures that are a nightmare to diagnose. Keep it simple where you can.

And if you're on a desktop, use a quality Ethernet cable and don't bend it sharply near the port. Physical stress on the RJ45 connector is a slow killer for Ethernet ports, and by the time it causes problems you've usually forgotten about the time someone yanked the cable. See our Ethernet not working guide if you suspect a physical connection issue rather than the adapter itself.

Network Adapter Troubleshooting: Summary

Network adapter troubleshooting on Windows is almost always solvable without touching hardware. Start with the restart and the Device Manager toggle. Move to the power management setting and driver update if those don't work. If you're getting "connected but no internet", the TCP/IP reset commands are your best friend. And if nothing works in normal mode but Safe Mode is fine, you're looking for a software conflict rather than a dead card.

The key thing with network adapter troubleshooting is working through it in order rather than jumping to the nuclear options. A proper restart fixes more than it should. The power management setting fixes more than anyone expects. And the Winsock reset has saved more machines from unnecessary reinstalls than I can count. Work through the tiers, and you'll have this sorted.