Yellow Exclamation in Device Manager? Read the Error Code First

Right-click the flagged device, select Properties, and read the specific error code in the Device status box before touching any driver – Code 10, Code 28, Code 43, and Code 45 each have a different root cause and a different fix, and the standard update the driver advice only resolves one of them. The yellow exclamation mark in Device Manager is not a single error – it is a visual flag that one of many possible device errors has occurred. Applying the wrong fix wastes time and can cause new problems. Reading the error code first takes less than 30 seconds and tells you exactly which fix path to follow.

How to Read the Error Code

Open Device Manager (press Win + X and select Device Manager). Find the device showing the yellow triangle. Right-click it and select Properties. Go to the General tab. In the Device status section, Windows shows the error description and the error code in parentheses – for example, This device cannot start. (Code 10). Note this code before doing anything else. If the description is long, read all of it – sometimes it includes the specific sub-error, NTSTATUS code, or a hint about the root cause that the code alone does not convey. The General tab also shows whether the device is listed correctly in the device tree or under a mismatched category, which is sometimes a diagnostic clue on its own.

Code 10 – This Device Cannot Start

Code 10 means the driver file loaded into memory successfully but the device initialization failed – the driver could not communicate with the hardware, or the hardware did not respond in the expected way. This is different from a missing driver (Code 28) or a blocked driver (Code 52). The driver is present and Windows is actively trying to use it, but the device is not cooperating.

Common Causes of Code 10

The most common cause after a Windows update is that Windows Update replaced a working OEM driver with a generic Microsoft-provided driver that does not support the full hardware feature set. The generic driver loads without error but fails at the initialization handshake with the device. Other causes include corrupted driver files, hardware failure at the device level, a resource conflict (IRQ, memory address), or a firmware incompatibility between the driver and the current BIOS version.

Per James K., who is a Desktop Support Specialist at Deloitte, “Code 10 errors after Windows Update are almost always caused by the automatic driver replacement pushing a generic driver over a working OEM one. Rolling back manually is faster than waiting for Microsoft to fix it – and checking the code before doing anything is what makes the difference between fixing it in five minutes or wasting an hour on the wrong solution.”

Fix – Roll Back the Driver

If Code 10 appeared after a Windows Update, try rolling back first. Right-click the device in Device Manager, select Properties, go to the Driver tab, and click Roll Back Driver. If the button is greyed out, the previous driver was not retained by Windows – you will need to download it from the manufacturer. If Roll Back is available, click it, select the reason (driver update made it worse), and restart. In most cases this restores the previous working driver and Code 10 disappears. To prevent Windows Update from replacing the driver again after rollback, use the wushowhide tool to hide the driver update – download it from Microsoft Support and run it to hide the specific driver update that caused the Code 10.

Fix – Reinstall From the Manufacturer

If Roll Back is not available or does not resolve Code 10, uninstall the driver completely. Right-click the device, select Uninstall device, and tick the box to Delete the driver software for this device. Restart. After the reboot, download the driver directly from the device manufacturer’s support site and install it. For laptops, use the laptop manufacturer’s driver (Dell, Lenovo, HP) rather than the chipset or component manufacturer’s driver – OEM builds are customized for the specific hardware configuration. After reinstallation, Code 10 should be gone. If Code 10 returns after fresh reinstall, check the device in another PC to rule out hardware failure. According to Microsoft’s Windows Update FAQ, using manufacturer-provided drivers is recommended when Windows Update’s generic driver does not work for a specific device.

Code 28 – Drivers Not Installed

Code 28 means Windows found the hardware device on the bus (PCI, USB, or other) but has no driver at all in its driver store for it. The device is physically present and detectable, but completely non-functional because no driver has been matched to it. This commonly happens after a clean Windows install, when using new or uncommon hardware, or when a driver is uninstalled without being reinstalled.

Fix – Automatic Driver Search

Right-click the device in Device Manager and select Update driver. Choose Search automatically for drivers. Windows will check its local driver store and Windows Update. If the driver is found, it installs automatically and Code 28 is resolved. Also check Settings > Windows Update > Advanced Options > Optional Updates – Microsoft surfaces device-specific drivers here that do not appear in the main Windows Update scan. This method resolves Code 28 for most common hardware including Bluetooth adapters, audio codecs, USB hubs, and built-in webcams.

Fix – Hardware ID Manual Lookup

If automatic search finds nothing, right-click the device, select Properties, go to the Details tab, and change the Property dropdown to Hardware IDs. Copy the first entry in the list – it will look like USB\VID_0BDA&PID_8153 or PCI\VEN_8086&DEV_A0E8. Paste this string into a web search. The VEN and VID codes identify the manufacturer (VEN_8086 = Intel, VEN_10DE = NVIDIA, VEN_10EC = Realtek, VID_0BDA = Realtek USB). The DEV and PID codes identify the specific product. Once you know the manufacturer and model, go to their official support site, find the download page for that device, and install the driver manually. This method identifies the exact driver needed without guessing from device names, which can be generic or incorrect.

Code 43 – Windows Has Stopped This Device

Code 43 means the device itself reported an unspecified failure to the Windows driver – the hardware signalled an error that the driver could not handle or recover from. Unlike Code 10 where initialization fails, Code 43 typically indicates the device was working and then stopped, or it is working intermittently. The fix depends heavily on the device type.

Code 43 on USB Devices

For USB devices, work through these checks in order before touching drivers. First, try a different USB port – the current port may have a power or signal integrity issue. Second, try a different USB cable – cable faults cause many Code 43 reports. Third, test the same device on a different PC to confirm whether the hardware itself is working. If the device is fine on another PC, the issue is on your Windows install.

The most effective and overlooked fix for USB Code 43 on laptops is the USB Root Hub power management setting. Open Device Manager, expand Universal Serial Bus controllers, right-click the first USB Root Hub entry, select Properties, go to the Power Management tab, and uncheck Allow the computer to turn off this device to save power. Repeat for every USB Root Hub entry listed. Restart. Windows aggressively suspends USB devices on battery-powered machines, and this power management setting causes Code 43 when a device cannot wake properly from the suspended state. This single setting resolves a large percentage of USB Code 43 reports on laptops that other guides miss entirely.

If power management is not the cause, right-click the USB device in Device Manager, select Uninstall device, tick delete driver software if shown, unplug the device for 30 seconds, then reconnect. Windows will re-detect and reinstall fresh. If Code 43 returns, download the latest driver from the device manufacturer directly instead of relying on Windows automatic detection.

Code 43 on GPUs

GPU Code 43 is a separate problem from USB Code 43. It appears after driver corruption, after a failed overclock session, after Windows Update replaces a working driver, or during hardware failure. For driver-related GPU Code 43, the correct fix is a clean uninstall using DDU (Display Driver Uninstaller) – a free tool specifically designed to remove GPU drivers completely, including registry entries that a standard uninstall leaves behind. Boot into Safe Mode (hold Shift, click Restart, go to Troubleshoot > Advanced Options > Startup Settings, press 4). In Safe Mode, run DDU, select your GPU brand (NVIDIA, AMD, or Intel), and choose Clean and restart. After the DDU restart, boot normally, download the latest GPU driver from the manufacturer site, and install fresh. Standard GPU driver reinstalls without DDU often leave behind residual registry entries that cause Code 43 to return immediately after install. DDU removes everything including those entries.

If Code 43 on a GPU persists after a DDU reinstall, test the GPU in a different PCIe slot or in a different PC to check for hardware failure. A GPU that returns Code 43 on multiple systems with clean drivers is usually failing hardware. See the DDU download page on TechPowerUp for the latest version of Display Driver Uninstaller.

Code 45 – Currently Disconnected

Code 45 (formally: Currently, this hardware device is not connected to the computer) means Windows has a driver and device record for the hardware but cannot detect the hardware on the bus at boot time. The most obvious cause is a physically disconnected device – an unplugged PCIe card, a disconnected SATA or M.2 drive, a detached front-panel USB cable, or a USB device that was removed. Check all physical connections first.

A less obvious cause that most guides miss: Code 45 can appear for devices that are physically connected but disabled in UEFI. Check your BIOS for the relevant controller. Common examples: on-board audio that is disabled under Advanced > Onboard Devices, a secondary SATA controller that is off, or a Thunderbolt port disabled under USB/PCIe settings. Enable the controller in UEFI, save, and restart – the device will reappear in Device Manager without the yellow triangle, and no driver action is needed at all. I have seen this on Dell OptiPlex machines where the previous user disabled the onboard NIC in BIOS as a security measure. Enabling it in UEFI brought the adapter back immediately with Code 45 gone and no driver reinstall required.

Code 22 – Device Is Disabled

Code 22 is the simplest of all Device Manager errors – the device was manually disabled by a user. This is not a driver problem. Right-click the device in Device Manager and select Enable device. The yellow triangle will disappear and the device will become active. No driver download, reinstall, or restart is needed. Code 22 most commonly appears when a user or an IT administrator disabled a device to troubleshoot something and forgot to re-enable it, or when a profile or script applied to the machine disabled a specific controller.

Code 52 – Windows Cannot Verify the Digital Signature

Code 52 means Windows detected a driver signing problem – the driver’s digital signature cannot be verified. This happens when a driver was installed without valid code signing, when the driver’s certificate has expired, or when Memory Integrity (HVCI) is blocking the driver because it fails the kernel integrity check. Unlike Code 28 (no driver at all), Code 52 means a driver is installed but Windows refuses to load it. The fix depends on why the signature is failing. Check Windows Security > Device Security > Core Isolation Details for any incompatible driver warnings – if the driver appears there, HVCI is the enforcement layer. See the fixes for Memory Integrity in the HVCI driver blocking guide. If no HVCI warning exists, the driver’s certificate itself may be invalid – download a fresh copy from the manufacturer and reinstall.

BIOS and Firmware as a Root Cause

A frequently overlooked cause of persistent yellow exclamation marks – especially for built-in hardware like audio controllers, Bluetooth adapters, and network cards – is a BIOS or UEFI firmware bug. Some Code 10 and Code 43 errors on specific motherboard and hardware combinations are caused by firmware-level initialization failures that no driver update can fix. Check your motherboard manufacturer’s site for BIOS firmware updates. Release notes will sometimes explicitly mention USB compatibility fixes, PCIe device initialization improvements, or audio controller corrections. Applying a firmware update when one of these conditions is mentioned can clear persistent Device Manager errors that all driver reinstalls failed to resolve. This step is especially relevant for newly-released CPUs and motherboard platforms where early BIOS builds have known hardware initialization issues.

Frequently Asked Questions

Can I have a yellow exclamation on a device that is still working?

Yes – in some cases a device will function partially while showing a yellow triangle. Code 10 on an audio device, for example, may mean one feature (like microphone capture) is broken while speaker output works. Code 43 on a USB hub may mean the hub works but one port does not. Always check whether the hardware you care about is actually affected before spending time troubleshooting – the error may be on a secondary function you do not need.

What if Device Manager shows the correct driver version but the device still does not work?

Driver version in Device Manager confirms the driver file is installed – it does not confirm the driver loaded and initialized successfully. Check the Device status on the General tab for the error code. Then open Event Viewer (eventvwr.msc), go to Windows Logs > System, and filter for the device’s hardware ID or the source name matching the driver. Runtime initialization errors produce Event Log entries that Device Manager does not show but that contain the specific failure reason, which is often an NTSTATUS code pointing to the exact hardware or configuration issue.

Should I uninstall a device with a yellow exclamation before reinstalling the driver?

For Code 28 (no driver) and Code 10 (driver failed to initialize), yes – uninstalling the device entry and deleting the driver software before reinstalling gives the cleanest result and avoids conflicts with cached driver store entries. For Code 22 (disabled) and Code 45 (disconnected), uninstalling is unnecessary and counterproductive – the fix is enabling the device or reconnecting the hardware. Always match the fix to the specific error code.

Why do yellow exclamation marks appear in Device Manager after a clean Windows install?

A clean Windows install includes only the drivers bundled in the installation image, which covers the most common hardware but not all devices. Less common hardware – specific audio controllers, integrated WiFi adapters, embedded Bluetooth, touchpad models, and fingerprint readers – will show as unknown devices or Code 28 after a clean install until the correct driver is installed. Running Windows Update fully (including Optional Updates) after a clean install resolves most of these automatically. The remaining ones require manual downloads from the device or laptop manufacturer’s support page.

Is it safe to ignore a yellow exclamation on a device I do not use?

For devices you genuinely do not use, a persistent yellow triangle is mostly cosmetic – it does not affect system stability or security. The exception is when the erroring device is a core system component like a chipset controller, storage controller, or USB host controller, where the error may affect other hardware that routes through it. For peripheral devices like a secondary audio interface, an old webcam, or a legacy port controller, leaving the error in place is generally acceptable. Confirm what the device is before ignoring it – the error may be on something more important than it looks.

Conclusion

The yellow exclamation mark in Device Manager covers a wide range of problems – reading the specific error code first is the essential step that determines the correct fix. Code 10 usually means a driver rollback or fresh manufacturer reinstall. Code 28 means no driver is installed and requires a hardware ID lookup. Code 43 on USB devices is often a power management setting before it is a driver problem; on GPUs it requires DDU. Code 45 and Code 22 are usually a physical connection or a BIOS setting, not a driver issue at all. Match the fix to the code and you resolve most cases on the first attempt.