Fix Device Manager problems by checking the device’s status code first, then taking the safest path: restart and rescan, verify hardware and services, remove recent changes, and update or reinstall drivers only after that. Guesswork can hide devices, break networking, audio, or input, and turn a small driver fault into a boot or stability problem. This guide lists Device Manager codes and symptoms, shows where to find them in Windows 10 and Windows 11, and maps each issue to the safest fix order.

That order matters because three similar-looking problems usually need different first moves: a device missing from the list, a device with a yellow warning icon, and Device Manager itself blinking or refusing to open. The icon tells you the device needs attention, but it is not the diagnosis. Device status appears in the Properties dialog box, on the General tab, in the Device status area.

How should you triage Device Manager problems first?

Start by capturing the exact symptom before you change anything: missing device, yellow warning icon, code-based error, normal-looking device that still fails, refresh loop, or Device Manager not opening. Then pull details from the Properties dialog, recent update history, and hidden-device view so your first fix fits the problem class instead of assuming every case starts with a driver update.

Collect the evidence before you change anything

Device Manager is the Windows utility for checking hardware status and managing drivers. In Windows 11 and Windows 10, the most useful device details are often the device name, its category, whether a yellow warning icon appears, and the status text shown in Properties.

  1. Open Device Manager. Press Windows + X and select Device Manager, or open Start, type Device Manager, and select the matching result. If Device Manager does not open, skip ahead to the section on blinking, refreshing, or not opening.
  2. Find the device entry. Expand the category where the hardware should appear, such as Network adapters, Sound, video and game controllers, Cameras, Bluetooth, or Mice and other pointing devices. If it is missing, open View and turn on hidden devices before you assume the hardware vanished.
  3. Open Properties. Right-click the device, choose Properties, then check the General tab and the Device status box at the bottom of that window. Microsoft says the device status appears there, and common guides point to the same location.
  4. Record exact details. Write down the device name, category, status text, and any code number shown on the General tab. Also note whether the Driver tab offers Roll Back Driver, which can point to a recent bad update.
  5. Check recent changes. Note whether the problem started after a Windows update, a driver install, docking the laptop, moving a USB device to a hub, or waking from sleep. Timing is often the fastest clue for separating driver faults from hardware or power issues.
  6. Check hidden presence. If the device appears only as hidden, that changes the diagnosis. Hidden entries often point to a disconnected device, stale device record, failed enumeration, or power and port issues rather than a pure driver problem.

Sort the symptom before you touch the driver

A yellow warning icon is only an attention flag. A missing device usually sends you first to ports, power, docking stations, hubs, firmware detection, or hidden devices. A code shown in Device status sends you to a code-specific path. A refresh loop or app failure shifts the first check toward system stability or unstable hardware enumeration.

Picture a laptop touchpad that stops working right after a Windows update, while Device Manager still shows the touchpad entry and the Driver tab offers Roll Back Driver. That pattern points to a driver path first. Change one variable: the touchpad entry is gone entirely, even under hidden devices. Now the first checks move toward BIOS settings, OEM packages, firmware, or hardware detection.

Decide whether the first branch is driver, hardware, or system-level

Driver-first cases usually have a visible device entry and a code that suggests configuration or loading trouble. Hardware-first cases often involve missing devices, repeated disconnect sounds, failure across multiple ports, or devices that disappear under load. System-level cases include Device Manager not opening, constant refreshing, or low-memory pressure that affects several devices at once.

Where do you find the error code in Device Manager?

You find the code in the device’s Properties dialog box, usually on the General tab in the Device status area. That is where Windows reports the plain-language status and code-based label. The Driver tab is for actions such as Update Driver, Roll Back Driver, and Uninstall device, it does not explain the root cause by itself.

Use the Properties window and Device status area

Microsoft says Device status errors appear in the Properties dialog box under the Device status area. If a common code is present, it may read as Code 1, Code 3, Code 10, Code 12, Code 19, Code 28, Code 31, or Code 43. Those codes apply to both Windows 11 and Windows 10.

The General tab answers, “What does Windows think is wrong?” The Driver tab answers, “What can be changed next?” Keeping those roles separate helps you avoid changing settings before you capture the status text.

Know what the Driver tab can and cannot tell you

The Driver tab shows the provider, version, date, and actions such as Update Driver, Roll Back Driver, and Uninstall device. It can confirm whether a recent driver change lines up with the failure. It cannot confirm a loose cable, a failing USB hub, a disabled camera shutter, or a device that firmware no longer detects.

Triage matrix

Symptom Likely cause First safe action What not to do Escalation trigger
Device missing from expected category Port, power, dock, hub, BIOS detection, disabled device, failed enumeration Show hidden devices, reconnect directly, restart, then scan for hardware changes Do not force random driver installs before confirming the device is detected Still absent after direct connection, restart, and OEM checks
Yellow warning icon Driver loading issue, resource conflict, registry/filter problem, hardware fault Open Properties and record the exact code and status text Do not treat the icon itself as the diagnosis Code persists after the correct code-specific path
Code 1, 28, or 31 Driver missing, incomplete, or not loading correctly Use Update Driver, then switch to the OEM package if Windows does not restore function Do not uninstall first if a recent rollback is available Driver installs cleanly but the code remains
Code 3 or 12 Low memory, resource pressure, or allocation conflict Check Task Manager Performance view and close applications to free memory Do not keep reinstalling drivers while system pressure is unresolved Resource errors return after restart with low app load
Code 10 or 43 Device failed to start, firmware issue, unstable driver, or hardware fault Remove recent changes, restart, try rollback or OEM driver, then reinstall device entry if needed Do not assume a generic driver package will fix firmware or hardware failure Repeated Code 43 or Code 10 after reinstall and direct connection
Code 19 Registry or filter-driver problem, often with storage or optical-device stacks Roll back recent software or driver additions and reinstall the device entry carefully Do not start with manual registry edits unless vendor guidance requires it Status returns after restart and clean reinstall
Device Manager blinking or refreshing Unstable hardware enumeration, failing USB device, driver crash, dock or hub fault Disconnect nonessential peripherals, undock, restart, and retest with direct connections Do not mass-update every driver during a refresh loop Refresh continues with only core devices attached
Device Manager not opening User-session issue, system corruption, heavy resource pressure, service failure Restart, open Task Manager with CTRL+ALT+DELETE, and check memory pressure Do not jump straight to device-specific uninstall steps Fails across restarts or in another user session

What does each common Device Manager code mean?

What does each common Device Manager code mean?
A Windows Device Manager window shows a driver properties dialog

These codes are most useful when you group them by cause: driver setup and loading problems, resource conflicts, and start failures that may point to firmware or hardware. Microsoft lists common code meanings, and one practical guide groups them the same way. That structure helps you pick the lowest-risk fix instead of treating every code like the same driver issue.

Codes 1, 28, and 31: driver missing, incomplete, or not loading properly

Code 1 means the device is not configured correctly. For Code 1, start in the device’s Driver tab, choose Update Driver, then let Windows search automatically for a better match before you move to a vendor package. Code 28 usually points to a missing driver, while Code 31 often means Windows cannot load the drivers required for the device. These are the cases where Update Driver is often the right starting move. (Microsoft Support)

If Windows does not find a working package, move to the manufacturer or OEM driver package, especially for laptop touchpads, Wi‑Fi adapters, Bluetooth radios, cameras, and audio devices. Those device classes often depend on vendor-specific components that a generic package may miss.

Codes 3 and 12: memory pressure and resource conflicts

Microsoft says Code 3 can mean low memory or other resources. For Code 3, Microsoft suggests closing applications to free memory, and it says to check Task Manager for memory and system resources. Code 12 usually points to resource conflicts, where Windows cannot allocate enough free resources to the device.

Open Task Manager through CTRL+ALT+DELETE if the desktop is unstable. Check the Performance view, then close heavy applications, restart, and retest. If Code 3 remains, Microsoft also says to uninstall the driver and restart if needed.

Codes 10 and 43: device failed to start or Windows stopped it

Code 10 usually means the device cannot start. Code 43 generally means Windows stopped the device because it reported a problem. These two codes often sit at the boundary between driver trouble and hardware trouble, so timing matters: recent updates point one way, repeated failures across ports or direct connections point the other.

Suppose a USB camera works through a dock one day, then starts showing Code 43 after a dock firmware update. First remove the dock from the chain and connect directly. If the code clears, the camera may be fine and the path between system and device is the issue.

Code 19: registry or filter-driver problems

Code 19 often points to registry configuration or filter-driver trouble. It can appear after software that hooks into a device class, such as disc utilities, security products, audio software, or device-management tools. Start by reversing the recent change and reinstalling the device entry cleanly before moving to deeper repair steps.

How do you fix missing devices and hidden devices?

How do you fix missing devices and hidden devices?
A Device Manager window appears beside large instructional text

Fix a missing device by proving whether Windows can still see it at all. First check the right category, then show hidden devices, then remove hubs, docks, and adapters from the path, and restart. If the device never appears, the first branch is detection, power, firmware, or hardware, not a blind driver update.

When the device is absent from its normal category

A missing Wi‑Fi adapter, camera, touchpad, or Bluetooth radio may be disabled in firmware, blocked by a hardware switch, hidden by a stale entry, or cut off by a dock or power state. External devices add another layer: the cable, the port, and the hub matter before any driver package does.

  1. Show hidden devices. If the device appears only when hidden items are shown, record that state first. A hidden entry suggests Windows has seen the device before, which is different from never detecting it at all.
  2. Remove connection variables. Disconnect USB hubs, docking stations, adapters, and extension cables. Reconnect the device directly to a known-good port and power source if it uses one.
  3. Restart and rescan. Restart Windows, reopen Device Manager, and use Scan for hardware changes. This rebuilds detection without immediately removing the existing driver entry.
  4. Check firmware controls. On laptops, confirm the camera, wireless adapter, or touchpad is not disabled by BIOS settings, a function key, or a vendor control utility. That is common when the device is missing entirely.

When hidden devices change the diagnosis

If the device is hidden and grayed out, Windows may be holding an old record for hardware that is disconnected or not currently enumerating. In that case, the safest next step is usually restart and rescan, followed by direct connection or OEM package checks. Updating a driver for a device Windows cannot currently enumerate may do nothing.

When ports, cables, docks, hubs, or power are the real issue

External audio interfaces, webcams, storage devices, and Bluetooth adapters often fail because the path is unstable, not because the driver is wrong. Laptop users also hit this with USB-C docks that carry video, audio, networking, and power on one chain. If several docked devices vanish together, suspect the dock or its driver set before blaming each device separately.

When should you update, roll back, or uninstall a driver?

Update Driver is the right first step when the device is present, identifiable, and showing a code that points to configuration or loading trouble. Roll Back Driver is safer after a recent bad update. Uninstall device is best when rebuilding the device entry makes sense, followed by restart and Scan for hardware changes.

Use Update Driver when the device is present and identifiable

Common guidance recommends Update Driver before uninstalling in most cases, and that fits codes like Code 1, Code 28, and many Code 31 cases. Open the device’s Properties, select the Driver tab, click Update Driver, and let Windows search automatically before you replace it with an OEM package. It is a lower-risk move when the device entry exists and Windows still knows what the hardware is.

Use Roll Back Driver after a recent bad update

If the device failed right after a driver update and the Roll Back Driver option is available on the Driver tab, use that path before uninstalling. It targets the most recent change directly and keeps the previous working package in place.

Use Uninstall device to rebuild the device entry cleanly

  1. Confirm the current status. Record the exact code and status text on the General tab before making changes. That gives you a reference if the code changes after reinstall.
  2. Uninstall the device. In Device Manager, choose Uninstall device for the affected entry. Use this when the device is present but the current instance may be corrupted or tied to a bad installation state.
  3. Restart Windows. Restart instead of only refreshing the list. A full restart gives Windows a clean chance to enumerate the hardware and reload the driver stack.
  4. Scan for hardware changes. Reopen Device Manager and scan for hardware changes if the device does not return on its own. This is the lowest-risk way to prompt rediscovery after restart.
  5. Switch to the OEM package. If Windows restores the device but the problem remains, install the manufacturer or OEM driver package. This matters most for touchpads, audio chipsets, Wi‑Fi, Bluetooth, and integrated cameras.

Why is Device Manager blinking, refreshing, or not opening?

When Device Manager blinks, constantly refreshes, or refuses to open, the first branch is usually system stability or unstable device detection rather than one simple driver fault. Start with restart, resource checks in Task Manager, and peripheral isolation. Then separate an app-level UI problem from a hardware enumeration loop caused by a bad device, hub, dock, or driver crash.

Refresh loops often point to unstable enumeration

A refresh loop usually means Windows keeps detecting and losing a device. USB devices, docks, Bluetooth radios, webcams, and failing storage bridges are common triggers. Disconnect nonessential peripherals, undock the system, and retest with only keyboard, mouse, display, and power connected.

A common first-timer mistake is updating the GPU, audio, Wi‑Fi, and chipset drivers all at once because Device Manager keeps redrawing. That adds variables fast. Isolate the unstable device first, especially if the refresh loop stops when a dock or hub is removed.

Check Task Manager and system pressure

Microsoft says to check Task Manager for memory and system resources when resource-related codes appear. That advice also helps when Device Manager itself is sluggish or unstable. Open Task Manager from CTRL+ALT+DELETE, use the Performance view, and check whether memory pressure is extreme or whether the system is generally unstable.

Separate UI failure from device failure

If Device Manager will not open at all, try a restart first. If it still fails, test whether other admin tools open normally and whether the issue appears in another user session. A failure isolated to one session points to profile or shell issues, a failure across the system points to broader Windows component or service trouble.

How do you tell whether the fault is driver or hardware?

Driver-related faults usually line up with a recent update, visible device entry, and repeatable code such as Code 1, 28, or 31. Hardware-related faults are more likely when the device disappears completely, fails across ports or systems, is missing in firmware, or keeps throwing Code 43 or start failures after clean reinstalls.

Signs that point to a driver problem

  • The device still appears in Device Manager under the expected category.
  • The problem started right after a Windows update or driver install.
  • Roll Back Driver is available and the timing matches the failure.
  • The device works intermittently without moving cables, ports, or power.
  • A vendor package is known to be required for full function, such as precision touchpad features, laptop hotkeys, or audio effects.

Signs that point to hardware, firmware, or connection failure

  • The device is missing entirely, even after restart and Scan for hardware changes.
  • The failure follows a specific port, hub, dock, or cable.
  • The device fails the same way across multiple ports or systems.
  • The hardware is disabled or absent in BIOS or firmware menus.
  • Code 43 or Code 10 returns after reinstall, rollback, and direct connection.

Device-specific notes for touchpad, Bluetooth, audio, Wi‑Fi, and camera

Touchpads often depend on OEM packages and hotkey services. Bluetooth problems may be radio, antenna, or power-management related, especially after sleep. Audio issues can come from vendor control layers as much as the base codec driver. Wi‑Fi adapters often need OEM packages after a major Windows update. Cameras can be blocked by privacy shutters, BIOS settings, or dock paths before drivers enter the picture.

What should you do when the first fixes fail?

If the first safe fix does not restore function, move one level deeper without stacking multiple destructive changes. Restart and rescan, use Windows troubleshooters and repair checks where relevant, then escalate to OEM support, BIOS or firmware updates, or replacement when repeat failures point away from software.

Restart, rescan, and use Windows troubleshooters

After uninstalling a device, always restart and scan for hardware changes rather than assuming the list will rebuild correctly on its own. For device-level faults, the Hardware and Devices troubleshooter is still commonly referenced as a Windows troubleshooting utility. It is not a cure-all, but it can surface basic configuration faults.

Escalate when repeated failure points away from software

If OEM drivers, rollback, reinstall, and direct connection do not change the status, it is time to escalate. Repeated Code 43, persistent Code 10, or a device that never reappears after restart and rescan often means firmware or hardware failure. At that point, check for BIOS or firmware updates from the device maker or system maker, then move toward service or replacement if detection still fails.

Keep reading

Frequently asked questions

How do I troubleshoot Device Manager?

Start with the symptom class, not the fix. Record the exact status from the device’s Properties dialog, note whether a yellow warning icon is present, check recent updates, and see whether the device appears under hidden devices. Then choose the branch: missing device, code error, refresh loop, normal-looking device that still fails, or Device Manager itself not opening.

How do I fix all Device Manager errors?

There is no single repair for every Device Manager error because the codes point to different causes, including driver, resource, registry, firmware, and hardware issues. The safe pattern is inspect status, remove recent changes, restart and rescan, use Update Driver when appropriate, then uninstall and reinstall only when the symptom and code support it.

Why is Device Manager not working?

Device Manager may fail because of user-session trouble, Windows component problems, heavy memory pressure, or an unstable device that keeps forcing refreshes. Restart first, then open Task Manager through CTRL+ALT+DELETE and check Performance. If the issue persists across restarts and another user session, treat it as a broader Windows problem rather than one device’s driver alone.

How do I find the error code in Device Manager?

Press Windows + X and open Device Manager, right-click the affected device, choose Properties, and read the General tab. The code and plain-language message appear in the Device status area. That is where Windows reports code-based status labels, while the Driver tab is where you change the driver by updating, rolling back, or uninstalling it.

What does Device Manager code 10 mean?

Code 10 usually means the device cannot start. It can come from a bad driver update, a vendor-specific package problem, firmware trouble, or a hardware fault. Start by checking whether the failure began after a recent change, then try rollback, restart, direct connection for external devices, and the OEM package before treating it as a hardware replacement case.

How do I fix Device Manager error code 43?

Code 43 means Windows stopped the device because it reported a problem, so start by removing recent changes and isolating the hardware path. Restart, connect the device directly instead of through a hub or dock, try rollback or the OEM driver, and reinstall the device entry if needed. Repeated Code 43 after that often points to firmware or hardware failure.