Unknown device: working out what it is and which driver it needs
DeviceInBox editorial team · Last updated October 6, 2026
"Unknown device" is what Device Manager shows when Windows cannot work out what a device is at all. It differs from entries like Ethernet Controller or PCI Device, where at least the device class is known. An unknown device either answered with no usable identification, or its descriptor could not be read, so Windows has nothing to match a driver against.
Start with the hardware ID, even if it looks useless
Open Properties, the Details tab, and select Hardware Ids. What you see decides everything that follows:
- A normal ID such as
PCI\VEN_8086&DEV_9D3AorUSB\VID_0BDA&PID_8179: the device is fine and only needs the right driver. Look the ID up and install it. USB\VID_0000&PID_0002orUSB\DEVICE_DESCRIPTOR_FAILURE: the device did not answer properly. That is a connection or power problem, not a driver problem. See Device Descriptor Request Failed.ACPI\with a vendor prefix, for exampleACPI\INT33A0orACPI\VEN_INT&DEV_33A0: a platform device on the motherboard. It needs the chipset or platform package from the laptop maker.HID\VID_...orUSB\VID_...&MI_01: one function of a composite device, usually a keyboard, mouse or dock with extra buttons.
Paste whatever you found here:
Work out which device it is
Device Manager lists the entry without saying where it is. Three things narrow it down:
- Unplug external devices one at a time and press F5 in Device Manager. The entry that disappears belongs to the device you just unplugged.
- Open View, then "Devices by connection". The unknown device appears under the controller it hangs on, which tells you whether it is on a USB hub, on the PCI bus or on the ACPI tree.
- Check the Events tab in Properties. The install date usually matches a dock, a printer or a laptop feature you added.
ACPI devices on laptops
On laptops most unknown devices are ACPI entries for things the chipset or the vendor's firmware exposes: the ambient light sensor, the lid switch, hotkey controllers, the fingerprint power rail, the thermal framework. They have no PCI or USB ID at all, so a generic driver search finds nothing. Install, in this order, the chipset package for the platform, then the vendor's own platform or hotkey package for that exact laptop model.
- Intel Chipset Device Software Driver 10.1.20003.8622 (Nov 5, 2024, Windows 10, 11)
- Intel Chipset Device Software Driver 10.1.19900.8599 (Jul 20, 2024, Windows 10, 11)
Common ACPI IDs and what they usually are: INT33A0 Intel Smart Connect, INT3400 to INT3406 the dynamic thermal framework, INT344B and ELAN or SYNA entries I2C touchpads, INT3F0D a chipset ACPI bridge.
Let Windows look first
Before hunting for a package by hand, open Settings, Windows Update, Advanced options, Optional updates and expand Driver updates. Microsoft distributes drivers for most chipset, card reader and fingerprint devices there, and they install cleanly.
If that list is empty, right-click the unknown device, choose Update driver, then "Search automatically for drivers". That queries the same catalog for the exact ID.
Devices that should not be there at all
Some unknown devices belong to hardware that no longer exists: a phone that was once connected in a special mode, a printer removed years ago, a virtual device from software that was uninstalled. Turn on View, then "Show hidden devices". Entries shown greyed out are not present now, and removing them changes nothing about how the machine works. If an unknown device reappears a second after you remove it, the hardware is present and still needs a driver.
Related: Base System Device, PCI Device and Code 28.
More guides
- Find your hardware ID
- Unknown USB Device (Device Descriptor Request Failed)
- Code 43: device reported problems
- Code 10: this device cannot start
- SM Bus Controller driver
- PCI Simple Communications Controller
- PCI Data Acquisition and Signal Processing Controller
- Base System Device driver
- PCI Device driver missing
- Ethernet Controller driver missing
- Network Controller driver missing
- Code 28: drivers are not installed
- Code 31: Windows cannot load the drivers
- Code 39: driver corrupted or missing
- Code 52: digital signature problem
- USB device not recognized
- Install a driver from an INF file
- Wi-Fi gone after a Windows update
- Bluetooth missing from Windows
- SD card reader not working