Device Manager Yellow Triangles: What the Error Code Numbers Actually Mean

You open Device Manager in Windows 11 and immediately see a yellow warning triangle beside one of your devices.

That symbol tells you something is wrong.

It does not tell you what is wrong.

The useful information is hidden one level deeper inside:

Device Manager > Device > Properties > General > Device status

That is where Windows gives you a numbered error code such as:

Code 10

Code 28

Code 31

Code 43

Those numbers matter because they describe completely different types of failure. Microsoft’s current Device Manager guidance still recommends reading the exact Device status code and troubleshooting that specific problem rather than simply reinstalling every driver you can find.

Yellow Triangle? Start Here

Before changing drivers or replacing hardware:

1. Open Device Manager.

2. Right-click the device showing the yellow triangle.

3. Select Properties.

4. Read the full message under Device status.

5. Record the Code number.

6. Open the Driver tab and note the provider, version and date.

7. If the problem began after a recent update, check whether Roll Back Driver is available.

8. If Windows calls it an Unknown device, open Details > Hardware Ids.

That short process gives you far more useful information than the warning triangle alone.

Device Manager Codes Are Not Windows Update Codes

This is worth making clear.

A Device Manager:

Code 43

is not the same kind of error as:

0x8007000E

or:

0x800F0922

and it is not the same thing as a blue-screen stop code.

Device Manager codes describe the state of a hardware device or its driver.

Always troubleshoot the code in the context in which Windows reports it.

Code 10 — This Device Cannot Start

A common Device Manager message is:

This device cannot start. (Code 10)

This means Windows loaded enough information to recognise the device, but the device or its driver could not initialise successfully. Microsoft continues to list Code 10 as one of the standard Device Manager error conditions.

Possible causes include:

damaged driver

incompatible driver

firmware issue

hardware fault

device not initialising correctly

USB or power problem

What to Try

Start with:

Restart Windows

Then:

check Windows Update

check the PC or device manufacturer’s driver

uninstall and redetect the device

roll back a recently changed driver

test external hardware on another port/computer where possible

Do not assume Code 10 means the hardware is dead.

It means Windows could not start it successfully.

Code 22 — The Device Is Disabled

Code 22 is usually straightforward.

Windows reports that the device is disabled.

This may have happened because:

somebody disabled it manually

software disabled it

configuration changed

Open Device Manager, right-click the device and choose:

Enable device

If it disables itself again or immediately produces another code, investigate further.

Code 28 — The Drivers for This Device Are Not Installed

Code 28 is one of the clearest Device Manager errors.

Microsoft defines it as:

The drivers for this device are not installed. (Code 28) and recommends reinstalling the device driver.

This often appears after:

fresh Windows installation

hardware upgrade

missing OEM driver package

device migration

Windows failing to identify specialised hardware

What to Do

Start with:

Settings > Windows Update

Then check:

Advanced options > Optional updates

where relevant.

If Windows still cannot find the driver, obtain it from the:

PC manufacturer

motherboard manufacturer

device manufacturer

For a business laptop, I would normally start with the computer manufacturer’s support site.

Never Download Drivers From Random “Driver Download” Sites

This deserves a strong warning.

If you search a Hardware ID such as:

PCI\VEN_8086&DEV_1234

you may find dozens of websites offering a driver download.

Do not assume they are trustworthy.

Use the Hardware ID to identify the hardware.

Then obtain the driver from a reputable source such as:

Dell

HP

Lenovo

Microsoft

Intel

AMD

NVIDIA

Realtek

the actual hardware vendor

Third-party driver-download sites can provide:

outdated drivers

modified packages

unwanted software

incorrect hardware matches

The safest driver is not necessarily the first result in Google.

Code 31 — Windows Cannot Load the Required Driver

Code 31 means Windows cannot load the drivers needed for that particular device.

A typical message is:

This device is not working properly because Windows cannot load the drivers required for this device. (Code 31).

Possible causes include:

incompatible driver

damaged driver

failed driver update

device configuration problem

software conflict

What to Try

Check:

Driver > Roll Back Driver

if the problem began immediately after an update.

Otherwise:

1. Uninstall the device.

2. Restart Windows.

3. Install the approved driver.

4. Recheck Device Manager.

If the same device repeatedly returns with Code 31, investigate firmware, compatibility and hardware rather than endlessly reinstalling the same package.

Code 38 — Previous Driver Instance Still Loaded

Code 38 can appear when Windows says a previous version of the driver is still held in memory.

Microsoft’s current Device Manager guidance recommends simply restarting the computer for this condition.

This is a good example of why reading the error number matters.

You do not need an elaborate driver-removal procedure if Windows is simply waiting for the previous driver instance to unload.

Code 39 — Driver May Be Missing or Corrupted

Code 39 typically indicates Windows cannot load the driver and that it may be:

corrupted

missing

otherwise unusable

Microsoft recommends reinstalling the device driver for this condition.

Again, start with the approved manufacturer driver rather than a generic third-party driver installer.

Code 43 — Windows Has Stopped This Device

Code 43 deserves special attention because people frequently misinterpret it.

Windows may say:

Windows has stopped this device because it has reported problems. (Code 43)

This does not automatically mean the hardware is dead.

It means Windows has received a failure indication from the device or its driver.

That can result from:

bad driver

firmware problem

USB communication issue

power problem

hardware failure

graphics-card fault

docking issue

Microsoft’s current graphics troubleshooting for Code 43 includes checking for driver updates, using Roll Back Driver where appropriate, and uninstalling/reinstalling the device before concluding the hardware itself has failed.

Code 43 Troubleshooting Order

I would use:

1. Restart Windows.

2. Check whether the problem started after a driver/Windows update.

3. Try Roll Back Driver if appropriate.

4. Update the approved manufacturer driver.

5. Uninstall and redetect the device.

6. For USB hardware, change cable/port.

7. Bypass hubs or docks.

8. Test the device on another computer where possible.

9. Check manufacturer diagnostics.

10. Suspect hardware only when the evidence genuinely points there.

If a GPU works in another machine, Code 43 probably deserves more driver or platform investigation.

If it fails consistently across known-good systems, hardware becomes much more likely.

Code 45 — Device Is Not Connected

Code 45 normally appears when Windows remembers a device but it is no longer connected.

This is common with:

USB devices

removable hardware

docks

Bluetooth devices

It does not normally mean Windows is broken.

If the device is supposed to be connected, check:

cable

USB port

dock

power

Bluetooth connection

hardware detection

If it is no longer in use, Code 45 may simply describe reality.

Code 48 — Windows Has Blocked the Driver

Code 48 can appear when Windows prevents a driver from loading.

This deserves caution.

A blocked driver may be:

incompatible

known to cause problems

unsafe

no longer supported

Do not immediately disable Windows security features to force the driver to load.

Instead:

1. Identify the hardware.

2. Check the manufacturer for a newer driver.

3. Check whether the device is still supported.

4. Replace obsolete hardware if necessary.

Running an old driver by weakening Windows security can create a bigger problem than the device itself.

Code 51 — Waiting for Another Device

Code 51 means the affected hardware is waiting for another device or dependency to start.

This can happen with device chains involving:

USB controllers

docking stations

buses

parent/child hardware relationships

Look for another device showing an error.

Fixing the parent or dependent component may resolve Code 51 automatically.

Code 52 — Windows Cannot Verify the Driver Signature

Code 52 tells you Windows cannot verify the digital signature of the driver.

Possible reasons include:

modified driver

corrupted driver package

obsolete software

unsigned driver

driver no longer trusted

Do not immediately disable Windows driver-signature enforcement as a permanent fix.

For an ordinary business PC, the correct response is normally to obtain a properly signed current driver.

Unknown Device? Use Hardware IDs

One of the most useful Device Manager techniques is identifying an Unknown device.

Right-click it and choose:

Properties > Details

Then select:

Hardware Ids

You might see something such as:

PCI\VEN_8086&DEV_...

or:

USB\VID_1234&PID_5678

These identifiers can tell you:

manufacturer

device family

exact hardware model

This is much better than blindly trying drivers.

For PCI hardware:

VEN usually identifies the vendor.

DEV identifies the device.

For USB:

VID identifies the vendor.

PID identifies the product.

Use those values to identify the hardware, then obtain the correct driver from the manufacturer.

Check the Events Tab

Another useful but often ignored area is:

Device Properties > Events

This can show events such as:

device configured

device started

device not migrated

driver installed

driver service added

device requires further installation

The timestamps are particularly helpful.

If everything worked until:

14 August 2026

and the device was reconfigured at:

09:32 on 14 August 2026

you have something concrete to investigate.

Updating the Driver Is Not Always the Answer

This is one of the main points I’d strengthen.

When someone sees a yellow triangle, the instinct is:

Update driver.

But sometimes the newest driver is what created the problem.

Suppose:

Wi-Fi worked yesterday

Windows Update installed a network driver overnight

today the adapter shows Code 10

In that case, the more sensible first check may be:

Properties > Driver > Roll Back Driver

rather than searching the internet for another new driver.

Microsoft itself includes rollback as a valid troubleshooting step for device errors such as Code 43.

Use the Manufacturer Driver on Business PCs

For business laptops, I would normally prefer the driver approved by:

Dell

HP

Lenovo

Microsoft Surface

other system manufacturer

before jumping to a generic component driver.

The OEM may have validated the package against:

BIOS

chipset

dock firmware

power management

specific laptop hardware

That can make a manufacturer-approved driver more reliable than a newer generic release.

Don't Use “Update Driver” as Proof Windows Found the Best Driver

Device Manager's:

Update driver > Search automatically for drivers

can be useful.

But if Windows tells you:

The best drivers for your device are already installed

that does not necessarily prove the current driver is the latest driver available from the manufacturer.

Check the vendor when troubleshooting a persistent fault.

External Hardware? Test It Somewhere Else

If the error involves:

USB drive

printer

webcam

USB Ethernet adapter

external audio device

dock

test the hardware on another computer where practical.

That gives you excellent evidence.

Works elsewhere

Investigate:

PC driver

USB port

Windows configuration

firmware

Fails everywhere

The hardware or cable becomes much more suspicious.

When Should You Suspect Hardware Failure?

Hardware becomes more likely when:

the device fails across multiple computers

different cables/ports make no difference

manufacturer diagnostics fail

Code 43 returns after clean driver reinstall

the device repeatedly disconnects

physical symptoms are present

another identical known-good device works normally

But a yellow triangle by itself is not proof of failed hardware.

Avoid Generic Driver-Updater Applications

I would not use utilities that promise:

Update all your drivers automatically

on business PCs.

They can:

install wrong drivers

replace manufacturer-customised packages

install unstable versions

create additional software clutter

make troubleshooting harder

Windows Update, OEM support channels and the actual hardware manufacturer should normally cover what you need.

The Quick Code Reference

Code    Meaning    Good first action

10    Device cannot start    Restart, driver/firmware check
22    Device disabled    Enable device
28    Driver not installed    Install correct driver
31    Windows cannot load required driver    Roll back/reinstall driver
38    Previous driver instance still loaded    Restart
39    Driver missing/corrupted    Reinstall driver
43    Device/driver reported failure    Driver, connection, firmware, hardware checks
45    Device not connected    Check physical connection
48    Driver blocked    Find supported signed driver
51    Waiting for another device    Check dependent devices
52    Driver signature cannot be verified    Install trusted signed driver

Microsoft’s full Device Manager error reference covers many additional codes beyond those listed here.

The Best Troubleshooting Order

When you see a yellow triangle in Windows 11:

1. Read the exact Device status message.

2. Record the Code number.

3. Check driver provider/version/date.

4. Ask whether the problem started after an update.

5. Consider Roll Back Driver where appropriate.

6. Restart if the code suggests a temporary driver state.

7. Install the approved manufacturer driver.

8. Use Hardware IDs for unknown devices.

9. Check the Events tab.

10. Test external hardware with another cable/port/computer.

11. Update BIOS/firmware where relevant.

12. Suspect hardware only after the software, connection and driver evidence supports that conclusion.

That is far more reliable than:

Yellow triangle = reinstall every driver.

How Hamilton Group Can Help

A Device Manager warning can be something as simple as a disabled device or as serious as failing hardware.

Hamilton Group can help diagnose:

Windows 11 Device Manager errors

Code 10

Code 28

Code 31

Code 43

Code 52

unknown devices

driver problems

USB and docking issues

network adapter problems

graphics-driver faults

hardware diagnostics

For business environments, we can also identify whether a problem affects one device or is being caused by a common Windows update, BIOS version, driver deployment or hardware model across the estate.

Visit hgmssp.com or call 0330 043 0069 to speak with Hamilton Group.