Fix Windows 10 Pro network adapter missing in Device Manager
A missing network adapter can make a Windows 10 Pro computer look offline even when the broadband service is working. In Melbourne and Sydney, premises often connect to the NBN through fibre-to-the-premises or hybrid fibre coax, while regional and rural areas may rely on copper, fixed wireless or satellite. The connection in the building is only half the story: Windows still needs a functioning Wi-Fi or Ethernet adapter to communicate with the ISP’s router.
Device Manager’s empty Network adapters category usually points to one of three layers: the hardware is absent, Windows has hidden or damaged the device entry, or a faulty driver and network stack are preventing normal detection. Start with reversible checks because reinstalling Windows or replacing the PC should be the last steps. The quickest path is to reveal hidden devices, test the physical connection, restore the correct driver and then reset damaged networking components.
Understand what the missing entry means
The first distinction is between one missing adapter and every adapter. A desktop may have separate entries for Ethernet, Wi-Fi and virtual VPN or Hyper-V connections, while a laptop may also list Bluetooth under a separate class. If Ethernet still works but Wi-Fi has vanished, focus on that device and its driver. If all physical adapters are absent, the cause is more likely to involve the operating system, firmware or a shared driver problem.
A hidden device can still be installed in Windows even though Device Manager does not show it in the normal view. This commonly happens after an upgrade, a failed driver uninstall or replacement of a USB network dongle. A pale or greyed-out icon under Network adapters is therefore more useful evidence than an empty category. Removing the stale entry can clear a damaged driver state without touching the working connection supplied by Telstra, Optus or another NBN provider.
The language used at home often blurs these faults: people say the NBN is down when the local Wi-Fi has failed. Before blaming the line, open a browser on another device and check whether the ISP gateway has power and signal lights. That separates a service outage from the Windows 10 Pro network adapter missing in Device Manager and saves a pointless visit to the router’s settings.
Reveal hidden devices and test the hardware
In Device Manager, choose View, Show hidden devices, then expand Network adapters. Look for a Wi-Fi, Ethernet, USB Wireless, Remote NDIS or vendor-named entry. Right-click a ghost adapter and select Uninstall device, marking the option to delete its software if Windows offers it. After that, select Action, Scan for hardware changes. Windows should either rediscover the hardware or create a device with a warning symbol.
Next, check the physical controls. Turn off Airplane Mode, enable Wi-Fi in the quick-settings panel and look for a Wi-Fi key on the keyboard. On many laptops, the network function shares the Fn key and may need to be pressed after another function key. Reconnect the Ethernet lead, try another known-good cable, and for a USB adapter move it to another port while avoiding unpowered hubs.
If the adapter is missing even before Windows loads, the problem lies deeper. Restart, enter the laptop’s UEFI or firmware setup and inspect the hardware list; Dell, HP, Lenovo and ASUS machines commonly place network hardware under integrated devices or advanced options. If it is disabled there, enable it and save. If it is not listed at all, the adapter, its firmware or the mainboard may require repair, and Windows drivers cannot fix that.
Restore the correct network driver
Before downloading anything, record the computer’s exact model and the adapter’s hardware IDs from Device Manager’s Properties, Details and Hardware Ids tabs. Search the manufacturer’s Australian support site for that model and its wireless or Ethernet driver, including a more recent chipset or firmware release when advised. These OEM packages are safer than files from general driver-download sites because they match the device’s hardware ID and approved firmware.
Install the vendor package while the faulty adapter is disconnected, then reconnect it or restart. If a Realtek, Intel, Killer or Broadcom entry reappears under Other devices, right-click it and choose Update driver, then Browse my computer and point Windows at the extracted driver folder. Avoid Device Manager’s online search unless the hardware ID confirms that the offered driver is a close match.
For additional checks beyond the manufacturer route, the network repair guidance provides a useful place to compare driver and connection symptoms. A device that returns after a cold boot but disappears again may also be affected by fast startup, sleep or resume behaviour, so note exactly when the entry vanishes.
Reset the Windows network stack
Open Windows Terminal or Command Prompt as administrator. Run the following commands individually and restart when prompted:
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
ipconfig /release
ipconfig /renew
These commands rebuild the Winsock catalogue, renew IPv4 settings and clear cached name records. Use ipconfig /renew on a DHCP connection; a business PC with a static address should keep its configured values. After the restart, open Network Connections with ncpa.cpl, confirm that the required adapter is present and then test the gateway, a public site and the local NBN services the household relies on.
If the adapter is still absent, use Settings, Network & internet, Status and the Network reset option. Reset removes and reinstalls Windows network adapters, clears the stack and requires a restart. Expect virtual VPN adapters, Hyper-V switches, third-party security filters and some Ethernet or USB-printing configurations to disappear temporarily; reinstall their software or recreate their settings only after the physical adapter is working again.
Repair update and system file problems
Driver faults can leave Windows Update unable to replace a missing device. Open an elevated terminal and run DISM /Online /Cleanup-Image /RestoreHealth, followed by sfc /scannow after DISM completes. Restart and repeat the hardware scan. These repairs restore component files and protected system files, but they do not replace firmware, so an adapter absent in UEFI still needs hardware attention.
Next, check Windows Update for optional driver updates and run its built-in troubleshooter if the scan fails. For installation-media and update steps that fit the wider Windows 10 Pro workflow, the Windows 10 help guides can help you prepare the correct tools and avoid mixing files from different builds. Do not install an Ethernet driver for a Wi-Fi device merely because both appear under Network adapters.
Third-party VPN clients, antivirus suites and packet-filter utilities can block driver installation. Temporarily uninstall those products, reboot and try the scan again. If you have edited the driver store or replaced an OEM utility, restore the original configuration before troubleshooting further. Repeated failed scans, event-log errors about the adapter’s hardware ID or a yellow exclamation mark are stronger reasons to seek device-specific support.
Deal with persistent hardware and software faults
When Windows cannot see the adapter in UEFI, test the hardware directly. For a USB Wi-Fi dongle, try another dongle or computer; for built-in Ethernet, inspect the cable, socket and power-saving settings. For a laptop, fully shut down rather than using sleep, disable Fast Startup temporarily and remove the battery if the model permits it. A working USB adapter can restore urgent access, but it does not repair a failed internal card.
Contacting Telstra or Optus can still be sensible for the broadband side of the problem. Ask the provider to check the NBN gateway, sync status and line or fixed-wireless service, especially if several devices lose access together. Their technician can refresh the connection, but it cannot restore an adapter that Windows has omitted; keep the two troubleshooting paths separate to avoid replacing software that is not the fault.
Windows 10’s standard support ended on 14 October 2025, so check whether the PC has Windows 10 extended security updates or can move to a supported release, and confirm that the manufacturer still supplies Windows 11 drivers for its hardware. Before any clean reinstall, back up files, record application licences and save the BitLocker recovery key. Reinstalling Windows should follow the hardware, driver and reset checks, not precede them.
Follow a dependable recovery checklist
Use this sequence when you need a repeatable recovery path rather than a collection of disconnected fixes:
- Write down the laptop or desktop model, Windows build and every adapter name previously shown in Device Manager.
- Reveal hidden devices and remove only confirmed ghost entries before scanning for hardware changes.
- Test Airplane Mode, Wi-Fi keys, Ethernet cables and a different USB port or adapter.
- Install the exact OEM wireless, Ethernet, chipset and firmware drivers for the machine.
- Reset Winsock and IP settings, then run DISM and SFC as administrator.
- Update Windows and any virtual network drivers, rebooting between each major change.
- Record what appears after every reboot and collect hardware IDs if support is needed.
Complete one stage before moving to the next, and restart after uninstalling a network driver or resetting the stack. If the adapter returns but the connection still fails, move on to gateway, DHCP, DNS and ISP testing. If it never returns, focus on UEFI, firmware, power management or replacement hardware.
Open Device Manager now and check the Network adapters category before changing anything else. Work through the recovery sequence, keep a small note of each result and leave the device powered on through driver installations and Windows Update. If the adapter reappears, verify the NBN gateway, then test the internet and any VPN needed for work.
For a PC that remains offline, gather the model number, Windows build, hardware IDs and the point where detection failed before contacting the manufacturer or ISP. Make that evidence the starting point for the next support request.