When faced with a lack of internet, many users first turn to finding the driver for their Wi-Fi adapter so they can reinstall it. However, a paradoxical situation often arises: the network doesn't work precisely because the system can't correctly identify the device without the installed software. In this case, the computer simply doesn't see the network card or marks it as an unknown device, making a standard connection to the router impossible.
Solving this problem requires a systematic approach and an understanding of where the operating system stores hardware information. Even if the internet is down, Windows stores unique hardware identifiers in its logs and registry, which allow you to find the required software version on another device or via a mobile phone. The key is to decipher these codes correctly and avoid mixing up chipset versions, as installing the wrong driver can lead to complete module failure.
In this article, we'll cover all available methods: from standard Device Manager tools to advanced PowerShell commands. You'll learn how to identify the exact adapter model, even if it's listed as "Unknown Device," and find safe sources for downloading original files. This knowledge is critical for any PC technician or advanced user who wants to maintain control of their system.
Using Device Manager to find information
The most obvious and accessible way to obtain initial information is to use the built-in Windows tool called Device Manager. This system component aggregates data on all devices connected to the motherboard, including those that are not functioning correctly. To launch it, press a key combination. Win + R, enter the command devmgmt.msc and press Enter, or right-click on the Start menu and select the appropriate item from the list.
In the window that opens, we are interested in the section Network adaptersIf at least the basic driver is installed, you will see the name of your wireless card, for example, Intel Wireless-AC 9560 or Realtek RTL8822BEDouble-clicking the device will open a properties window, where the "Driver" tab displays the vendor, development date, and driver version. This information can often help you determine whether the installed version is up-to-date and whether it's a standard Microsoft stub.
However, the situation may be more complex: if the adapter's name is listed as "Unknown Device" with a yellow exclamation point, the standard description won't help. In this case, go to the "Details" tab. From the "Property" drop-down list, select Equipment ID (or Hardware ID). You will see lines like PCI\VEN_10EC&DEV_8822&SUBSYS..These are the codes VEN (Vendor ID) and DEV (Device ID) is a unique passport of your equipment.
⚠️ Attention! When copying the equipment ID, be careful not to copy the symbols
REVorSUBSYSIf you're searching for a driver by the device's base code, use this method. Often, older or newer chip revisions require different software versions, and specifying the full code can confuse your search.
Write down or copy the first line (the most complete one) and use it to search the internet. By combination VEN_XXXX&DEV_YYYY You can accurately identify the chipset manufacturer, even if the adapter itself is released under the laptop's brand. This is especially important for OEM versions of devices, where the names in the system may be hidden or changed by the computer manufacturer.
Analysis via the command line and PowerShell
For those who prefer a text-based interface or need more detailed technical information, the command line is a great tool. It allows you to download a structured report on network interfaces, which sometimes contains more data than the manager's graphical interface. To access this information, run the command prompt (CMD) or PowerShell as an administrator.
Enter the command netsh wlan show driversThis command will display a detailed report about the wireless network driver. In the list, you will find the lines "Vendor," "Date," "Version," and, most importantly, "INF file name." The INF file is the driver's installation file, and its name (for example, oem12.inf or netrtwlanx.inf) can tell you which package was used during installation. This is useful if you're trying to roll back a system or find the original installer by filename.
If the standard command doesn't produce results or the adapter isn't active, you can use a more powerful tool called PowerShell. Enter the command:
Get-PnpDevice | Where-Object {$_.Class -eq"Net"} | Select-Object FriendlyName, InstanceId, Status
This command will filter all devices of the "Network" class and display their friendly names and unique instance IDs. Status OK indicates normal operation, whereas Error or Unknown signal a problem. This approach allows for a quick scan of the system for resource conflicts or hardware initialization failures.
What to do if the commands don't work?
If your system is blocking PowerShell scripts, you may have a security policy enabled. Try running PowerShell as administrator and entering the command: Set-ExecutionPolicy -Scope CurrentUser Unrestricted. This will allow local scripts to run, but be aware of the risks of running untrusted code.
Identifying a device by physical marking and ID
In cases where software methods are ineffective (for example, the system won't boot or the device is completely dead), physical inspection is the only option. This is especially true for desktop PCs with PCI cards or laptops, where the Wi-Fi module is often implemented in a M.2 or Mini PCIeOnce you remove the laptop's case cover or back panel, you'll see a sticker on the module itself.
The sticker usually indicates the chipset manufacturer (Atheros, Broadcom, Intel, Qualcomm) and model. However, often it only contains a QR code or a short batch code. In this situation, the hardware ID method can help again, but you'll have to look for it on the laptop or motherboard manufacturer's website in the Support section. There, they list all the components ever used for your specific laptop model.
Therefore, blindly installing a driver from a website based on your laptop model may not work if your revision is different. Always check the hardware ID found in your system against the driver description on the website.
| Chip manufacturer | Typical VEN prefixes | Frequent series of devices | Driver Features |
|---|---|---|---|
| Intel | VEN_8086 | Wireless-AC, AX200, Centrino | Stable, frequently updated via the update center |
| Realtek | VEN_10EC | RTL88xx, RTL87xx | Requires manual installation, frequent version conflicts |
| Broadcom | VEN_14E4 | BCM43xx | Often require specific drivers for the OS |
| Qualcomm/Atheros | VEN_168C | AR9xx, QCA61xx | Popular in gaming laptops, sensitive to BIOS versions |
Using the table above allows you to quickly navigate the sea of technical specifications. Knowing the chip manufacturer narrows your driver search from thousands of options to a few official sources. This saves time and reduces the risk of system viruses when downloading software from untrusted sources.
Specialized utilities for identification
When built-in Windows tools aren't enough, third-party identification programs come to the rescue. They scan a database of known devices and match hardware IDs with model names. One of the simplest and most effective tools is the utility Unknown Device Identifier or online services that operate on the principle of the PCI IDs database.
The process of using such programs is usually simple: you run a scan, the utility finds a device with an unknown ID and suggests a name. For example, it might report that PCI\VEN_10EC&DEV_8822 - This Realtek RTL8822BE 802.11ac PCIe AdapterOnce you've got the exact name, finding the driver becomes a piece of cake. The main advantage of such programs is their autonomy: many have portable versions that can be run from a flash drive without installation.
However, be careful with so-called "driver packs" and automatic installers. While they often find and install the required driver, they can also install unnecessary adware or an incompatible driver version that only works reliably on the developer's test rig. Manual verification Finding a name through the device manager is always more reliable than blindly trusting the automation.
Where can I safely download a driver by ID?
Once you've determined the exact model or hardware ID, the next step is to find the download source. The number one priority is the official website of your laptop or motherboard manufacturer. This is where you'll find drivers that have been tested for compatibility with your specific device model. Even if the version listed there is older than the one on the chip manufacturer's website, it's often more stable.
If the laptop manufacturer's website doesn't have a driver (which may happen with older models), go to the chipset manufacturer's website (Intel, Realtek, AMD). It's important to be careful with the operating system's bit depth (x64 or x86) and version. Installing a Windows 10 driver on Windows 11 may work, but installing a Windows 7 driver on Windows 10 often results in compatibility errors.
There are also equipment ID directories such as Devid.info or PCI-ids.github.ioThese resources are useful when you simply need to find out what's going on behind the code. They don't always offer a direct driver download, but they do provide the exact name, which you can search for along with the word "driver download."
⚠️ Warning! Avoid websites with names like "driver-updater-free-download," which promise to "find all drivers in one click." These resources often contain modified versions of drivers with embedded miners or adware. Download only from the manufacturer's official domains.
When downloading, pay attention to the file extension. Drivers for Windows are usually supplied as .exe (installer) or .inf / .sys (files for manual installation via the manager). If you downloaded the archive .zip or .rar, it must be unpacked first. Running executable files from unverified archives is a direct path to compromising your PC's security.
☑️ Check before installing the driver
Manual installation and driver update
Once you have received the driver file, you need to install it correctly. If this .exe file, usually it's enough to run it and follow the wizard's instructions. However, if you only have files .inf, .sys And .cat (often found in driver packs or for older devices), you will have to use the manual installation method through the Device Manager.
Return to Device Manager, right-click the problematic device (or "Unknown Device"), and select "Update Driver." In the window that appears, select "Browse my computer for driver software." Next, specify the path to the folder where you unzipped the driver files. Make sure "Include subfolders" is checked so the system can find the driver you need. .inf file deep in the directory.
The system will attempt to find a compatible driver in the specified folder. If successful, the device will disappear from the "Unknown" list and appear under its name in the network adapters section. After this, it is mandatory to reboot computer to apply changes and correctly initialize the protocol stack.
Sometimes Windows may display a warning that "The best drivers for your device are already installed," but the device still doesn't work. In this case, click "Let me pick from a list of available drivers" and try selecting a different version from the list, or click "Have Disk" and force the path to the INF file. This can bypass digital signature or version verification in some cases.
Common problems and their solutions
Even with correct model identification, difficulties can arise. One common problem is the error Code 10 ("The device cannot start"). Often, this indicates not a missing driver, but a resource conflict, a power failure on the USB port (for external adapters), or a physical malfunction of the module. In such cases, completely removing the device from the Device Manager with the "Delete driver software" checkbox checked and then scanning for hardware changes can help.
Another issue is unstable operation after a driver update. If a new driver causes connection interruptions, it's a good idea to roll back to the previous version. There's a "Roll Back" button in the driver properties that returns system files to the state they were in before the last update. This often resolves issues that arose after an automatic update via Windows Update.
It's also worth checking your power settings. Windows tends to disable your Wi-Fi adapter to save power, which can cause it to freeze. In the device properties, under the "Power Management" tab, uncheck "Allow the computer to turn off this device to save power."
⚠️ Important! Settings interfaces and item names may vary slightly depending on your Windows version (10 or 11) and adapter manufacturer. If you don't see a specific option, look for a similar one in related menus.
Frequently Asked Questions (FAQ)
Is it possible to use a driver from a different adapter model from the same manufacturer?
In rare cases, this might work if the chipsets are identical, but it's a gamble. Drivers often contain specific power and frequency settings for a particular hardware implementation. Using the wrong driver can lead to reduced performance, overheating, or complete module failure. It's best to search for drivers strictly by hardware ID.
Why does Windows say the driver is installed, but there is no Wi-Fi?
This means the device is identified but cannot function. Possible causes include: the physical switch on the laptop case is off, disabled in the BIOS, a WLAN AutoConfig service failure, or an IP address conflict. Check if the Wi-Fi indicator on the keyboard is lit and if the service is active in services.msc.
Do I need to remove the old driver before installing the new one?
When upgrading (for example, from 2.0 to 2.1), a simple over-install is usually sufficient. However, if you're changing manufacturers or troubleshooting errors, we recommend using dedicated utilities for a complete cleanup (Clean Install) or uninstalling the device through the device manager with a file cleanup to avoid registry conflicts.
Where can I find a driver if there is none for my OS (for example, Windows 11)?
Try installing a driver for Windows 10. In most cases, Windows 10 drivers are fully compatible with Windows 11. Installing in compatibility mode (right-click the installer -> Properties -> Compatibility) increases the chances of success.
How do I know if I have a built-in Wi-Fi adapter or a USB one?
In Device Manager, integrated adapters are usually listed as PCIe devices (often with "PCIe" in the name), while USB adapters are listed as USB Network. USB adapters can also disappear from the list when physically disconnected, which is easy to verify experimentally.