Drivers: Device Manager Errors, Updates, Rollbacks and the Yellow Triangle

01 What Windows drivers are and why they matter

A driver is a small, specialized program that lets Windows talk to a specific piece of hardware. Each device — a graphics card, sound card, network adapter, USB controller — needs its own driver, because the hardware differs and the instructions to operate it are device-specific. Without the right driver, Windows can see that something is connected but can't reliably control it.

This is why driver problems show up in so many forms: a missing driver means a device may not appear at all, an outdated one may limit performance, and a broken or incompatible one can make a device fail or, in a worse case, destabilize the system. Keeping in mind that a driver is the bridge between hardware and the operating system is the foundation for everything else on this page.

When you're troubleshooting, it also helps to remember that a driver issue is not the same as a hardware fault. A device can be perfectly fine and simply be missing or misconfigured software, which is usually easy to fix. Keeping those two possibilities distinct early on saves a lot of time.

02 Understanding Device Manager

Device Manager is Windows' built-in console for viewing and managing the hardware connected to your PC and the drivers that control it. It lists your devices in categories — display adapters, sound, network adapters, USB controllers — and shows a status icon for each. A small arrow, a yellow triangle, or a red cross each carry meaning.

The yellow warning triangle (a yellow triangle with an exclamation mark) is the icon you'll see most when something is wrong: it means Windows found the device but there's a problem with its driver or configuration. Right-click a device and choose Properties to open a window with a status line, the driver details, and the device's specific error code.

Device Manager is the single most useful place to start when a device misbehaves, because it tells you what Windows thinks the problem is in a specific, checkable way. You don't need to install anything to use it — it's part of Windows.

03 How to open Device Manager

The fastest route is the Run dialog: press the Windows key + R, type the command below, and press Enter. That opens Device Manager directly on every supported Windows version.

devmgmt.msc

Other reliable routes: right-click the Start button (or press Windows key + X) and choose Device Manager from the menu, or search for "Device Manager" in the Start menu. When it opens, Windows may ask how to view the devices — "by category" is the friendliest starting point. The small toolbar at the top offers actions like "Scan for hardware changes" and a menu for showing hidden devices.

04 Understanding the yellow warning triangle

The yellow triangle with an exclamation mark means one specific thing: Windows detected the device, but it can't use it properly because of a driver or configuration problem. It's a warning, not a confirmation that the hardware is broken. A device with this icon may still partially work, or not work at all, depending on the underlying error.

The icon alone doesn't tell you the cause — you need to open the device's Properties to see the specific error code and Windows' description of the problem. That code (for example, Code 10 or Code 28) is the key to choosing the right next step, which is why this guide is organized around reading and responding to those codes (see reading error codes).

A few habits make the yellow triangle less alarming. Don't panic-reinstall everything — first read the specific error. Note which device has the icon and what it was doing before. And remember that several devices can carry the triangle at once, which often points to a single shared cause (a recent update, a chipset driver, a Windows update) rather than several separate failures.

05 Reading Device Manager error codes

When you open a device's Properties, the "Device status" area usually shows a code in brackets, like "The device cannot start (Code 10)." That code is Windows' specific diagnosis, and it's far more useful than the general yellow triangle. Different codes point to different kinds of problems: a missing driver, a resource conflict, a firmware fault, or a device Windows has disabled.

The table below lists the codes you're most likely to meet. Use it for a quick read, then jump to the detailed section for that code for the specific steps. Keep in mind that the exact wording Windows shows can vary by version and by device, so treat these as the general meaning rather than a word-for-word quote.

The pattern to remember: the code tells you the category of problem, not always the exact cause. A Code 10, for instance, can come from a bad driver, a resource conflict, or failing hardware. Read the code to narrow things down, then work through the suggested first steps in order, testing after each one.

06 Error code 1

Code 1 usually means Windows thinks a device should be present but can't confirm it — the status typically reads that the device "is not present, is not working properly, or does not have all of its drivers installed." In practice it often appears after a device was removed, after a failed driver install, or when a connection is intermittent.

A useful first check is to rescan: use the Action menu's "Scan for hardware changes" and make sure the physical device is firmly connected (and, on a laptop, that it isn't a port or docking issue). If the device genuinely is no longer connected, the code is simply telling you so. If it is connected and still shows Code 1, try uninstalling and reinstalling the device, or let Windows Update attempt a driver.

07 Error code 10 — "the device cannot start"

Code 10 is one of the most common codes you'll see, and the most general: the driver loaded but the device failed to start, and Windows hasn't pinned down why. Common causes include a recently updated or corrupt driver, a resource conflict, a firmware problem, or, less often, the hardware itself.

Start by reading the fuller description in the device's status, which sometimes gives a more specific stop reason. Then, if a driver update preceded the problem, roll the driver back to the previous version. If rollback isn't available, uninstall the device (optionally removing the driver software) and let Windows reinstall it, or install the manufacturer's driver. If the code returns after a clean reinstall and the hardware is old, it's worth considering that the component itself may be failing.

08 Error code 12 — "not getting enough resources"

Code 12 means the device "is not getting enough resources" — a resource conflict where the device can't secure the IRQ, memory range, or DMA channel it needs to operate. This is more common on older systems with many add-in or PCIe devices, and it can appear when a new device is added or when a BIOS setting changes.

Because it's a sharing problem, the fix is usually about allocation rather than a driver file. Check whether another device is claiming the same resource, disable a device you don't need to free one up, and look in the BIOS/UEFI for any resource-assignment or power settings that affect the slot or bus. If it involves a card you can move, physically relocating it to a different slot sometimes resolves it — see driver and resource conflicts.

09 Error code 14 — "invalid device status"

Code 14 indicates the device "has reported invalid device status" — in other words, the device or its firmware reported a state that Windows doesn't accept. This often points to a hardware or firmware-level problem rather than a simple missing driver.

A full power cycle is a good first step: shut the PC down completely (not sleep), unplug or switch off power, wait a little, and restart, which can clear a stuck device state. If it's a laptop, try a different port. If the code persists across a clean driver reinstall, the component or its firmware is the more likely cause, and manufacturer support is a reasonable next stop.

10 Error code 18

Code 18 is typically shown when "the drivers for this device are not installed" — Windows found the device but no suitable driver was put in place. You'll often see it with newly added hardware, after a fresh Windows install, or after a driver was removed.

The fix is to get the driver in place. Let Windows Update try first (it has a large built-in driver store), and if that doesn't resolve it, install the driver from the device or computer manufacturer. If the device shows as unknown, find its hardware ID first and use that to locate the correct driver. A "Scan for hardware changes" can sometimes prompt Windows to match a driver it already has.

11 Error code 19 — firmware-reported problem

Code 19 generally means the device "is disabled because the firmware has reported a problem." Here the device's own firmware has flagged an issue, so Windows has taken the device offline. This is more about the hardware or its firmware than about a Windows driver file.

A full power cycle is a good first move, as it can clear transient firmware states. After that, check whether the manufacturer has published a firmware or BIOS update for the device or the system, since firmware fixes are the usual remedy for firmware-reported faults. If the code remains after updating firmware and reinstalling drivers, the hardware is the more probable cause and a manufacturer or repair service is appropriate.

12 Error code 22 — "driver could not be loaded"

Code 22 usually appears when a driver for the device "could not be loaded," or the device's driver failed to start. It tends to follow a failed or interrupted driver installation, or a driver file that is missing or incompatible.

A clean reinstall is the usual remedy: uninstall the device in Device Manager (checking the option to delete the driver software if offered), then reinstall from the manufacturer or via Windows Update. If a specific driver version works but the current one doesn't, roll back to the working version. Repeated Code 22 after clean installs can indicate a corrupted driver package or a deeper system issue, in which case running the built-in system file checkers is a sensible next step.

13 Error code 24 — missing dependency

Code 24 typically means "the driver for this device requires access to another device on your computer, but that device is currently unavailable." So the problem is a dependency: the driver needs something else — a parent device, a service, or another controller — and that something else isn't responding.

Look at what the device depends on. A card in a PCIe slot may rely on the chipset or root bus working correctly, so check the parent device in Device Manager for its own errors, and make sure any related Windows service is running and set to start. Resolving the dependency usually clears the code, and a reboot after fixing it helps Windows re-establish the relationship.

14 Error code 28 — "drivers not installed"

Code 28 is the classic "the drivers for this device are not installed" code, and one of the most common you'll encounter — especially on a freshly installed system or with brand-new hardware. It means Windows sees the device but has no driver for it.

Let Windows Update try first, since it maintains a large driver store and will often find the right driver automatically. If not, get the driver from the manufacturer and install it. If the device also shows as unknown, capture its hardware ID and use that to find the exact driver. After installing, run a "Scan for hardware changes" and, if needed, a restart, so the new driver is picked up and the yellow triangle clears.

15 Error code 29 — missing dependency

Code 29 is similar in spirit to Code 24: the driver "requires access to another device on your computer, but that device is currently unavailable." The device can't function because a dependency is missing or offline.

Identify the dependency and address it — this is often a parent controller or a related Windows service. Check the parent device in Device Manager for its own status, confirm the relevant service is present and set to start automatically, and then reboot. If the dependency is a physical component (a controller or bus), make sure that component is seated and healthy, since the dependent device won't clear until its dependency is available.

16 Error code 31 — "cannot initialize the device"

Code 31 generally means "Windows cannot initialize the hardware device." The operating system tried to bring the device up and it didn't respond, which points more toward the hardware, its firmware, or a low-level driver than to a simple missing file.

Begin with a full power cycle and, where possible, reseating the device or trying a different slot or port. Update the device's firmware and the system BIOS if the manufacturer offers them, since initialization faults are sometimes firmware-related. If a clean driver reinstall doesn't change things and the device is older, treat it as a possible hardware failure and consider manufacturer support.

17 Error code 32 — missing dependency

Code 32 usually indicates a driver dependency problem — commonly that the driver "requires access to another device on your computer, but that device is currently unavailable." It behaves much like Code 24 and 29: the device is waiting on something else.

Find and fix the dependency. Look at the parent device and any related service in Device Manager, make sure the required service is installed and running, and reboot so Windows can re-link the device to its dependency. If the dependency is a physical controller or bus, confirm that component is present and healthy. In many cases the code clears once the device it depends on is back online.

18 Error code 37 — corrupt install

Code 37 typically means the driver "requested an unknown registry path" — a sign that a driver installation was corrupted or incomplete and left Windows pointing at something that isn't there. This follows interrupted installs or a bad driver package more often than a hardware fault.

The remedy is a clean reinstall of the driver: uninstall the device in Device Manager with the option to delete the driver software if offered, remove any partially installed driver, and install a fresh copy from the manufacturer or Windows Update. If the problem started after a specific driver version, roll back to a known-good version. Repeated Code 37 can also indicate a damaged driver package, so downloading the driver again from a trusted source can help.

19 Error code 39 — disabled by Windows

Code 39 means "Windows has automatically disabled the device because it has reported problems." Windows switched the device off on its own after detecting repeated faults, so the device won't work until the underlying issue is addressed.

Check the Windows Event Viewer for the specific failure that triggered the disable — this often points at a driver or a hardware fault. Then try rolling back or reinstalling the driver, and update firmware or BIOS if available. If the device keeps getting disabled after clean driver work, it's reporting real problems and the hardware is a likely cause, so manufacturer support is a sensible next step. While it's disabled, you can re-enable it temporarily in its Properties to test whether it works at all.

20 Error code 41 — "still setting up"

Code 41 usually means "Windows is still setting up the device" — a transient state where the device is mid-configuration. In most cases it resolves on its own after a short wait or a restart, so it's the least worrying of the codes here.

If it clears after a reboot, there's nothing more to do. If Code 41 sticks around for an unusually long time or returns repeatedly, treat it as a stuck setup process: try a "Scan for hardware changes," reinstall the device's driver, or run Windows Update so any pending driver completes. Persistent Code 41 on a specific device can indicate a driver that never finishes installing, so a clean reinstall of that driver is the usual fix.

21 Error code 43 — "reported problems"

Code 43 is the most-cited of the device codes: "this device has been disabled because it has reported problems." It means the device (or its driver) told Windows it has failed and Windows has stopped it. It can be triggered by a bad driver, a firmware fault, overheating, or actual hardware failure, so it's worth diagnosing rather than assuming a cause.

Start with the Event Viewer: the System log usually records the specific reason the device was stopped, and that detail points the way. Then roll back or cleanly reinstall the driver, and check for overheating or a loose connection — this code is a common sign of a graphics card that is failing or running hot (see graphics driver troubleshooting). Update firmware/BIOS if offered. If the device is repeatedly stopped after a clean driver install, the hardware is the more likely culprit and manufacturer support is the right next step. If the device is a mystery, capture its hardware ID to confirm exactly what it is.

22 Error code 45 — "device not present"

Code 45 generally means "this device is not present" — Windows has a record of a device that is no longer connected. This is normal and expected when you unplug something, remove a card, or change hardware; it's the system noting that a previously known device has gone away.

If the device is supposed to be connected, check the physical connection and try a different port or slot, then run "Scan for hardware changes" so Windows re-detects it. If you intentionally removed the hardware, the entry is harmless and will clear on its own or after a rescan. Persistent Code 45 on a device you know is connected usually means the connection or the slot is faulty rather than a driver problem.

23 Error code 52 — incomplete driver

Code 52 typically means "the drivers for this device are not installed, or the drivers do not include a resource that is required." So either the driver is missing or the driver that's present is incomplete for this particular device.

The fix is to install a complete, correct driver: let Windows Update try, and if that's not enough, get the full driver package from the manufacturer (partial or generic drivers are a common cause of the "resource not included" wording). Do a clean uninstall first if a driver is already present but wrong. After installing, rescan for hardware changes and reboot if needed. If a complete manufacturer driver still produces Code 52, the device may need a specific firmware or a particular driver version, which the vendor can confirm.

24 Identifying unknown devices

An "Unknown device" (often under "Other devices") is hardware Windows can see but doesn't have a driver or identity for. It's a common sight after adding new hardware or after a fresh install, and it's the starting point for finding the right driver.

The reliable way to identify it is through its hardware ID. Open the device's Properties, go to the Details tab, and select "Hardware Ids" from the dropdown. Copy the top value — it's a string that identifies the exact device. That identifier is what you use to find the correct driver, and it's the next step in finding a device's hardware ID.

Once you have the hardware ID, you can match it to the manufacturer's driver (many support pages let you look up by device) or confirm what the device actually is. If a device shows as unknown and Windows Update can't resolve it, the hardware ID is your best tool for getting the correct driver from the right source.

25 Finding a device's hardware ID

The hardware ID is a unique identifier that tells you exactly what piece of hardware is installed, even when Windows can't name it. To read it, open the device's Properties in Device Manager, choose the Details tab, and pick "Hardware Ids" from the property list. The first entry is the primary ID.

There are related properties worth knowing too: "Compatible IDs" (a list of broader IDs the device matches), "Device Instance Path" (where the device sits in the system), and "Location Information" (which physical slot or port). The primary Hardware ID is usually what you need to look up a driver.

Copy the ID to your clipboard rather than re-typing it, since these strings are long and easy to get wrong. With the ID in hand you can determine the exact device and find the correct driver from the manufacturer — the whole point of this step. You can also list installed drivers from the command line if you prefer:

pnputil /enum-drivers

26 Identifying the correct driver

"The correct driver" means a driver that matches three things: the exact device, the right version of Windows, and the right architecture (64-bit, in practice for modern systems). A driver that's close but not exact is a common source of persistent problems.

Start from the hardware ID (see the previous sections) to confirm the exact device, then get the driver from the most authoritative source available. For a laptop or branded PC, the computer manufacturer's support page is usually best, because it lists the drivers validated for that specific model. For a standalone component (a GPU, a network card), the component manufacturer's site is the right place. Windows Update is a fine fallback and often has a suitable driver.

Avoid generic "driver downloader" utilities and unofficial driver sites — they frequently install the wrong driver or bundle unwanted software. The safest, most accurate path is: identify the device precisely, then install the driver the hardware or computer maker provides for your version of Windows.

27 How to update a driver through Device Manager

Updating a driver replaces the current driver for a device with a newer version. In Device Manager, right-click the device, choose "Update driver," and you'll get two main options. The first — "Search automatically for drivers" — lets Windows look (including via Windows Update) for a newer driver and install it if it finds one. The second, manual option, lets you point Windows at a driver you've downloaded or browse your computer for driver software.

A sensible habit is to let Windows try the automatic option first, because it often has a suitable driver already and it keeps you on a tested version. Use the manual option when you have a specific driver from the manufacturer that you want to install (for example, a newer graphics driver). Before updating anything critical, it's worth creating a recovery point and noting the current driver version so you can roll back if the new one misbehaves.

One important nuance: "Update" can sometimes install a different or generic driver than you expected, and the automatic path may find nothing newer even when the vendor has one. That's why, for performance hardware, many people install the manufacturer's driver directly from its official site. Updating is low-risk and reversible, which makes it a reasonable first attempt when a device seems to be running on an old driver — see manufacturer drivers vs Windows Update.

28 How to scan for hardware changes

"Scan for hardware changes" asks Windows to re-check what hardware is present and to match drivers accordingly. You'll find it on the Action menu in Device Manager (and, on some versions, as a toolbar button). It's the quickest way to get Windows to notice a newly connected device or to re-evaluate a device that has changed state.

It's a good first action in several situations: after plugging in new hardware, after removing and reinstalling a device, or when a device has disappeared from the list. It won't fix a bad driver on its own, but it prompts Windows to re-detect and, where it has a suitable driver, to install or re-associate it.

If a scan doesn't resolve a problem, it tells you the issue is likely a driver that needs a specific version (from the manufacturer) rather than something Windows can match automatically. So treat a scan as a fast, low-risk first step before moving to manual driver installation.

29 How Windows automatically reinstalls drivers

One of Windows' useful behaviours is that, when you remove a device or its driver, it often reinstalls a working driver on its own. This happens when you scan for hardware changes or reboot: Windows matches the device against its driver store (its collection of known drivers, including those delivered via Windows Update) and installs the best match it finds.

This is why "uninstall and let Windows reinstall" is a common and effective fix: it clears a corrupt driver and lets Windows put back a clean, compatible one. It also means you don't always need to hunt down a driver file — Windows' store plus Windows Update covers a lot of common hardware.

The limitation is that the automatic driver is sometimes a basic or generic one rather than the vendor's latest, which is fine for stability but may leave performance on the table (notably for GPUs). So automatic reinstall is a great way to get a device working again, and you can follow up with the manufacturer's driver if you want the full-featured version.

30 Manufacturer drivers vs Windows Update drivers

You'll generally have two sources for a driver: the driver delivered through Windows Update (part of Microsoft's driver store) and the driver published by the hardware or computer manufacturer. Both can be "correct" in the sense that the device works, but they differ in how current and how fully featured they are.

Windows Update drivers are convenient, automatically maintained, and stable — the sensible default for most devices (audio, basic network, USB controllers, and so on). Manufacturer drivers are often newer and expose more features and performance, which matters most for graphics cards and some other performance hardware. For those, installing the vendor's driver directly is usually worth it.

A good rule of thumb: let Windows Update handle the everyday devices, and use manufacturer drivers where you want the latest features or performance, or where Windows Update has no suitable driver. Whichever you choose, get it from an official source, and note the version you install so you can roll back if needed.

31 Chipset drivers and why they matter

The chipset is the set of components on the motherboard that manage communication between the CPU and everything else — memory, storage, USB, PCIe slots, and so on. Chipset drivers tell Windows how to work with that hardware, and because so many devices hang off the chipset, a missing or outdated chipset driver can cause problems that look like they're with individual devices.

If you're seeing several devices with errors at once — USB controllers, storage controllers, PCIe devices, or unknown devices — the chipset is a common shared cause, and updating the chipset driver (from the motherboard or computer manufacturer) can clear several codes at once. It's also one of the first things worth installing on a fresh build or a fresh Windows install.

Get the chipset driver from the motherboard maker (for a desktop build) or the computer maker (for a laptop/branded PC), matching your exact model. It's a safe, reversible update, and doing it before you chase individual device drivers can save a lot of back-and-forth.

32 Driver installation failures

A driver install can fail in a few ways: the installer errors out, Windows can't find a suitable driver, the install completes but the device still shows a warning, or the install is interrupted. Common causes include an incomplete or wrong driver package, a missing prerequisite (like the chipset driver), or the installer being blocked.

Work through it methodically: confirm you have the driver for the exact device and Windows version (a mismatch is the most common cause), run the installer with the necessary permissions, and make sure the chipset driver is current first, since some device drivers depend on it. If the installer itself fails, get a fresh copy from the official source and try a clean install (uninstall any partial driver first).

If installs keep failing on one device but work on others, the device or its slot may be at fault. And if Windows Update reports it can't find a driver, that usually means you need the manufacturer's driver rather than something from the Windows store.

33 Windows Update driver problems

Windows Update delivers many drivers automatically, and occasionally a delivered driver isn't the best fit for your hardware, leaving a device with a warning or reduced function after an update. It can also happen that Windows Update removes or replaces a working manufacturer driver with a more generic one.

First, confirm the problem is tied to an update (check the update history for a driver or quality update around when it started). If a Windows Update driver is the issue, you can install the manufacturer's driver to take precedence. If a Windows quality update caused broader driver trouble, uninstalling that update from Windows Update settings can restore the prior state.

Keep the balance in mind: Windows Update drivers are generally safe and keep most devices working, so the goal isn't to stop driver updates, but to steer a specific device to a better driver when the automatic one misbehaves. Getting the vendor's driver and noting the working version keeps you stable without cutting yourself off from updates.

34 How to roll back a driver

Rolling back restores the previous version of a driver — the one that was in place before the most recent update. It's available on a device's Properties page, on the Driver tab, as a "Roll Back Driver" button, and it's the fastest remedy when a recent driver update is what broke a device.

The button only works if Windows still has the earlier version available; if it's greyed out, either no previous version is stored or it was removed (see when rollback isn't available). Before rolling back, take a moment to confirm the timing fits — that the problem started around the last driver update — because rolling back only helps if that update is the cause. After rolling back, restart if prompted and test the device.

Roll back is one of the safest driver actions, because it returns you to a known-working state rather than introducing something new. It's a good first move for a Code 10 or Code 43 that appeared right after an update.

35 When a driver rollback is appropriate

Rollback is the right tool when the timeline points at a driver update: the device worked, a driver was updated (often automatically), and it stopped working or started misbehaving afterward. In that situation, returning to the previous driver is the most direct fix.

It's the wrong tool, though, when there was no recent update to roll back to, when the device never worked on the current driver, or when the problem is actually hardware. Rolling back a driver that was never working won't help, and if the "previous" version is also bad, you'll just be moving sideways.

A practical rule: if a driver change and the problem are close in time, roll back first (it's fast and reversible). If there's no clear driver change, or rollback isn't available, move to a clean reinstall with a known-good driver instead.

36 When Roll Back Driver is unavailable

When the Roll Back Driver button is greyed out, it usually means Windows no longer has the previous driver version — perhaps it was never stored, was overwritten, or the device was reinstalled. So you can't simply step back, and you need another path to a working driver.

The usual alternative is a clean reinstall. Uninstall the device in Device Manager, checking the option to delete the driver software if offered, then reinstall a known-good driver — either by letting Windows Update find one or by installing the manufacturer's driver for the exact device and Windows version. If you know which version previously worked, download that specific version from the manufacturer.

To make rollback available in future, some manufacturer installers store the prior driver, and creating a recovery point before updates gives you a system-level way back. If you regularly hit this, keeping a record of which driver versions work on your machine (the Driver tab shows the version and date) saves time.

37 How to uninstall a problematic driver

Uninstalling removes a device's driver (and optionally the driver software itself). In Device Manager, right-click the device and choose "Uninstall device." A dialog may offer a checkbox to "Attempt to remove the driver for this device" — checking it does a deeper clean, which is useful when the existing driver is corrupt.

Uninstall is a stronger step than update or rollback, and it's the right one when a driver is damaged and the lighter options have failed. After uninstalling, either run "Scan for hardware changes" or restart, and Windows will typically reinstall a basic driver automatically (see how Windows reinstalls drivers); or you install the manufacturer's driver. Because uninstalling can briefly leave a device without a driver, do it on a device you can afford to have offline for a few minutes.

Be deliberate about scope: uninstall the specific device that's misbehaving, not "all devices." And if you're uninstalling a display driver to fix a graphics problem, be aware your screen may change resolution or briefly flicker — that's normal and reversible.

38 Creating a recovery point before driver changes

A system restore point is a snapshot of your system's state that you can return to if a later change goes wrong. Because driver changes — especially chipset and major device drivers — can have wider effects, taking a restore point before you make them is cheap insurance and one of the best habits to form.

To create one, search for "Create a restore point" (or open System Protection), select your drive, and choose "Create," giving it a name like "Before driver update." Windows will take the snapshot. You can then make your driver changes with the confidence that, if something breaks, you can restore to this point.

A couple of caveats: restore points cover system and driver state, not your personal files, so they're a complement to (not a replacement for) regular backups. And you can only roll back to a point that was actually created, so create one before the change, not after. It's a reversible, low-effort step that makes more invasive driver work much less scary.

39 Driver problems after a Windows update

A Windows update can change or replace drivers (updates often include driver updates), and occasionally a new driver doesn't suit your hardware, leaving devices with warnings or new behaviour right after an update. If several things changed at once with an update, that's a strong clue the update is involved.

Work out which update it was (Settings → Windows Update → update history) and then target the change. If a specific driver update is the cause, roll that driver back. If the update itself is the problem and it's a recent quality update, you can sometimes uninstall that update from Windows Update settings to return to the prior state.

Keep the options in mind: roll back the affected driver (most targeted), uninstall the problematic update (broader), or, if a driver is missing after the update, reinstall it. Creating a recovery point before big updates is the cleanest insurance, so you have a system-level way back if an update causes driver trouble.

40 Graphics driver troubleshooting

Graphics (display) driver problems are among the most common and the most visible: screen flicker, artifacts, crashes in games or video, a dropped or black display, or a Code 10/43 on the display adapter. Because the GPU is performance-critical and its driver is large and complex, it's the one device where the manufacturer's driver usually matters most.

Start by noting when the problem began — right after a driver update, a Windows update, or new hardware? If it followed a driver update, roll the graphics driver back first. For a stubborn problem, do a clean driver install: uninstall the display adapter (optionally deleting the driver), then install the current driver from the GPU manufacturer's site. Many GPU vendors also offer a dedicated cleaner for a truly clean slate.

Keep an eye out for signs that point to hardware rather than software: if a clean, current driver still gives a Code 43, crashes, or a black screen, and the card runs very warm, the card or its connection may be failing. Check that it's seated and its power connectors are attached, and if the problem persists on a clean driver, manufacturer support is the right next step.

41 Network adapter driver troubleshooting

Network driver problems show up as lost internet, a disabled adapter, a Code 10/28/43 on the network adapter, or Wi-Fi that works but is unreliable. Distinguishing a driver problem from a network or router problem is the key first move (if other devices on the same network are also down, it's likely not your adapter's driver).

Confirm it's local first, then work the adapter: check that the adapter is enabled, roll back or reinstall the network driver, and try "Scan for hardware changes." For Wi-Fi, also check the wireless service is running and the correct adapter is selected. Getting the adapter's driver from the computer manufacturer (for laptops) or the card's vendor is the reliable fix when Windows Update's driver misbehaves.

If a clean driver reinstall doesn't restore the connection and the adapter shows a hardware-level error, the wireless or card hardware may be at fault. Testing with a USB network adapter or a wired connection can confirm whether the built-in adapter is the problem, which is useful information for a repair decision.

42 Audio driver troubleshooting

Audio driver issues range from "no sound" to a device that appears in Device Manager with a warning. Before touching drivers, rule out the simple stuff: the correct output device is selected, nothing is muted, and the right app is sending audio to the right device. A surprising number of "no sound" cases are just a wrong default device.

Once the basics check out, look at the audio device in Device Manager. Roll back or reinstall the audio driver, and make sure the audio service is running. Audio drivers are well covered by Windows Update and by the computer manufacturer, so a clean reinstall from one of those sources usually resolves driver-level no-sound problems.

If a clean driver reinstall restores the device but sound is still wrong, the issue may be a specific output (headphones vs speakers), a sample-rate mismatch, or the app. If the audio device shows a hardware-level error after clean driver work, the audio hardware (or, on a laptop, a connection) may be failing, which is a repair conversation.

43 Bluetooth driver troubleshooting

Bluetooth problems typically appear as a missing or disabled Bluetooth adapter, a Code 10/28/43 on the Bluetooth device, or paired devices that won't connect. As with other wireless, first confirm it isn't a broader issue (airplane mode on, the other device's battery, or the PC's wireless switched off).

Then work the Bluetooth adapter in Device Manager: make sure it's enabled, roll back or reinstall its driver, and run a hardware-changes scan. The Bluetooth driver is usually handled well by Windows Update or the computer manufacturer, so a clean reinstall is the standard fix. On some laptops the Bluetooth radio shares hardware with Wi-Fi, so a problem in one can affect the other — worth checking both.

If the adapter is missing entirely or shows a hardware error after a clean reinstall, the radio may be faulty or tied to a setting. Testing whether a USB Bluetooth dongle works can confirm whether the built-in radio is the issue.

44 USB driver and device troubleshooting

USB problems include a port that doesn't power or recognize a device, an "Unknown device" under Universal Serial Bus controllers, or a Code 10/43 on a USB hub or root hub. Because many devices share the USB controller and the root hubs, a problem at the controller level can affect several ports at once.

Start by testing the device in a different port (ideally one on the opposite side of a desktop, to test a different controller), and check the USB controllers in Device Manager for errors. A clean reinstall of the USB controller drivers, or an updated chipset driver, often clears controller-level codes. For a single device, uninstall it and rescan so Windows re-detects it.

If an entire set of ports stopped working, that points at the controller, power, or (on a laptop) a hardware fault rather than a single device's driver. If individual ports work but one doesn't, it may be a port or cable issue. USB Selective Suspend (a power setting) can also cause intermittent disconnects on some devices, and toggling it is a reasonable thing to try.

45 Storage-controller driver troubleshooting

Storage-controller drivers manage how Windows talks to your drives (SATA, NVMe, and related controllers). Problems here can look like a missing or slow drive, a "Standard NVM Express" or "IDE ATA/ATAPI" device with a warning, or a storage controller showing an error. These can be more serious because they affect your data, so back up important files before doing anything aggressive.

A missing storage driver is a classic issue on fresh Windows installs (which is why installers sometimes need extra storage drivers). In normal use, if a storage device shows an error, check the device's status and code, try a clean driver reinstall, and make sure the chipset driver is current (storage controllers often sit under the chipset). Updating the chipset driver can resolve storage-controller codes.

Because storage involves your data, favour the safe, reversible steps — driver reinstall, chipset update, checking connections — over anything that touches the disk contents. If a drive is showing hardware-level errors or failing to be detected at all, that's a drive-health situation: back up first, check the connection, and consider that the drive itself may be failing.

46 PCI / PCIe device errors

PCI and PCIe devices are the cards and components in your expansion slots — graphics cards, network cards, sound cards, add-in storage. Errors on them can appear as a "PCI simple communicator," a PCIe root port, or the specific card showing a Code 10/12/43. PCIe root-port errors, in particular, can cause the devices behind that port to misbehave.

A useful first check is whether the error is on the card itself or on the PCIe root port or bridge it connects through — if the root port is erroring, the devices behind it may be collateral. Reseating the card, trying a different slot, and updating the chipset and BIOS are the standard hardware-side steps. Resource-conflict codes (like a Code 12) on PCIe devices can sometimes be resolved by moving the card to a different slot or adjusting BIOS settings.

If a specific card errors on a clean driver in multiple slots, the card or the slot may be at fault. If several devices behind one root port fail together, the port or a BIOS/PCIe setting is a likely cause. These are the kinds of problems where the exact error code and which devices are affected tell you whether to chase the card, the slot, or the firmware.

47 Driver and resource conflicts

A conflict happens when two devices try to use the same system resource (an IRQ, a memory range, a DMA channel) or when two drivers disagree about how a device should behave. Resource conflicts classically show up as a Code 12 ("not getting enough resources"), and driver conflicts can surface as instability or a device that works in one state but not another.

Resource conflicts are more common on systems with many add-in cards or legacy devices. The usual remedies are to free up a resource (disable a device you don't need), move a card to a different slot, or adjust BIOS/UEFI settings that control resource allocation. For driver conflicts, the fix is often to standardize on one driver for a device (for example, removing a duplicate or generic driver in favour of the manufacturer's) rather than having two drivers compete.

When diagnosing a conflict, note which devices are affected together — if two devices started failing at the same time or one "steals" from another, a shared resource is a likely theme. Resolving conflicts is usually about allocation and consistency, not about installing more software.

48 Safe Mode and driver troubleshooting

Safe Mode starts Windows with a minimal set of drivers and services, which is useful for isolating whether a problem is caused by a specific (non-essential) driver or by something more fundamental. If a device problem or a crash goes away in Safe Mode, that's a useful signal that a third-party driver is involved.

You can enter Safe Mode from Settings → Recovery → Advanced startup, or by holding Shift while choosing Restart, or via the startup settings screen. From Safe Mode you can often uninstall a problematic driver or roll it back more easily, because the offending driver isn't loaded.

Keep the purpose in mind: Safe Mode is a diagnostic and repair environment, not a place to do your normal work (many drivers and features are intentionally absent, so things like Wi-Fi or your GPU may be limited). Use it to isolate and fix a driver problem, then restart into normal mode to confirm the fix holds.

49 The driver troubleshooting workflow

A reliable order of operations keeps driver troubleshooting from becoming a scattergun. In broad strokes: identify the device and read its exact error code; confirm the timing (did a driver or Windows update precede it?); try the least invasive fix that matches the code (roll back if an update is the cause, reinstall if the driver is missing or corrupt); get the correct driver from an official source; and test after each step.

The table below lays out the workflow by situation, so you can see the first check, the next step, and when to escalate.

The real value of the workflow is that it separates software causes from hardware causes methodically. Most driver problems resolve in the first few steps; if you've done a clean, correct driver install and checked the hardware and the code persists, you have strong evidence the issue is physical, which points to manufacturer support rather than more driver tinkering.

50 When to stop and seek manufacturer support

There's a point where continuing to cycle through driver steps stops being productive and the honest answer is that the cause is likely hardware, or beyond what's safe to fix without the right tools and parts. Recognising that point is part of good troubleshooting.

Signs it's time to call it: a clean, correct, current driver still produces the error; the device shows hardware-level codes (Code 14/19/31/43 persisting after clean driver work); the problem follows a physical event (a drop, a spill, a power surge); the device is old and the cost of parts approaches the machine's value; or the fix would require opening the system in a way you're not comfortable doing.

When you do reach out, you'll get further by reporting the specific error code, what you've already tried (updates, rollbacks, clean reinstalls, chipset/firmware updates), and when it started. That context lets a manufacturer or technician skip the basics you've done and focus on the likely hardware or firmware cause. And remember the standing rule: back up your data before any repair or before sending a machine away.