Identifying the hardware of a wireless network interface often poses a problem for users when standard drivers stop working or the system stops detecting the device after reinstalling the operating system. Owners of USB adapters and laptops are faced with a situation where Windows identifies the device as "Unknown Device" or assigns it a standard Microsoft ID without providing any configuration options. Understanding which one chipset used in your adapter is the key to finding the correct software and stable network operation.
Adapter manufacturers such as TP-Link, D-Link, or Xiaomi often use third-party chips from companies like Realtek, MediaTek, or Atheros in their products. The hardware version (HV) can vary even within a single adapter model, making the box markings inaccurate for selecting drivers. Therefore, knowing the exact version Vendor ID And Device ID becomes a critical skill for any advanced user.
In this article, we'll cover all available methods for identifying chipsets: from built-in operating system tools to specialized utilities and the Linux command line. You'll learn how to read technical specifications and understand why the same adapter may behave differently on different computers. This knowledge will help you avoid installing unstable driver versions and hardware conflicts.
Using Device Manager in Windows
The most accessible way to obtain primary information about network equipment is the built-in system tool device ManagerHowever, the standard display often hides technical details, showing only the marketing name of the model. To get to the bottom of things, you need to go to the properties of a specific device and open the "Details" tab. Here, from the drop-down list of parameters, select the line Equipment ID or Device Information.
You will see lines like this PCI\VEN_10EC&DEV_8822 or USB\VID_0BDA&PID_8812The key values here are after VEN (Vendor) and DEV (Device) or VID And PID for USB. For example, code 10EC or 0BDA clearly indicates the chip manufacturer Realtek, A 168C indicates the use of solutions from Qualcomm AtherosThe numbers after DEV or PID are a unique identifier for a specific crystal model.
If the system displays the device as "Unknown Device" with a yellow exclamation point, the method remains the same: the unknown device's properties contain all the necessary codes for searching for a driver online. Windows can sometimes misidentify a device, so double-checking the codes using other utilities is a good idea.
⚠️ Warning: Do not attempt to install drivers based solely on the adapter model name printed on the case. The plastic case may contain different board versions with different chipsets.
- 📌 Open Device Manager using the command
devmgmt.msc. - 📌 Find the "Network adapters" or "Other devices" section.
- 📌 Copy the hardware ID string to search the database.
Analysis via the command line and PowerShell
For those who prefer a text-based interface or don't have access to a graphical shell, the Windows command line is a powerful tool. wmic (Windows Management Instrumentation Command-line) allows you to display detailed information about network interfaces. The command
wmic path win32_networkadapter where "NetEnabled=true" get name, AdapterType, ManufacturerA more in-depth analysis is available through PowerShell, which is standard for modern versions of Windows. Using the cmdlet Get-NetAdapter, you can get a list of interfaces and then use filters to find out details about the driver and its version. However, to get exactly ChipID It is better to use queries to WMI classes that return raw data about the equipment, including PNPDeviceID.
It's important to understand that standard commands may not display the device ID if the device driver is completely missing and it's identified as a basic system device. In such cases, the Device Manager graphical interface or third-party software are more effective. However, for quickly checking the driver status and version, the command line is ideal.
Secret command for export
You can dump a full report of all devices to a text file using the systeminfo command or more specific pnputil queries to analyze them later in a text editor.
Specialized utilities for identification
When built-in tools aren't enough, specialized programs created by enthusiasts and engineers for in-depth hardware diagnostics come to the rescue. One of the most reputable utilities is HWINFO or AIDA64, which read data directly from device registers. These programs display not only the chip name, but also its temperature, current connection speed, supported standards, and even voltage.
There are also lightweight portable utilities such as USBDeview or Device ID, which don't require installation. They're especially useful for USB adapters, as they display a history of connected devices and their vendors. USBDeview It does a great job of displaying VID/PID even for devices that are not currently connected but whose drivers remain in the system.
Using third-party software requires caution: download programs only from the developers' official websites. Malware often disguises itself as diagnostic utilities. Time-tested tools like CPU-Z (Devices tab) can also provide basic information about PCI devices, including network cards.
| Utility | Type | Level of detail | Platform |
|---|---|---|---|
| HWINFO64 | Diagnostics | High | Windows |
| USBDeview | Monitoring | Average | Windows |
| AIDA64 | Audit | Maximum | Windows |
| lspci / lsusb | CLI | High | Linux |
Determining the chipset in the Linux operating system
In the Linux world, hardware identification is traditionally performed through a terminal, which provides direct access to the system kernel. For PCI interfaces (integrated cards, MiniPCIe), the command lspci, and for USB adapters - lsusbAdding a flag -v (verbose) or -nn (numeric IDs) allows you to see the vendor and device numeric identifiers that are needed to search for drivers.
After executing the command lsusb You'll get a list of all USB devices. Find your Wi-Fi adapter in the list; often the chip name is already listed, for example, "Realtek Semiconductor Corp. 802.11ac NIC." If only "Unknown Device" is displayed, the numeric codes after ID (For example, 2357:0120) can be entered into the database linux-usb.org for accurate identification.
For more convenient reading of information, you can use the utility inxi, which formats the output in a readable form. The command inxi -N will display network information, including the driver the device is currently using. This is critical, as Linux often uses open-source drivers (e.g., ath9k or rtw88), the name of which directly indicates the chipset family.
☑️ Checking on Linux
Decoding vendor and device codes
Understanding what lies behind hexadecimal codes allows you to instantly navigate the sea of hardware. The most common chip manufacturer for budget and mid-range adapters is RealtekTheir chips, such as RTL8812AU or RTL8723BU, are known for their availability, but often require manual compilation of drivers on Linux or finding specific versions for Windows 10/11.
Company MediaTek (formerly Ralink) also holds a significant market share, especially in the USB adapter segment. Chips of the series MT76xx They are often found in Xiaomi and TP-Link devices. They are known for their good out-of-the-box Linux compatibility, but can have connection stability issues in Windows when using standard Microsoft drivers.
The more premium segment is represented by chips Intel (AC and AX series), which are typically built into laptops. They are characterized by high stability and excellent performance with the Bluetooth protocol, as they are often combined modules. Chips Qualcomm Atheros have historically been considered the benchmark for stability, although their share of the consumer USB adapter market has declined in recent years.
⚠️ Please note: Driver interfaces and names may change with the release of new operating system versions. Always check the compatibility of a specific driver version with your OS version on the chip manufacturer's website.
- 🔍 10EC / 0BDA — Realtek (the most popular, often capricious drivers).
- 🔍 8086 — Intel (high stability, often found in laptops).
- 🔍 168C — Qualcomm Atheros (good Linux support).
- 🔍 0E8D — MediaTek / Ralink (budget segment, USB dongles).
Common problems and their solutions
One of the most common problems is when the adapter is detected but does not work at high speeds. This often happens when the chip Realtek A generic Windows driver is installed, which doesn't support all the device's features. As a result, the adapter may only operate in the 2.4 GHz band, ignoring 5 GHz, or may not support monitor mode.
Another issue is IRQ or resource conflicts, although these are rare in modern UEFI systems. Most often, the problem stems from power saving: the system disables the Wi-Fi module to conserve power, after which it fails to initialize correctly. Disabling the "Allow the computer to turn off this device to save power" option in the USB root properties or the adapter itself often resolves the issue.
If you updated your BIOS or operating system and Wi-Fi is gone, the new software version may have changed the way it interacts with your hardware. In such cases, rolling back the driver or installing a version specifically marked as compatible with the latest Windows updates can help. Sometimes, completely removing the device from the Device Manager, clearing the drivers, and then rebooting can help.
Why does Device Manager show "Unknown Device"?
This means that the operating system sees a physical connection, but doesn't have a mapping between the hardware ID and the name and driver in its database. The device is functional; it just needs a "translator."
Is it possible to find out the chip without installing drivers?
Yes, the hardware ID (VID/PID) is read at the bus level and is available to the system immediately after connection, even if the driver is not installed. These codes are what you need to search for the driver.
Does the adapter version (V1, V2, V3) affect the chip?
Yes, this is the most common pitfall. The manufacturer can change the internal configuration of a model, keeping the appearance and name, but replacing the chipset with a cheaper or newer one. Drivers from the V1 may not work on the V2.
Where can I find a database of VID and PID codes?
There are open repositories such as pci-ids.ucw.cz or linux-usb.org that contain up-to-date lists of all known hardware identifiers.
Is it worth buying an adapter with an unknown chip?
If you can't find information about the chipset before purchasing, it's best to hold off. Open information about the controller used is a sign of manufacturer transparency and a guarantee of future driver availability.