The error “Windows could not find a driver for your network adapter” does not always mean the driver simply needs an update. Windows may see the Wi-Fi or Ethernet controller without a usable driver, identify it only as an unknown device, or fail to detect the network hardware at all.
The fastest fix depends on what Device Manager shows.
Check Device Manager Before Downloading Anything
Right-click Start > Device Manager.
Look under both:
- Network adapters
- Other devices
Then match what you see to the next step.
| Device Manager result | What to do |
|---|---|
| Network adapter appears normally | Driver exists; troubleshoot the connection rather than searching for a missing driver |
| Adapter has a down arrow | Right-click it and choose Enable device |
| Adapter has a yellow warning icon | Open Properties > Device status and record the error code |
| Network Controller/Ethernet Controller appears under Other devices | Identify it and install the correct driver |
| No physical network controller appears anywhere | Scan for hardware, check chipset drivers, BIOS/UEFI and hardware |
Ignore WAN Miniport entries when looking for the physical Wi-Fi or Ethernet controller.
Select View > Show hidden devices, then Action > Scan for hardware changes. A faded adapter is not proof that the hardware is currently detected.
If You See Network Controller or Ethernet Controller
This is one of the clearest missing-driver cases.
Right-click the unidentified device and choose:
Properties > Details > Hardware Ids
The first entry may begin with something similar to:
PCI\VEN_...
or
USB\VID_...
The hardware ID lets you distinguish between network controllers when a laptop model was sold with different Intel, Realtek, Qualcomm, MediaTek, Broadcom, or other adapters.
Do not paste the ID into a random “driver download” site and install whatever it offers. Use it to determine which package on the PC, motherboard, or network-adapter manufacturer’s official support page matches the hardware.
Find the Exact PC or Motherboard Model
For a laptop or prebuilt desktop, start with the computer manufacturer’s support page.
Press Windows + R, enter:
msinfo32
and press Enter.
Record the System Manufacturer and System Model.
For a custom desktop with onboard networking, identify the motherboard model. If you installed a separate PCIe or USB network adapter, identify that adapter instead.
This matters because one laptop family can ship with several different wireless cards. Downloading a WLAN package for the right laptop name but the wrong network controller can still produce a “compatible hardware not found” error.
Get the Driver When the PC Has No Internet
A missing network driver creates a circular problem: the computer needs internet to obtain the driver but needs the driver to get online.
Use whichever temporary method is available:
- Connect through Ethernet if only Wi-Fi is missing.
- Use phone USB tethering when supported.
- Download the driver on another computer and copy it to a USB drive.
- Use a compatible USB network adapter temporarily.
If you rely on an iPhone and its hotspot is unavailable, see Personal Hotspot Not Working on iPhone.
Once temporary internet works, Windows Update becomes worth checking before manually installing anything.
Check Windows Update and Optional Driver Updates
On Windows 11, open:
Settings > Windows Update > Check for updates
After installing available updates, check:
Settings > Windows Update > Advanced options > Optional updates
Look under Driver updates for a relevant Wi-Fi, WLAN, Ethernet, LAN, network, or chipset package.
Microsoft says Windows Update normally supplies recommended hardware drivers, while optional driver updates may require manual selection.
Do not install every optional driver merely because it is available. Choose packages that correspond to the hardware you are troubleshooting.
If Windows Update does not provide a suitable driver, use the manufacturer’s package.
Download the Correct Network Driver
On the official support page for the PC or motherboard, look for categories such as:
- Network
- LAN
- Ethernet
- Wireless LAN/WLAN
- Wi-Fi
- Chipset
Verify:
- Exact computer or motherboard model
- Network-adapter vendor
- Windows version
- x64 or ARM64 architecture where applicable
- Wi-Fi versus Ethernet
- Hardware revision where listed
For a laptop or prebuilt PC, I would normally try the OEM package before a generic chip-vendor driver because the system manufacturer may include model-specific components or configuration.
Do not use “universal driver” utilities that scan the PC and demand a download or payment.
Install Chipset Drivers When Several Devices Are Unknown
A clean Windows installation can be missing more than the network driver.
If Device Manager contains several unknown PCI devices, install the official chipset/platform drivers for the exact system first. Supporting system components can be necessary before Windows identifies integrated hardware correctly.
Restart when requested, then return to Device Manager.
You do not need to reinstall every driver on the computer just because Wi-Fi is missing.
Install an EXE or MSI Driver
When the manufacturer supplies an .exe or .msi package:
- Copy it to the affected computer.
- Run the installer.
- Follow the manufacturer’s prompts.
- Restart Windows.
- Recheck Device Manager.
If the installer says no compatible hardware is present, stop and verify the hardware ID, adapter vendor, Windows architecture, and exact PC model.
Trying several unrelated packages until one installs is not a reliable driver strategy.
Install an INF Driver Manually
Some manufacturers provide an extracted driver folder or ZIP archive rather than a normal installer.
Extract a ZIP first. Then:
- Open Device Manager.
- Right-click the unidentified network controller.
- Choose Update driver.
- Select Browse my computer for drivers.
- Browse to the extracted driver folder.
- Leave Include subfolders selected.
- Click Next.
- Restart after installation.
If Windows still cannot find a driver in that folder, the package may not contain an INF that supports the device’s hardware ID.
Do not force an unrelated INF through Have Disk simply because it has the same Intel, Realtek, or Qualcomm branding.
What the Device Manager Error Code Tells You
When the adapter has a yellow warning symbol, open Properties and read Device status.
Some useful distinctions are:
- Code 1: Windows says the device is not configured correctly. The driver may be missing or incorrectly configured.
- Code 18: Windows recommends reinstalling the driver.
- Code 28: Drivers are not installed for the device.
- Code 10: The device cannot start. A driver, firmware, or hardware issue may be involved.
- Code 31: Windows cannot load the drivers required for the device.
- Code 43: Windows stopped the device because it reported a problem.
- Code 45: The device is not currently connected.
A Code 28 controller needs a matching driver. A Code 45 device that is physically absent will not be repaired by downloading five different driver packages.
Reinstall a Driver That Already Exists
This is appropriate when the network adapter appears under Network adapters but its driver became corrupted or stopped working after an update.
Before uninstalling anything, download the replacement driver when possible. Microsoft specifically recommends having a backup driver available when the PC cannot get online.
Then:
- Open Device Manager > Network adapters.
- Right-click the affected adapter.
- Select Uninstall device.
- Restart Windows.
Windows may reinstall a driver from its local driver store. If it does not, install the official package you saved.
When Windows offers to remove the driver package as well, be cautious on a computer with no alternative internet connection. Removing the only local copy can leave you with nothing to reinstall after restart.
If the problem started after a driver update
Open:
Device Manager > Network adapter > Properties > Driver
Use Roll Back Driver when the option is available.
If it is greyed out, Windows does not have a previous package available for rollback.
Network Reset Is Not a Missing-Driver Fix
On Windows 11, Network reset is under:
Settings > Network & internet > Advanced network settings > Network reset
Microsoft describes Network reset as a late troubleshooting step that removes installed network adapters/settings and reinstalls adapters after restart.
That can help when Windows already has a valid adapter and driver but networking is misconfigured.
It cannot manufacture a compatible driver package for an unknown controller. If Device Manager shows Code 28, fix the driver first.
Network reset can also require you to reconnect Wi-Fi networks or reconfigure VPN/network software afterward.
Wi-Fi Adapter Is Completely Missing
When there is no Wi-Fi controller under Network adapters or Other devices:
- Select View > Show hidden devices.
- Run Action > Scan for hardware changes.
- Install the correct chipset/platform drivers.
- Restart and check Device Manager again.
- Check whether wireless networking is disabled in BIOS/UEFI.
- Check the laptop’s wireless function key or physical switch if it has one.
If Ethernet works, use it to download the exact WLAN driver.
Wi-Fi and Bluetooth can be provided by the same physical card but still require separate Windows drivers, so working Bluetooth does not prove the Wi-Fi driver is installed correctly.
Ethernet Adapter Is Missing
For onboard Ethernet, install the LAN/Ethernet package from the PC or motherboard support page.
If you are using a dock or USB Ethernet adapter, the missing component may instead be a dock, USB, Thunderbolt, or adapter driver.
A bad Ethernet cable can stop the connection from working, but it normally does not make the physical Ethernet controller disappear from Device Manager.
Microsoft’s Ethernet troubleshooting guidance also recommends obtaining the manufacturer’s driver on another computer and transferring it by USB when the affected PC cannot get online.
Check BIOS or UEFI When Windows Cannot Detect the Hardware
Integrated LAN or WLAN can be disabled in firmware.
Enter the computer’s BIOS/UEFI using the manufacturer’s documented method and look for settings such as:
- Integrated NIC
- Onboard LAN
- Wireless LAN
- WLAN Device
- Internal Network Adapter
Make sure the required controller is enabled.
Do not change unrelated storage, Secure Boot, CPU, voltage, or boot settings while looking for the network option.
If the adapter remains absent from Device Manager and manufacturer diagnostics cannot detect it either, the problem is moving away from Windows drivers and toward firmware or hardware.
When Hardware Becomes the Stronger Suspect
Driver troubleshooting has reached its limit when:
- The correct official driver repeatedly reports that compatible hardware is absent.
- The adapter repeatedly disappears from Device Manager.
- The device still reports Code 10 or 43 after a correct driver reinstall.
- The controller is enabled in BIOS but cannot be detected.
- Networking failed after liquid exposure, impact, or an internal repair.
- A desktop PCIe network card is not detected in a known-good slot.
On a desktop, a technically experienced user can power the PC down and verify that an add-in network card is seated correctly.
For a laptop, internal wireless cards and antenna leads are easier to damage. Use the manufacturer’s service documentation or professional repair when physical inspection is required.
The important boundary is whether Windows can enumerate the network hardware. When it appears as Network Controller or Code 28, identify it and install the matching driver. When a valid adapter and driver already exist, troubleshoot Windows networking. When the hardware does not appear at all after chipset, firmware, and detection checks, repeated driver downloads are unlikely to solve the problem.
