Match the symptom before changing settings
| What you observe | Where to focus |
|---|---|
| Unknown device appears under Other devices | Read Hardware Ids and locate the exact OEM component |
| PCI Device or SM Bus Controller is unknown | Install chipset and platform drivers from the PC maker |
| Unknown USB Device appears only when connected | Test the accessory, cable, port and USB descriptor |
| ACPI entry remains unknown after reinstall | Install the OEM system-interface, hotkey or sensor package |
Diagnose unknown device before replacing drivers
Open Properties for the Unknown device and capture Hardware Ids plus Device status. Code 28 often indicates a missing driver, but the hardware ID is needed to know which one.
Confirm what hardware was recently connected or changed. For removable devices, disconnect and reconnect one at a time so the unknown entry can be matched to a physical device.
Use the symptom evidence to select the correct layer. “Unknown device appears under Other devices” points toward read hardware ids and locate the exact oem component, while “PCI Device or SM Bus Controller is unknown” suggests install chipset and platform drivers from the pc maker. Also note what changed immediately before the failure: a Windows update, driver package, new dock, BIOS update, sleep or hibernation cycle, physical impact, liquid exposure or installation of device-management software.
Use the hardware ID to identify the exact manufacturer/device, then obtain the driver from Windows Update or the PC/component maker. Do not guess from similar product names.
Restart Windows and disconnect recent accessories one at a time. If the unknown entry vanishes with a specific device, you have identified the hardware boundary.
The remaining symptoms also narrow the search: “Unknown USB Device appears only when connected” means you should test the accessory, cable, port and usb descriptor, while “ACPI entry remains unknown after reinstall” means you should install the oem system-interface, hotkey or sensor package. After each repair, verify the original function rather than accepting a successful installer message. A package can finish correctly while Windows still loads another driver or the hardware remains unavailable.
Use Hardware Ids instead of guessing
Open Properties > Details and select Hardware Ids. Copy the longest value. PCI entries commonly contain VEN and DEV identifiers; USB entries use VID and PID; ACPI entries often name a platform component. Search those identifiers together with the exact PC model on the manufacturer's support site.
Do not choose a driver merely because its category sounds correct. A laptop may contain vendor-specific power, hotkey, fingerprint, card-reader and sensor devices. The PC maker's package accounts for firmware and platform dependencies that a random generic file may miss.
1Install platform dependencies first
- Install the supported chipset package.
- Add Serial IO, management engine or system-interface packages when listed.
- Restart, then scan for hardware changes.
2Identify removable hardware separately
- Disconnect the accessory and see whether the unknown entry disappears.
- Reconnect directly with a known-good cable.
- Use the accessory manufacturer's model-specific installer.
Interpret common unknown-device names
SM Bus Controller, PCI Data Acquisition and Signal Processing Controller, Base System Device and PCI Encryption/Decryption Controller often belong to the chipset or platform stack. An unknown Multimedia Controller may need audio or capture drivers, while an unknown Network Controller normally needs Wi-Fi or Ethernet support.
A USB descriptor failure is different: Windows cannot reliably read the device identity. Try another port and cable, remove an unpowered hub, fully shut down and restart the PC, and test the device elsewhere before hunting for a model-specific driver.
Resolve duplicate, stale and virtual entries
Use View > Show hidden devices cautiously. Greyed entries can represent disconnected accessories and are not automatically faults. Remove an old entry only when it conflicts with the current device or belongs to hardware that will no longer be used.
Virtual machines, phone utilities, RGB software, VPN clients and emulators may install virtual devices. Repair or uninstall the owning application rather than substituting a physical-hardware driver. If the entry returns immediately, inspect its Hardware Ids and service provider again.
Verify the repair before making more changes
Restart Windows—not only the affected app—and confirm that the unknown entry is replaced by the correct named device without an error code. Check Device Manager again: the device should remain present without a warning icon, and Device status should say it is working properly.
After identifying and installing the proper driver, confirm the unknown entry disappears, the real device appears by name, restart Windows, and test its function.
Technical order checked against Microsoft's current Device Manager guidance. Device-specific menus and driver availability vary by manufacturer.
Frequently asked questions
What is an Unknown device in Device Manager?
Windows detected hardware but does not have enough driver information to name and operate it correctly.
How do I find the manufacturer of an Unknown device?
Open Properties > Details > Hardware Ids and use the vendor and device identifiers with the official PC or hardware support site.
Can an Unknown device be harmless?
It may be an unused feature, but it still deserves identification because missing platform drivers can affect power, sensors or stability.