A device with a yellow mark and no name is not a mystery. The hardware ID encodes vendor and device numbers, and Windows already knows which driver package failed to bind.
Read **Hardware Ids** in Device Manager, split the **VEN_** and **DEV_** numbers, then match the package with **pnputil /enum-devices /problem**. Install the right INF instead of guessing a driver name.
The device shows as **Unknown device** because no INF claimed it. The Details tab still reports the identifier the firmware presents, which is the only reliable search key.
Get-PnpDevice -Status Error | Select-Object FriendlyName,InstanceId,Class
Get-PnpDevice -Status Error | Select-Object -ExpandProperty HardwareID**VEN_8086** is the vendor, **DEV_a7a0** the device, **SUBSYS** the board-specific variant. The vendor number is what you search first, and the subsystem decides between two almost identical models.
$id = (Get-PnpDevice -Status Error | Select-Object -First 1).HardwareID[0]
$id
$id -match 'VEN_(\w{4})' | Out-Null
"Vendor: $($Matches[1])"
$id -match 'DEV_(\w{4})' | Out-Null
"Device: $($Matches[1])"**pnputil /enum-devices /problem** lists only the broken devices with the problem code. Code 28 means no driver, code 10 means the driver loaded and failed, code 43 means the device reported an error.
pnputil /enum-devices /problem
pnputil /enum-devices /problem /class USB
Get-PnpDevice -Status Error | Select-Object FriendlyName,Problem,ProblemDescriptionDrivers stay in the driver store after a failed attempt. **pnputil /enum-drivers** shows the OEM package names, and the INF usually names the vendor and the model family.
pnputil /enum-drivers | Select-String -Pattern 'oem|Provider|Class' -Context 0,1
Get-WindowsDriver -Online | Where-Object { $_.ClassName -eq 'USB' } | Select-Object Driver,ProviderName,Version,Date**/add-driver** stages the INF and **/install** binds it to matching hardware. A package for the wrong subsystem installs without error and leaves the device broken, so compare the ID first.
pnputil /add-driver C:\drivers\chipset\*.inf /install /subdirs
Get-PnpDevice -Status Error | Select-Object FriendlyName,Status,Problem
Get-PnpDevice | Where-Object InstanceId -like '*VEN_8086*' | Select-Object FriendlyName,StatusA device without a problem code and with a proper name is bound. Keep the hardware ID in the ticket or the machine notes; the next reinstall is then a two-minute job.
Get-PnpDevice -Class USB,Net,Display | Where-Object Status -ne 'OK' | Select-Object FriendlyName,Status
Get-PnpDevice | Where-Object InstanceId -like '*VEN_8086*' | Select-Object FriendlyName,Status,DriverVersionEnable View > Show hidden devices. A device that is present only while powered needs the check to run with the hardware plugged in.
The INF targets another architecture or another hardware ID. Compare the SUBSYS value in the INF with the one Device Manager reports.
The driver bound and then failed. Remove the device with pnputil /remove-device, reboot, and let Windows bind it again with the same package.
Check the vendor page for the exact model revision and for a Windows 11 build. An older package often installs with compatibility mode but fails at runtime.
No. The hardware ID describes the model, so every device of that model shares it; the serial number identifies the single unit.
Yes, if the package contains an INF. Point pnputil at the INF file and skip the installer that adds services and tray icons.
In the driver store under C:\Windows\System32\DriverStore\FileRepository. Removing it from there with pnputil /delete-driver is the clean uninstall.
Remove the package you added with pnputil /delete-driver oemNN.inf /uninstall and reboot. Get the exact oem name from pnputil /enum-drivers.
Free · no account needed · tracks your progress