Windows Network Adapter Error: Causes and Fixes

What Does a Network Adapter Error Mean in Windows

A network adapter error is a general term for problems where the Windows operating system cannot properly initialize, configure, or use a network device (built-in or external). Symptoms can vary: from complete lack of network connectivity (a network icon with an X or exclamation mark in the system tray) to a yellow triangle appearing in Device Manager with error codes such as Code 10 (device cannot start), Code 31 (driver cannot load required components), or Code 28 (driver not installed).

The error may appear immediately after system startup, after installing Windows updates, drivers, or new software, or following a power failure.

Common Causes

Causes of network adapter errors in Windows are typically divided into three categories: software (drivers, system), configuration, and hardware.

1. Outdated, corrupted, or conflicting drivers. The most frequent cause. A driver may have been damaged during installation, conflict with another device's driver, or become incompatible after a Windows update.
2. Damage to system network components. Critical Winsock files, dll libraries, or Windows services (e.g., WLAN AutoConfig, Network Connections) can be corrupted by viruses, incorrect utilities, or system crashes.
3. Incorrect network or power-saving settings. A power policy may disable the adapter to save battery charge (on laptops), and incorrect static IP/DNS settings can block access.
4. Hardware conflict. Two network adapters (e.g., built-in Wi-Fi and a USB adapter) may conflict for resources. Conflicts can also arise when installing virtual adapters (Docker, VPN clients).
5. Hardware failure. The network controller on the motherboard or the USB adapter itself may fail. A poor connection in a port, a faulty cable, or a problem with a router/switch port will also cause similar symptoms.
6. Insufficient permissions or security conflict. Running programs or services that require network access without administrator privileges. Aggressive antivirus or firewall software may block the driver.

Solutions

Troubleshooting should progress from simple and quick to complex. Start with a reboot, then diagnose in Device Manager, and only then move on to system resets and hardware checks.

Method 1: Diagnose and Reinstall the Driver via Device Manager

This is the primary and most effective action for most problems associated with an error code in Device Manager.

1. Press Win + X and select Device Manager.
2. Expand the Network adapters section.
3. Locate the problematic adapter. It will be marked with a yellow exclamation mark.
4. Right-click it and select Uninstall device.
5. IMPORTANT: In the window that appears, be sure to check the box "Delete the driver software for this device" if it is present. Click Uninstall.
6. In the Device Manager menu, select Action → Scan for hardware changes. Windows will attempt to find and install a basic driver. Often this is sufficient to restore basic network access.
7. If the basic driver does not install or functionality is limited (e.g., no Wi-Fi), download the latest driver from the official website of your laptop/motherboard manufacturer or the chipset maker itself (Intel, Realtek, AMD, Broadcom, Killer). Install the driver manually: in Device Manager → Action → Add legacy hardware → select the downloaded .inf file.

💡 Tip: Use a driver cleanup utility (e.g., Display Driver Uninstaller (DDU) for GPUs; for network drivers, alternatives like DriverStore Explorer exist) if standard uninstallation doesn't help.

Method 2: Reset the Network Stack and TCP/IP Configuration

This method resolves issues caused by incorrect protocol settings, Winsock catalog corruption, or conflicts after crashes.

1. Close all programs using the network.
2. Open Command Prompt (cmd) or PowerShell as an administrator (via the Start menu → Windows PowerShell → Run as administrator).
3. Sequentially enter the following commands, pressing Enter after each. After executing the netsh commands, you must restart your computer:

   netsh winsock reset
   netsh int ip reset
   ipconfig /release
   ipconfig /renew
   ipconfig /flushdns
   

4. Restart the PC. After booting, check for network connectivity.

Method 3: Restore System Files and Check Integrity

Use this if the problem is caused by corrupted Windows system files.

1. In the same administrative command prompt, run:

   sfc /scannow
   

   This command will scan and attempt to repair corrupted system files. The process may take 10–20 minutes.
2. After sfc completes, perform a deeper check using DISM:

   DISM /Online /Cleanup-Image /RestoreHealth
   

   This tool uses Windows Update components to restore the system image.
3. After successful completion, restart the computer and check the network again.

Method 4: Check in Safe Mode and Disable Conflicting Software

The goal is to determine if third-party software (VPN, antivirus, virtual adapters) is causing the problem.

1. Boot into Safe Mode with Networking. To do this: Settings → Update & Security → Recovery → Advanced startup → Restart now → after reboot, select Safe Mode with Networking.
2. If the network works in Safe Mode, the issue is with third-party software or a driver.
3. Boot back into normal mode. Temporarily disable or uninstall:
   • Non-built-in antivirus/antispyware software (not Windows Defender).
   • VPN clients and virtual network adapters (e.g., from VirtualBox, Docker, VMware).
   • Network optimization or "acceleration" programs.
4. After disabling each component, reboot and check if the network has returned.

Method 5: Check and Configure Power Settings (for Laptops)

Sometimes power-saving policies disable the adapter to conserve battery.

1. In Device Manager, find your network adapter, open its Properties.
2. Go to the Power Management tab.
3. Uncheck the box for "Allow the computer to turn off this device to save power".
4. Click OK and restart the laptop.

Method 6: Hardware Diagnostics and BIOS/UEFI Update

If all software methods fail, check the hardware.

1. For a built-in adapter: Enter BIOS/UEFI (Del/F2/F10 key during boot). Find the section related to integrated devices (Integrated Peripherals, Onboard Devices). Ensure the network controller (Onboard LAN, Integrated NIC) is Enabled.
2. For a USB adapter: Try a different USB port (preferably a USB 2.0/3.0 port directly on the motherboard, not through a hub). Test the adapter on another computer. If it also isn't recognized on another PC, the adapter is likely faulty.
3. BIOS/UEFI update: Sometimes new BIOS versions fix compatibility issues with controllers. Do this cautiously and only if you are confident in the process! Download the latest stable version from your motherboard/laptop manufacturer's website and follow their instructions.

Prevention

• Do not disable automatic driver updates via Windows Update. Often, stable and compatible versions are delivered this way.
• Create system restore points before installing major Windows updates, new drivers, or software that may affect the network (VPNs, antiviruses).
• Use drivers only from official websites. Avoid "universal" driver packs, which can damage the system.
• Regularly clean your system of temporary files and unused software, especially virtual adapters and old versions of network utilities.
• For laptops: In power settings, create a "High performance" plan and disable adapter shutdown in it, as described above.