ToolTip AI

Driver errors,
translated.

Device Manager tells you what is wrong in a sentence that explains nothing. «Windows has stopped this device because it has reported problems» is a fact about Windows' inference, not about your hardware. Here is what each message is really claiming, and what you can safely do about it.

device manager · windows 10 & 11 · x64

Before you press anything.

A driver error is almost never fixed by the first button the screen offers.

Windows guesses. When a device misbehaves, the error code describes what the operating system observed at the moment it gave up — not the root cause. That is why the same «Code 43» can mean a dead USB controller, a bad cable, an antivirus that blocked a kernel callback, or a driver from three Windows versions ago.

So work in this order, and stop as soon as one step fixes it. Most driver problems die at step two.

  • Write down the code, not the sentence. The number in «Status: Code 43» is stable across Windows versions and languages. The sentence next to it is rephrased constantly, and it is the sentence search engines fail on.
  • Change one variable at a time. Port, cable, driver version, BIOS setting. Two changes at once and you have learned nothing even if it starts working.
  • Skip every «driver updater» utility. They install generic drivers with no vendor testing and no clean way back. Windows Update, the PC maker's support page and the chip maker's page are the only three sources worth using.
  • Know that Disable is not Uninstall. One is a switch you can undo in two seconds. The other can delete the only copy of the driver on the machine — including the one that lets you reach the internet. Entry twelve below is the one people need most.

The codes.

Open the one you have. Device Manager shows it under the device's Status box, on the General tab.

Code 10 — this device cannot start
What it is
Windows loaded the driver and asked the device to begin working, and the device refused or never answered in time. The driver is present; the handshake failed.
What changes
Nothing yet — this is a symptom. In practice it is usually a driver built for a different Windows version, a power-management setting that switched the device off too aggressively, or a physical device that is genuinely not initialising.
Risk
Reversible Reinstalling a driver and rebooting does not touch your data. The only way to make it worse is to uninstall the network driver on the only machine you own with no other way to download a replacement.
Code 12 — not enough free resources
What it is
Two devices are claiming the same interrupt or memory window, and the plug-and-play manager gave up on one of them. Far more common on older hardware and on machines with a lot of PCIe cards.
What changes
The fix is to move the device to a different slot or port, or to disable a device you are not using so it stops reserving the resource. Rebooting sometimes shuffles the allocation and hides the problem until it returns.
Risk
Careful Disabling the wrong device can take out audio, the chipset or a storage controller. Note what you disabled before you do it.
Code 18 and Code 28 — the drivers for this device are not installed
What it is
Windows knows the hardware exists (it read its vendor and device identifiers) but has no driver package matching it. The two codes mean the same thing; 28 is the one modern Windows shows, 18 appears in older installs and some upgrade paths.
What changes
You need a driver from Windows Update, from the machine maker's support page for your exact model, or from the chip maker. A device with no matching driver is also how an Unknown device starts — see the entry below.
Risk
Reversible Installing a driver is reversible with Roll Back Driver or by uninstalling the device and letting Windows rediscover it.
Code 22 — this device is disabled
What it is
Someone turned the device off in Device Manager — the «Disable device» command, not a hardware fault. The little down-arrow on the icon is the tell.
What changes
Right-click and choose Enable device. That is the whole fix. If it disables itself again after a reboot, something is doing it on purpose: a group policy, a management agent, or a driver that refuses to start.
Risk
Reversible The safest code on this page. Nothing is deleted and nothing is reinstalled.
Code 24 — this device is not present, is not working properly, or does not have all its drivers installed
What it is
A catch-all that Windows shows while a device is on its way out. It appears normally for a few seconds after you choose Uninstall device, and it appears for a device that was unplugged since the last boot.
What changes
If you just uninstalled the device, do nothing: the ghost entry disappears on reboot. If it persists on a device that is physically present, use Scan for hardware changes and then treat it as a Code 18.
Risk
Reversible Mostly a display state. The only mistake here is panic-deleting a leftover entry that is about to vanish by itself.
Code 31 — Windows cannot load the device driver; it may be corrupted or missing
What it is
The driver is registered in the system but failed to load. Corruption, a half-finished update, or a filter driver left behind by a program you removed.
What changes
Reinstall the driver from a clean copy. If the message survives a clean reinstall, the usual culprit is an upper or lower filter left in the registry by uninstalled software — that one needs the vendor's cleanup tool rather than more driver files.
Risk
Careful Editing device filter keys by hand in the registry can make a machine unbootable if you touch a storage or class key. Do not do it on a guess.
Code 37 and Code 39 — the driver failed to initialise, or an old copy is still in memory
What it is
Both are driver-side failures. Code 37 means the driver's initialisation routine returned an error. Code 39 means Windows cannot load the driver because a previous version is still resident, or its registry entry is unreadable — it shows up a lot after a failed update or a Windows servicing pass.
What changes
A full shutdown (not sleep, not restart with fast startup on) clears the resident copy for Code 39. If it stays, reinstall the driver; if it still stays, the registry service key for that device class is the problem.
Risk
Careful «Shut down and turn on again» is free. Reinstalling a chipset or storage driver while the old one is half-loaded is where machines get strange.
Code 43 — Windows has stopped this device because it has reported problems
What it is
The most-reported code and the least specific one. The driver told Windows «something is wrong with this device, stop using it». Windows did not decide what is wrong; the driver did, and it is not obliged to say.
What changes
Work from cheapest to dearest: a different port or cable, then disable and re-enable the device, then Roll Back Driver if the errors began after an update, then a clean reinstall of the vendor driver. For USB storage and phones, also check the power settings that are allowed to switch the device off.
Risk
Reversible Every step above can be undone. What is not reversible is assuming Code 43 is always software: on a device that fails on three different machines, it is the hardware.
Code 45 — this hardware device is not currently connected
What it is
Windows still has the device recorded from a previous session but cannot see it now. Completely normal for anything you unplug: docks, monitors, phones, external drives, gamepads.
What changes
Nothing to fix if the device works when it is plugged in. If it vanishes mid-use, the problem is the connection or the power management of the port, not the driver.
Risk
Reversible Informational. The entry exists so you stop chasing it.
Code 52 — Windows cannot verify the digital signature for the drivers required for this device
What it is
The driver exists but is unsigned, or signed with a certificate Windows no longer trusts. On 64-bit Windows this is a hard stop, not a warning, unless Secure Boot policy is relaxed.
What changes
The correct answer is a newer signed driver from the vendor. Windows does offer a way to load unsigned drivers temporarily, and it is a diagnostic tool, not a configuration: the restriction returns on the next boot and the machine is less safe while it is off.
Risk
Expensive Disabling driver signature enforcement is one of the few settings where malware can persist in kernel mode. Do it to test, never to live with.
«Unknown device» with a yellow triangle and no code at all
What it is
The hardware identified itself with a vendor and device identifier, and no installed driver package claims that pair. Windows can tell something is there but not what it is.
What changes
Read the Hardware Ids line on the Details tab — a string like VEN_8086&DEV_1903. The VEN_ half is the maker and the DEV_ half is the chip; those two numbers identify the device far better than its name, and they are what you search for.
Risk
Reversible Reading a property cannot break anything. Guessing a driver from a device name can: install by hardware ID and you will not guess wrong.
Update, Roll Back, Disable, Uninstall — the four buttons people confuse
What it is
The right-click menu of any device. They are not four strengths of the same action; they do four different things to four different copies of the driver.
What changes
Update driver looks for a different package and leaves the current one on disk. Roll Back Driver returns to the version Windows kept from before the last update — it is greyed out whenever no previous version was saved, which is most of the time on a fresh install. Disable device switches it off and keeps everything: reversible in two clicks. Uninstall device removes the instance; and the checkbox next to it, Attempt to remove the driver for this device, is the one that actually deletes the driver files. Windows re-detects an uninstalled device on the next reboot and reinstalls it from the driver store, which surprises people who wanted it gone.
Risk
Careful Order matters: disable before you uninstall anything you might need back, and only tick the removal checkbox once you have the replacement driver already downloaded.

Your device manager is not this page.

These twelve codes are the common ones. Yours may be a vendor-specific message nobody has written down yet, in a driver panel translated by whoever shipped it. That is the case a reference cannot cover — and the case the application reads.

Get ToolTip AI on Microsoft Store
Windows 10 build 19041 or newerWindows 1164-bit onlyNo administrator rights
Part of the guides library.