Device Manager Yellow Triangles: Reading the Error Code Numbers

You open Device Manager and find a yellow warning triangle beside your graphics card, network adapter, Bluetooth radio, USB controller or another piece of hardware.

The affected device may have stopped working entirely—or it may appear to operate normally while Windows quietly reports a configuration problem.

The yellow triangle is not the diagnosis.

It simply tells you that Windows has recorded a problem against that device. The useful information is inside the device’s Properties window, where Device Manager displays a numbered status code and a more detailed message.

Examples include:

This device cannot start. (Code 10)

The drivers for this device are not installed. (Code 28)

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

Those numbers describe very different conditions. One might require only a restart, another may need the correct manufacturer driver, while another can indicate a physical hardware failure.

The right approach is to record the exact code and investigate what it means before uninstalling drivers, editing the Registry or replacing equipment.

What the Yellow Triangle Means

Device Manager displays a yellow triangle with an exclamation mark when Windows has assigned a problem code to a device. Opening the device’s Properties shows the code and its accompanying message in the Device status box. 

A warning can relate to:

• Missing or unsuitable drivers
• Drivers that fail to start
• Disabled hardware
• Firmware configuration
• Insufficient device resources
• A disconnected peripheral
• A driver blocked for compatibility or security reasons
• A device reporting an internal failure
• A dependency on another device that has not started
• A temporary restart requirement

A yellow triangle does not automatically mean the physical hardware is broken.

It also does not prove that downloading the newest available driver will solve the problem.

How to Find the Error Code

Right-click Start and select:

Device Manager

Find the device showing the yellow warning symbol.

Then:

1. Right-click the device.
2. Select Properties.
3. Open the General tab.
4. Read the complete Device status message.
5. Record the code number.

Microsoft identifies the Device status area as the correct place to find Device Manager’s problem code. 

Take a screenshot before changing anything.

A useful support record includes:

Device: Intel Wireless Bluetooth

Category: Bluetooth

Device status: This device cannot start. (Code 10)

Driver provider: Intel

Driver version: 24.x.x.x

Problem began: After Windows update

Computer model: Dell Latitude 7450

This is much more useful than reporting:

Bluetooth has a yellow triangle.

Device Manager Codes Are Not Windows Update Codes

A Device Manager code such as:

Code 10

is not the same as a Windows Update error such as:

0x800f0922

It is also different from:

• A blue-screen stop code
• An application error
• An HTTP status code
• An Event Viewer ID
• A printer error displayed on the printer itself

Always interpret the number in the context in which Windows displayed it.

Check More Than the General Tab

A device’s Properties window can contain several useful tabs.

Driver

The Driver tab may show:

• Driver provider
• Driver date
• Driver version
• Digital signer
• Update Driver
• Roll Back Driver
• Disable Device
• Uninstall Device

Details

The Details tab can display identification and configuration information used when diagnosing driver problems. Hardware IDs are particularly useful because Windows uses them to match a physical device with compatible driver packages. 

Select:

Property > Hardware Ids

You may see a value such as:

PCI\VEN_8086&DEV_7A70&SUBSYS_...

or:

USB\VID_0BDA&PID_4853

The identifier can help establish the exact component when Device Manager displays only:

Unknown device

Do not publish complete device reports publicly without reviewing them. They can contain computer, device and organisational information.

Events

The Events tab can reveal:

• When the device was configured
• Whether installation was requested
• Whether a driver service was added
• Whether the device failed to start
• Whether Windows migrated the device during an upgrade

The General, Driver, Details and Events tabs can all provide useful diagnostic information. 

Common Device Manager Codes at a Glance

These codes are separate internal Device Manager problem states; Microsoft maintains the underlying list and recommended resolutions for Windows. 

Code 1: Device Is Not Configured Correctly

The full message is:

This device is not configured correctly. (Code 1)

Microsoft says this normally means that no driver is installed or the installed driver is configured incorrectly. The recommended first action is to update the driver. 

This can occur after:

• A clean Windows installation
• Replacing a motherboard or expansion card
• Connecting specialist equipment
• Removing manufacturer software
• A failed driver installation
• Installing the wrong architecture or model package

What to do

1. Check Windows Update.
2. Review optional driver updates.
3. Identify the computer and device model.
4. Download the correct driver from the official manufacturer.
5. Restart and recheck Device Manager.

Do not select a similarly named driver intended for another hardware revision.

Code 3: Driver Corruption or Low Resources

The full message may say:

The driver for this device might be corrupted, or your system may be running low on memory or other resources. (Code 3)

Microsoft identifies two broad possibilities: a corrupted driver or insufficient memory and system resources. Its recommended actions include closing applications, checking memory availability and reinstalling the driver. 

Check Task Manager

Press:

Ctrl + Shift + Esc

Review:

• Memory usage
• Available memory
• Committed memory
• CPU use
• The process consuming the most resources

If Windows has virtually no available memory, restart and test the device before assuming the driver is faulty.

If Code 3 returns while system resources are normal, reinstall the correct driver.

Code 10: This Device Cannot Start

Code 10 is one of the most common—and least specific—Device Manager errors.

The full message is:

This device cannot start. (Code 10)

It means Windows found the device and selected a driver, but the device did not start successfully. Microsoft’s primary recommendation is to update the driver. 

Possible causes include:

• Incorrect driver
• Damaged driver
• Driver and firmware incompatibility
• A device stuck after sleep
• Insufficient power
• USB or docking problems
• BIOS configuration
• Hardware failure

A sensible Code 10 sequence

1. Restart Windows.
2. Disconnect and reconnect external hardware.
3. Try another cable or port.
4. Install Windows updates.
5. Install the exact manufacturer driver.
6. Roll back a recently changed driver.
7. Uninstall and redetect the device.
8. Update firmware or BIOS where appropriate.
9. Test the device on another computer.
10. Run manufacturer diagnostics.

A Code 10 on a USB headset is approached differently from Code 10 on an internal storage controller. The code gives you the state; the device type and recent history give you the context.

Code 12: Not Enough Free Hardware Resources

The full message is:

This device cannot find enough free resources that it can use. (Code 12)

This does not normally mean that your SSD is full or that Windows needs more RAM.

It relates to hardware resources such as:

• I/O ranges
• Interrupts
• Memory-mapped resources
• Direct Memory Access channels

Microsoft says Code 12 can occur when devices have conflicting resource assignments or when the system firmware has not allocated sufficient resources to the device. 

Possible triggers include:

• Installing a PCIe expansion card
• Adding several high-bandwidth devices
• BIOS or UEFI bugs
• Outdated chipset firmware
• Docking stations
• Older specialist hardware
• Platform-resource allocation problems

What to do

• Install current chipset drivers.
• Update BIOS or UEFI through the computer manufacturer.
• Remove recently added hardware temporarily.
• Test the device in another expansion slot.
• Disconnect unnecessary docks and peripherals.
• Restore firmware defaults only after recording existing settings.
• Contact the system or motherboard manufacturer.

Do not randomly disable essential motherboard devices to free resources.

Code 14: Restart Required

The message is:

This device cannot work properly until you restart your computer. (Code 14)

The resolution is exactly what it says: restart Windows. 

Use:

Start > Power > Restart

Do not only close the lid or use Shut down.

If Code 14 remains after a proper restart, the installation may not be completing correctly. Check:

• Pending Windows updates
• Driver installation failures
• Insufficient system-drive space
• Security software interference
• The device’s Events tab

Code 18: Reinstall the Drivers

The message is:

Reinstall the drivers for this device. (Code 18)

Microsoft recommends either updating the driver or uninstalling the device and scanning for hardware changes so Windows can install it again. 

Before uninstalling it, download the correct manufacturer package—particularly if the device provides:

• Network access
• Storage
• Keyboard or mouse control
• Display output
• A specialist business function

You do not want to remove the only working network driver and then discover that the replacement package is unavailable.

Code 19: Damaged Registry Configuration

The message is:

Windows cannot start this hardware device because its configuration information

(in the registry) is incomplete or damaged. (Code 19)

Microsoft says this can occur when the device’s service configuration is incomplete, conflicting or damaged, and recommends uninstalling and reinstalling the driver. 

Code 19 is commonly associated with devices whose driver stack includes additional filter software, such as:

• Optical drives
• Audio devices
• Security products
• Backup software
• Disc-writing software
• Specialist USB equipment

Do not immediately edit UpperFilters or LowerFilters

Many internet guides recommend deleting Registry filter entries.

Those values may belong to legitimate:

• Security software
• Backup applications
• Encryption tools
• Storage utilities
• Hardware-control software

Removing the wrong filter can disable other devices or prevent Windows from starting.

Start by:

1. Recording the device and code.
2. Uninstalling recently added device-related software.
3. Reinstalling the official driver.
4. Using System Restore when the problem began after a clear configuration change.
5. Escalating Registry work to an experienced technician.

Code 22: Device Is Disabled

The message is:

This device is disabled. (Code 22)

Microsoft says this code normally means the device was disabled through Device Manager. The resolution is to enable it again. 

Right-click the device and select:

Enable device

Before enabling it, consider why it was disabled.

It may have been deliberately turned off because:

• It conflicts with another adapter.
• A company policy requires it.
• An external alternative is in use.
• The device is faulty.
• A technician was isolating a problem.

On a business-managed computer, confirm the intended configuration first.

Code 24: Device Is Absent or Not Working Properly

The message is:

This device is not present, is not working properly, or does not have all its

drivers installed. (Code 24)

Microsoft says the condition may reflect incorrect installation, hardware failure, a missing driver or a device that has been prepared for removal. 

Check:

• Is the USB device physically connected?
• Is the expansion card properly seated?
• Does the device receive power?
• Does another cable work?
• Is the device visible in BIOS or UEFI?
• Does another computer detect it?
• Is it merely an old hidden entry?

If Code 24 belongs to an internal device that repeatedly disappears, hardware assessment may be required.

Code 28: Drivers Are Not Installed

The message is:

The drivers for this device are not installed. (Code 28)

This generally means Windows has detected hardware but cannot find a suitable installed driver. Microsoft recommends uninstalling the device, scanning for hardware changes and providing a manufacturer driver when Windows asks for one. 

Common examples include:

• Network Controller
• PCI Device
• SM Bus Controller
• Base System Device
• Unknown USB Device
• Multimedia Controller
• Fingerprint sensor

Use the Hardware ID

Open:

Properties > Details > Hardware Ids

Copy the first value and use it to identify the component through:

• The computer manufacturer’s support page
• The motherboard manufacturer
• Your organisation’s hardware inventory
• The component manufacturer

Avoid random driver-download websites.

Microsoft advises using Windows Update or the official manufacturer service and avoiding other driver-download sources. 

Code 29: Disabled in Firmware

The message is:

This device is disabled because the firmware of the device did not give it the

required resources. (Code 29)

Microsoft recommends enabling the device through the computer’s BIOS or firmware settings. 

Settings may be named:

• Integrated Devices
• Onboard Devices
• Wireless Device Enable
• Audio Controller
• Camera
• Thunderbolt
• USB Configuration
• PCIe Slot
• I/O Port Access

Use the computer manufacturer’s instructions.

Do not change unrelated firmware options such as:

• Storage controller mode
• Secure Boot
• TPM configuration
• UEFI or Legacy boot mode
• RAID settings

An incorrect storage setting can prevent Windows from booting.

Code 31: Windows Cannot Load the Required Drivers

The message is:

This device is not working properly because Windows cannot load the drivers

required for this device. (Code 31)

Microsoft recommends updating or reinstalling the driver. 

Code 31 may occur when:

• The driver is incompatible with the current Windows build.
• A supporting chipset or bus driver is missing.
• Windows selected a generic but unsuitable package.
• Security software blocks part of the driver stack.
• A feature update failed to migrate the device properly.
• A virtual or filter driver is damaged.

Install packages in the manufacturer’s recommended order.

For a laptop, that may mean:

1. BIOS or firmware
2. Chipset
3. Serial I/O or platform drivers
4. Device-specific driver
5. Manufacturer control software

Code 32: Driver Service Has Been Disabled

The message is:

A driver (service) for this device has been disabled.

An alternate driver may be providing this functionality. (Code 32)

Microsoft says the driver’s start configuration is disabled and recommends reinstalling the device driver. 

This can occur after:

• Registry cleaning
• “Debloating” scripts
• Security-software changes
• Manual service modifications
• Driver-package replacement
• Manufacturer-software removal

Do not simply change an unknown driver service to Automatic through the Registry or Services console.

Drivers do not all use ordinary service-start behaviour, and an incorrect setting can destabilise Windows.

Codes 37, 39 and 40: Driver Loading Failures

These codes point towards different stages of driver failure.

Code 37

Windows cannot initialize the device driver for this hardware. (Code 37)

Microsoft says the driver returned a failure while initialising and recommends reinstalling it. 

Code 39

Windows cannot load the device driver for this hardware.

The driver may be corrupted or missing. (Code 39)

Microsoft again recommends reinstalling the driver. 

Code 40

Windows cannot access this hardware because its service key information in the

registry is missing or recorded incorrectly. (Code 40)

Microsoft identifies invalid driver-service Registry information and recommends driver reinstallation. 

For all three:

1. Download the official driver.
2. Record the current driver version.
3. Uninstall the affected device.
4. Restart.
5. Install the manufacturer package.
6. Restart again.
7. Check Device Manager.

If several unrelated devices show similar codes, investigate:

• Windows corruption
• Security products
• Failed Windows servicing
• Storage errors
• Registry-modification utilities

Code 38: Previous Driver Still in Memory

The message is:

Windows cannot load the device driver for this hardware because a previous

instance of the device driver is still in memory. (Code 38)

Microsoft’s recommended resolution is to restart the computer. 

If it returns after restarting:

• Update the driver.
• Disconnect and reconnect the device.
• Check for duplicate device software.
• Review filter drivers and manufacturer utilities.
• Test a clean boot.

Code 38 recurring after every restart suggests more than a temporary stale driver instance.

Code 41: Driver Loaded but Hardware Not Found

The message is:

Windows successfully loaded the device driver for this hardware but cannot find

the hardware device. (Code 41)

Microsoft says Windows has loaded a driver but cannot locate the corresponding device. 

Check:

• Cable and power
• USB port
• Internal card seating
• Firmware detection
• Whether the device has been removed
• Whether the wrong legacy driver was installed

A driver cannot make physically absent hardware appear.

Code 42: Duplicate Device

The message is:

Windows cannot load the device driver for this hardware because there is a

duplicate device already running in the system. (Code 42)

Microsoft says this can occur when Windows or a bus driver has created duplicate device instances, or when a device is discovered in a new location before the old instance is removed. The recommended first step is restarting Windows. 

If it returns:

1. Disconnect the device.
2. Show hidden devices.
3. Record duplicate entries.
4. Remove only the obsolete non-present instance.
5. Restart.
6. Reconnect the device directly rather than through a hub.

Do not remove every grey device entry indiscriminately.

Code 43: The Device Reported a Problem

The message is:

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

Code 43 means a driver controlling the device informed Windows that the device failed in some way. Microsoft advises reinstalling the driver and consulting the device manufacturer when basic troubleshooting does not resolve it. 

Code 43 is common with:

• Graphics cards
• USB devices
• Bluetooth adapters
• Webcams
• External storage
• Docking stations

It can be caused by:

• A driver fault
• Firmware failure
• Insufficient or unstable power
• A damaged USB cable
• Overheating
• Hardware failure
• The device entering an invalid state

Code 43 does not automatically mean the device is dead

Try:

1. Restarting Windows.
2. Completely powering the computer down.
3. Reconnecting external devices.
4. Changing cable or port.
5. Removing hubs and docks.
6. Rolling back a recent driver.
7. Installing the manufacturer driver.
8. Updating firmware.
9. Testing the device elsewhere.
10. Running hardware diagnostics.

When a graphics card repeatedly reports Code 43 across a clean driver installation and another operating environment, physical failure becomes more likely.

Code 45: Hardware Is Not Connected

The message is:

Currently, this hardware device is not connected to the computer. (Code 45)

Microsoft states that Code 45 is simply used to indicate a previously connected device is no longer present. It clears automatically when the device is reconnected. 

A faded hidden entry for an old:

• USB drive
• Phone
• Dock
• Bluetooth accessory
• Printer
• External network adapter

may therefore be completely normal.

Code 45 becomes relevant when it belongs to an internal device that should still be present, such as:

• Bluetooth radio
• Webcam
• Internal Wi-Fi adapter
• Fingerprint reader
• Storage controller

In that situation, check firmware, platform drivers and hardware detection.

Code 47: Prepared for Safe Removal

The message is:

Windows cannot use this hardware device because it has been prepared for safe

removal, but it has not been removed from the computer. (Code 47)

Disconnect the device and reconnect it. Restart Windows if necessary. 

This is commonly associated with:

• USB storage
• Docking devices
• Removable adapters
• Card readers

Do not force a removable drive back online while it is writing data.

Code 48: Driver Blocked

The message is:

The software for this device has been blocked from starting because it is known

to have problems with Windows. Contact the hardware vendor for a new driver.

(Code 48)

This is not an invitation to bypass Windows driver protection.

Microsoft recommends obtaining a corrected or updated driver from the hardware manufacturer. 

Do not:

• Disable driver-signature enforcement permanently
• Turn off security features
• Install a driver from an unknown archive
• Modify the driver package manually
• Force-install an incompatible version

A blocked driver may contain a compatibility or security defect that Windows is intentionally preventing from loading.

Code 51: Waiting for Another Device

The message is:

This device is currently waiting on another device or set of devices to start.

(Code 51)

Microsoft advises examining other failed devices on which the affected device may depend. 

For example, a device may depend on:

• A USB controller
• PCI bus
• Chipset component
• Audio controller
• Bluetooth USB interface
• Thunderbolt controller
• Virtualisation or filter driver

Do not focus only on the device showing Code 51. Look higher in the device tree for another yellow triangle.

Code 52: Driver Signature Cannot Be Verified

The message is:

Windows cannot verify the digital signature for the drivers required for this

device. (Code 52)

Microsoft says the driver may be unsigned or corrupted and recommends obtaining the latest compatible driver from the hardware manufacturer. 

A valid digital signature helps Windows verify:

• The publisher
• The integrity of the package
• Whether it has been altered since signing

Code 52 may appear after:

• Installing an obsolete driver
• Using a package intended for an older Windows release
• Driver-file corruption
• Attempting to install unofficial software
• Security-policy changes

Do not weaken Windows security to make the warning disappear.

Code 54: Device Is Being Reset

Code 54 means the device has failed and Windows is attempting a reset.

Microsoft describes it as an intermittent state related to an ACPI device reset and recommends restarting when the device remains stuck in that condition. 

If it occurs frequently:

• Update BIOS or UEFI.
• Update chipset and device drivers.
• Check sleep and wake behaviour.
• Disconnect docks and external hardware.
• Test power-management settings.
• Run manufacturer diagnostics.

A repeated Code 54 after sleep may indicate a firmware or power-state problem.

Show Hidden Devices Carefully

In Device Manager, select:

View > Show hidden devices

Windows may then display devices that are hidden by default, including non-present or “phantom” devices that were previously attached but are no longer connected. 

Faded devices are not automatically faulty.

They may represent:

• A USB device currently unplugged
• An old monitor
• A former docking station
• A Bluetooth accessory
• A printer not currently available
• A device detected in another physical port

Do not remove every faded device as a general cleanup exercise.

Remove a hidden device only when:

• You have positively identified it.
• It is obsolete or duplicated.
• It is contributing to a documented installation problem.
• You have a recovery plan.

A Safe Driver Repair Sequence

When the code points towards a driver problem, use this order.

1. Restart Windows

Some codes exist only because a driver replacement, removal or reset has not completed.

2. Check Physical Connections

For external hardware:

• Reconnect the cable.
• Try another cable.
• Try another port.
• Remove USB hubs.
• Connect the correct power supply.
• Test the device elsewhere.

3. Install Windows Updates

Open:

Settings > Windows Update

Select Check for updates.

Then check:

Advanced options > Optional updates > Driver updates

Windows 11 installs recommended drivers through Windows Update and presents some additional packages as optional updates. 

4. Use the Exact Manufacturer Driver

For laptops and branded desktops, start with the computer manufacturer for:

• Chipset
• Bluetooth
• Wi-Fi
• Audio
• Touchpad
• Camera
• Storage
• USB-C
• Thunderbolt
• Firmware

Microsoft advises downloading drivers only from the device manufacturer’s official service when Windows cannot locate a suitable package. 

5. Roll Back a Recent Driver

When the triangle appeared after an update:

1. Open the device’s Properties.
2. Select Driver.
3. Select Roll Back Driver.
4. Choose a reason.
5. Restart.

Microsoft documents rollback as the supported response when a device stopped working after a recent driver or Windows update. 

6. Reinstall the Device

Before beginning, download the replacement driver.

Then:

1. Right-click the device.
2. Select Uninstall device.
3. Confirm.
4. Restart Windows.
5. Allow Windows to redetect it.
6. Install the manufacturer package if required.

Windows attempts to reinstall the device driver after restart. 

Be cautious with any option that removes the driver package as well as the device. Microsoft notes that deleting the package requires administrative rights and can prevent Windows from reusing it automatically. 

When the Driver Is Not the Real Problem

The triangle may remain even after the correct driver has been installed.

Hardware becomes more likely when:

• The device disappears and returns repeatedly.
• It is absent from BIOS or firmware.
• It fails on another computer.
• Manufacturer diagnostics report an error.
• Code 43 returns after a clean driver installation.
• The device overheats.
• A USB device is not detected through any cable or port.
• The problem followed liquid, impact or electrical damage.
• Several functions on one physical card fail together.
• The computer freezes when the device is enabled.

Examples include:

• A failing Wi-Fi/Bluetooth module
• Damaged USB controller
• Defective graphics card
• Failing storage device
• Faulty docking station
• Damaged motherboard
• Insufficient power supply
• Loose internal connection

A driver reinstall cannot repair electrically failed hardware.

Check BIOS, Firmware and Platform Drivers

Some Device Manager problems originate below Windows.

Review official updates for:

• BIOS or UEFI
• Embedded controller
• Chipset
• Intel Management Engine
• AMD platform components
• USB-C or Thunderbolt
• Docking-station firmware
• SSD firmware

Firmware-related codes such as 12, 29, 33 and 35 particularly warrant checking the computer or motherboard manufacturer. Microsoft specifically associates several of these codes with firmware resource or configuration problems. 

Before updating firmware:

• Connect reliable mains power.
• Save the BitLocker recovery key.
• Confirm the exact computer model.
• Close applications.
• Do not interrupt the update.

Check Reliability Monitor and Event Viewer

Press Windows key + R, enter:

perfmon /rel

Review failures at the time the yellow triangle appeared.

Then open Event Viewer and check:

Windows Logs > System

Look for repeating events involving:

• Kernel-PnP
• Driver Frameworks
• USB
• Display
• Disk
• Bluetooth
• Network adapters
• Device setup
• The manufacturer driver

Do not assume every warning is related. Focus on events matching the time and affected device.

When Several Devices Have Yellow Triangles

Multiple warnings appearing simultaneously can indicate a shared underlying problem.

Possible causes include:

• Missing chipset drivers
• Failed Windows feature upgrade
• Damaged USB or PCI controller
• BIOS reset
• Platform firmware issue
• Corrupt Windows driver store
• Security software blocking drivers
• Motherboard failure

Look for a common parent.

For example, several USB devices may fail because the USB controller is faulty—not because every connected peripheral broke at once.

Likewise, Bluetooth may depend on an internal USB interface, while audio, camera and sensors may share platform or serial-I/O drivers.

Do Not Use Generic Driver-Updater Tools

A program claiming that twenty drivers are “critically outdated” does not know more about your exact business laptop than its manufacturer necessarily does.

Generic tools can:

• Replace customised drivers
• Install the wrong hardware revision
• Update several components simultaneously
• Make rollback difficult
• Bundle unwanted software
• Misinterpret old-looking driver dates
• Introduce new Device Manager codes

Use:

1. Windows Update
2. The exact computer manufacturer
3. The component manufacturer where there is a clear reason

Common Mistakes to Avoid

Treating every yellow triangle as hardware failure

Many codes describe driver, configuration or restart problems.

Updating every driver at once

When the problem worsens, you will not know which package caused it.

Deleting hidden devices indiscriminately

Many are simply disconnected peripherals.

Downloading by filename alone

A driver filename does not prove compatibility with the exact hardware ID.

Editing the Registry before reinstalling the driver

Registry filters and service entries may belong to important software.

Disabling driver-signature enforcement

Code 52 should be resolved with a legitimate signed driver.

Changing unrelated BIOS settings

Storage or security changes can make the computer unbootable.

Removing a network driver without downloading its replacement

You may lose the connection needed to obtain the driver.

Assuming “The best drivers are already installed” means no other driver exists

Device Manager reports only what it selected from the sources it checked. The manufacturer may provide a newer or model-specific package. 

Ignoring the exact code

Code 22 needs a different response from Code 43 or Code 52.

A Practical Yellow-Triangle Checklist

When Device Manager shows a warning:

1. Open the device’s Properties.
2. Record the full Device status message.
3. Record the code number.
4. Take a screenshot.
5. Record the driver provider and version.
6. Check the Events tab.
7. Copy the Hardware ID where needed.
8. Note when the problem began.
9. Restart Windows.
10. Check physical cables, ports and power.
11. Disconnect docks and unnecessary peripherals.
12. Install normal Windows updates.
13. Review optional driver updates.
14. Download the exact manufacturer driver.
15. Roll back a recent driver where appropriate.
16. Reinstall the device if the code recommends it.
17. Scan for hardware changes.
18. Check hidden devices for duplicates—not general cleanup.
19. Update platform drivers and firmware.
20. Review Reliability Monitor and Event Viewer.
21. Test the hardware on another computer where possible.
22. Run manufacturer diagnostics.
23. Arrange hardware assessment if the code persists.

How Hamilton Group Can Help

A yellow triangle tells you that Windows has noticed a problem. It does not tell you whether the correct solution is a restart, a driver, a firmware update or replacement hardware.

Hamilton Group’s experienced IT team can identify the cause without applying random driver packages or risky Registry changes.

Device and Driver Diagnosis

We can analyse:

• Device Manager codes
• Driver versions
• Hardware IDs
• Device events
• Plug and Play installation status
• Parent and dependent devices
• Windows and manufacturer logs

Correct Driver Selection

Hamilton Group can identify and install the appropriate:

• Chipset driver
• Graphics driver
• Wi-Fi or Bluetooth package
• Storage controller
• Audio driver
• Touchpad or camera driver
• USB-C and Thunderbolt software

Firmware and BIOS Support

Where the error relates to platform configuration, we can safely update:

• BIOS or UEFI
• Embedded controllers
• Dock firmware
• SSD firmware
• Motherboard components

Hardware Testing

When Code 10, 24 or 43 suggests possible hardware failure, we can test:

• Memory
• Storage
• Network adapters
• Graphics hardware
• USB controllers
• Docks
• Expansion cards
• Motherboards

Business-Wide Remediation

When several PCs develop the same yellow triangle after an update, Hamilton Group can:

• Identify affected models
• Compare driver versions
• Pause an unsuitable deployment
• Roll back the problem driver
• Test a corrected package
• Deploy the solution centrally
• Monitor compliance through Microsoft Intune

Hamilton Group aims to make first contact on IT support requests within 15 minutes, helping businesses restore essential hardware before it causes extended downtime.

Read the Number Before Trying the Fix

The yellow triangle is only the warning symbol.

The numbered Device Manager code tells you what Windows believes has gone wrong:

• Code 28: no suitable driver
• Code 10: the device did not start
• Code 22: the device is disabled
• Code 43: the device or driver reported failure
• Code 45: the hardware is disconnected
• Code 52: the driver signature cannot be verified

Record the code, check the driver and hardware history, then follow the resolution appropriate to that specific state.

Call 0330 043 0069, book a meeting with one of our experts or visit hgmssp.com for experienced help with Device Manager errors, Windows drivers and computer hardware.