How to identify unknown devices with hardware IDs

Fresh Windows installs and rebuilt PCs often leave a handful of mystery entries scattered through Device Manager, each with a yellow warning and a vague label. Chasing them one by one, with no plan, wastes an afternoon. A tidier approach clears the whole list systematically: identify each device, install drivers in the right order, and recheck as you go so the entries that resolve stop distracting you. Follow this cleanup workflow and you'll turn a page full of unknowns into a fully recognized set of hardware, using only tools built into Windows.

1. 1

   Take stock of every warning

   Right-click the Start button and open Device Manager. From the View menu, turn on "Show hidden devices" so nothing stays out of sight. Scroll through and note every entry with a yellow warning triangle or a red mark, plus anything sitting under "Other devices" with a generic name. Jot down a quick list. Getting the full picture up front stops you from fixing one device, celebrating, and then discovering three more you missed. It also helps you spot patterns, like several unknowns that all turn out to belong to the same chipset once you start installing.

2. 2

   Set a restore point before you start

   Since you'll be installing several drivers in a row, create one safety net now. In the Start search box, type "Create a restore point" and open it. Confirm protection is on for your system drive, then click Create and name it something like "before driver cleanup." With a restore point in place, if any single driver causes trouble you can roll back the whole session rather than trying to unpick which change broke things. One restore point covers the entire cleanup, so you don't need to make a new one before each install.

3. 3

   Install the chipset drivers first

   Order matters. Many unknown entries are motherboard functions that only get proper names after the chipset driver is in place. Head to your PC or motherboard maker's official support page, find the chipset package for your exact model and Windows version, and install it before anything else. This often clears several mystery entries at once, since it teaches Windows what the built-in controllers, hubs, and management interfaces actually are. Installing graphics, audio, or network drivers before the chipset can leave devices half-recognized, so resist the urge to jump ahead to the interesting hardware.

4. 4

   Recheck Device Manager after each install

   After the chipset install and a reboot, return to Device Manager and compare it against your list. Some entries will now show real names and lose their warning icons. Cross those off. This recheck step is the heart of the workflow: it tells you what's genuinely left rather than what you assumed was still broken. Use the Action menu's "Scan for hardware changes" to nudge Windows into re-evaluating. Working in rounds like this, install then recheck, keeps you from installing drivers for devices that already quietly resolved themselves a step earlier.

5. 5

   Read the Events tab for clues

   For a stubborn unknown, right-click it, choose Properties, and open the Events tab. It shows a timeline of what Windows tried to do with the device, including which driver it searched for and whether it found one. The messages sometimes name the hardware or point to a missing package. Click "View All Events" to open the fuller log in Event Viewer if you need more detail. This history often explains why a device stayed unknown, such as Windows finding no matching driver, which tells you to go get one rather than keep rescanning and hoping.

6. 6

   Check Windows Update optional updates

   Windows keeps many drivers as optional updates that don't install automatically. Open Settings, go to Windows Update, then Advanced options, and select Optional updates. Expand the Driver updates section and you may find matches for your remaining unknown devices. Tick the ones that clearly fit and install them. This is a legitimate, Microsoft-hosted source, so it's a safe way to resolve leftovers without visiting any third-party download site. Recheck Device Manager afterward, since a couple more entries often clear here, especially for common network and peripheral chips.

7. 7

   Chase down the final holdouts

   Whatever's left after chipset, reboot, and optional updates is likely a specific component needing its exact driver. Open the holdout's Properties, go to Details, and read its Hardware Ids to learn the vendor and model. Use that to find the correct package on the manufacturer's official support page. Install it, reboot, and recheck. Repeat for each remaining device. Working through the survivors individually, armed with their real hardware IDs, is far faster than random attempts, and it's usually just one or two devices by this point rather than the full list you started with.

8. 8

   Confirm a clean device list

   When you think you're done, do a final pass through Device Manager with hidden devices still shown. There should be no yellow triangles and nothing left under "Other devices." Expand a few categories to confirm the names look like real hardware rather than generic placeholders. If everything reads cleanly, your cleanup is complete. Consider keeping a note of which official support pages had the drivers you needed, so the next time you rebuild this machine you can repeat the process quickly instead of rediscovering every source from scratch.