Code 28 is a Device Manager error. Microsoft defines it as:
“The drivers for this device are not installed. (Code 28)” [R1][R2]
This means Windows knows that the device exists, but it does not currently have a suitable driver installed for it.
A driver is software that lets Windows communicate with hardware. Without a compatible driver, the device may appear in Device Manager but cannot provide its normal functions. [R3]
Code 28 is not the same as “the device is broken”
Code 28 is primarily a driver-installation problem, not proof of hardware failure.
Microsoft's driver documentation identifies one form of this condition as Windows Plug and Play being unable to find a compatible driver for the device. [R1]
That is different from Code 43, where a driver reports that the device has failed, and from Code 45, which means a previously known device is currently disconnected. [R2]
Those distinctions matter because each state needs a different repair.
Start with Windows Update
The safest first place to look for a driver is Windows Update.
Windows automatically installs recommended drivers for many hardware devices. Optional driver updates can also appear under:
Settings → Windows Update → Advanced options → Optional updates [R3]
If Windows offers a driver for the affected device, install that driver and restart the PC if requested.
Do not install every optional driver merely because it is listed. The goal here is to supply the missing driver for the device showing Code 28.
Try Device Manager
Microsoft also documents reinstalling the affected device through Device Manager.
For Code 28, the documented process is to uninstall the affected device and then scan for hardware changes so Windows attempts to install the driver again. [R2]
This is useful when Windows already has a suitable driver package available but the device did not install correctly.
Removing the device entry does not repair damaged hardware. It causes Windows to detect the device again and attempt the driver-installation process another time.
If Windows cannot find a driver
If Windows Update and automatic driver installation cannot find a compatible driver, use the official support site of the PC manufacturer or device manufacturer.
Microsoft recommends downloading manual drivers from the manufacturer's website and specifically warns against obtaining drivers from unrelated download sites. [R4]
Make sure the driver is intended for:
- the exact device or PC model;
- your version of Windows;
- the correct system architecture.
Installing a driver intended for similar-looking but different hardware is not a good substitute.
How does Windows know which driver belongs to the device?
Windows uses identifiers reported by hardware to match devices with driver packages.
A hardware ID identifies a device and is used by Windows when selecting a matching driver. Windows may also use more general compatible IDs when an exact hardware-ID match is unavailable. [R5]
You can see these identifiers in Device Manager → Properties → Details → Hardware Ids.
This is especially useful when Device Manager shows a generic name such as Unknown device. The hardware ID can help identify what the device actually is before a driver is installed.
What if no compatible driver exists?
Older devices may not have a supported driver for the version of Windows you are running.
Microsoft's Code 28 documentation specifically describes the case where Plug and Play cannot find a compatible driver. [R1]
If neither Windows Update nor the manufacturer's current support site provides a compatible driver, do not force-install an unrelated package. Check the manufacturer's compatibility information instead.
The device may require different hardware, an older supported operating system, or vendor assistance.
How do I know it is fixed?
After installing the driver, check the device again in Device Manager.
Code 28 should no longer appear, and Windows should identify the device normally.
Then test what the device is actually supposed to do: play audio, connect to the network, read data, display video, or perform its other intended function.
The problem is resolved when the correct driver is installed and the device actually works, not merely when a driver installer reports success.