Full Diagnostic Tree & Step-by-Step Overview
Your network adapter (Wi-Fi or Ethernet) is not working, likely following an OS update or driver change. How is the failure presenting in your operating system?
- The Network Adapter is visible in Device Manager, but shows a yellow warning triangle (Code 10, Code 43, Code 28, Code 31)
- The Network Adapter has completely DISAPPEARED from Device Manager / Network Connections (Missing Hardware)
- The adapter shows as enabled and 'Working Properly', but cannot obtain an IP or drops continuously after a few minutes
- You are on macOS, and your Wi-Fi or USB-to-Ethernet adapter stopped responding after a macOS update
Let's inspect the driver status. Open Device Manager (`Win + X` > *Device Manager*), expand 'Network adapters', right-click your Wi-Fi/Ethernet controller, select **Properties**, and click the **Driver** tab. Is the 'Roll Back Driver' button available?
- YES — The 'Roll Back Driver' button is active and clickable
- NO — The 'Roll Back Driver' button is GREYED OUT or unclickable
Native Rollback Available: Reverting to Previously Stored Working Driver Package
Solution:
Diagnostic Cause
A recent Windows Update or automated driver utility installed an incompatible or buggy Network Interface Controller (NIC) driver payload, causing hardware startup failures or protocol stack collisions.
Step-by-Step Fix
1. Trigger Rollback:
In Device Manager, right-click your network card > Properties > Driver tab.Click Roll Back Driver.When prompted with *'Why are you rolling back?'*, select 'My apps don't work with this driver' or 'Previous version of the driver was more reliable' > Click Yes.2. Verify Hardware Initialization:
Your screen/network stack will pause for 5–10 seconds.Verify that the Device Status box changes to *'This device is working properly.'*3. Prevent Automatic Driver Overwrites:
Press Win + R, type sysdm.cpl, press Enter > Go to Hardware tab > Device Installation Settings.Select No (your device might not work as expected) to prevent Windows Update from instantly re-installing the broken driver.
Rollback Button Greyed Out: Accessing Cached Windows Driver Repository
Solution:
Diagnostic Cause
When the primary rollback flag is clear (often after a feature update or clean installation), the Windows Driver Store (System32\DriverStore\FileRepository) still retains older INF driver packages that can be manually forced onto the adapter.
Step-by-Step Fix
1. Browse Local Driver Store:
In Device Manager, right-click the network adapter > Update driver.Select Browse my computer for drivers.Select Let me pick from a list of available drivers on my computer.2. Inject Older Driver Target:
Ensure Show compatible hardware is checked.You will see a list of historical driver versions (e.g., Realtek/Intel drivers with different dates/version numbers).Select the previous build date (avoid the newest top entry) and click Next.3. Verify and Lock:
Windows will install the selected driver binary. If successful, your network adapter will re-initialize immediately.
PCIe Bus Lockup / Deep Sleep State Preventing Hardware Enumeration
Solution:
Diagnostic Cause
Modern Wi-Fi 6/7 cards (Intel AX210/AX211/Killer) and 2.5G Realtek Ethernet chips can enter an unrecoverable D3 Cold power state after aggressive OS sleep cycles or failed driver updates, rendering them invisible to the PCIe bus.
Step-by-Step Fix
1. Execute Motherboard / PCIe Power Flush:
Shutdown the computer completely.Unplug the power cable from the PSU (or disconnect laptop battery/hold power button if internal).Press and hold the computer Power Button for 30 full seconds to bleed residual motherboard capacitor voltage.Reconnect power and boot into Windows.2. Unhide Hidden Devices in Device Manager:
Open Device Manager > Click View top menu > Select Show hidden devices.Expand Network adapters. If your card appears faded, right-click it and select Uninstall device.Check the box for 'Attempt to remove the driver for this device' > Click Uninstall.3. Install Offline OEM Driver Package:
On a working phone or secondary device, download the official motherboard/laptop manufacturer network driver installer (.exe or .inf).Transfer via USB drive to the affected PC, run installer, and restart.
Corrupted Driver Network Binding / Invalid Winsock Catalog State
Solution:
Diagnostic Cause
The physical network driver is loaded, but its virtual binding layers (NDIS intermediate drivers, VPN filters, or TCP/IP protocol stacks) are corrupted, preventing socket creation or DHCP negotiation.
Step-by-Step Fix
1. Run Elevated Terminal Command Sequence:
Press Win + X > Select Terminal (Admin) or Command Prompt (Admin).2. Execute Stack Purge Commands:
Reset Winsock catalog: netsh winsock resetReset IPv4 stack: netsh int ip resetRelease/Renew lease: ipconfig /release followed by ipconfig /renewFlush DNS cache: ipconfig /flushdns3. Perform Windows Network Reset:
Open Settings > Network & internet > Advanced network settings.Click Network reset > Reset now.This will clean-remove all network adapter drivers and re-install default system binaries upon automatic reboot.
Corrupted macOS SystemConfiguration Network Preferences or Driver Kernel Extensions
Solution:
Diagnostic Cause
Major macOS updates (e.g., Sequoia, Sonoma) can corrupt system preference files managing network interfaces (NetworkInterfaces.plist), leaving Wi-Fi or Thunderbolt Ethernet adapters unable to initialize hardware sockets.
Step-by-Step Fix
1. Delete Corrupted Preference Files:
Open Finder > Click Go in top bar > Go to Folder...Paste path: /Library/Preferences/SystemConfiguration/Locate and move the following files to your Trash:com.apple.airport.preferences.plistcom.apple.network.identification.plistNetworkInterfaces.plistpreferences.plist2. Rebuild System Interfaces:
Reboot your Mac. macOS will automatically detect all physical hardware adapters and generate fresh, uncorrupted configuration plists.3. Re-add Interface in System Settings:
Go to System Settings > Network.If your adapter is missing, click the three dots icon bottom right > Add Service > Select your hardware interface (e.g., *Wi-Fi* or *USB 10/100/1000 LAN*) > Click Create.