Code 28 in Device Manager: Step-by-Step Driver Fixes

Code 28 in Device Manager means CM_PROB_FAILED_INSTALL. The practical split is this: after you reconnect the device, does it still fail to install in Device Manager, or does it install and still stay missing from File Explorer? For storage devices, the second case can happen when the driver loads but the disk still needs a drive letter. (drivereasy.com)

What Code 28 means in Device Manager

Start by identifying the exact device before changing anything. In Device Manager, note the device name, the device class it appears under, and whether it is listed under Other devices or inside its normal category with a warning icon.

Where to look in Device Manager

Open Win+X > Device Manager. Problem devices often appear under Other devices, but they can also sit inside their normal class with a warning icon. (kb.wisc.edu)

Open the device entry, then check Properties > General for the status text and Properties > Driver for driver installation status. Microsoft identifies Code 28 as CM_PROB_FAILED_INSTALL. (Microsoft Learn)

Why USB storage confuses people

A USB drive can have two separate problems that look like one. First, the device may not have a working driver installed. Second, even after the driver loads, the disk may still stay out of File Explorer until it gets a drive letter. (wintips.org)

That is why Disk Management is not the first stop. Use it after Device Manager stops showing Code 28 and the device appears as a storage device or disk.

According to law.cornell.edu — Cornell’s Title 28 page is about Judiciary and Judicial Procedure, showing non-device-manager ambiguity for the term code 28. (source)

Likely causes of Code 28, ranked by what to check first

1) Missing or wrong device driver

1. Go to Win+X > Device Manager > the problem device > right-click > Properties.
2. Read the exact device name and class. If it is under Other devices, note that before changing it. That tells you Windows has not placed it into a normal hardware category yet.
3. Right-click the device, choose Update driver, then use Search automatically for drivers. If Windows finds nothing, install the package from the PC maker, motherboard maker, or device maker next.

This is the most common branch. Updating the driver package is a standard fix reported by windowscentral.com.

2) USB port, hub, or controller path problem

1. Plug the device into a different rear USB port on the motherboard, one that is not next to the port you used first.
2. Remove docks, front-panel ports, extension adapters, and unpowered hubs from the chain.
3. If the device changes behavior by port, reset the USB controller path before chasing drivers: open Device Manager > Universal Serial Bus controllers, uninstall the USB Root Hub and Generic USB Hub entries, restart Windows, then reconnect the device directly.

A USB drive may also fail because the USB path is unstable. If the device works on one port but not another, focus on the path on this PC first.

3) Blocked or incomplete install on this PC

1. Check whether the same device works on another computer.
2. If it does, suspect software, policy, security tools, or the chipset layer on this system.
3. Use a clean boot later in the workflow to test interference, after trying the direct driver and USB path steps first.

This branch matters when the device is fine elsewhere but keeps returning to Code 28 here.

4) Storage device detected, but still no drive letter

1. Only use this branch after Code 28 clears in Device Manager.
2. Check whether the device now appears as USB Mass Storage Device or as a disk in Disk Management.
3. If the disk is present but absent from File Explorer, open Win+X > Disk Management, right-click the partition, choose Change Drive Letter and Paths, then add or change a letter.

Assigning a drive letter is a post-driver visibility fix, not a first-line Code 28 fix.

Use this Code 28 decision tree before changing anything

Start with device class, then test one different USB port and one different computer before reinstalling anything. That short sequence separates four realities fast: missing driver, bad USB path, blocked install on this PC, or a storage disk that loads but still needs a drive letter.

Decision-tree checklist

How do I fix Code 28 when the driver is missing or wrong?

Fix the exact device entry first, not the whole PC. In Device Manager, confirm the hardware name, try Update driver, then use the correct OEM or chipset package if Windows does not find one. If the install looks corrupted, uninstall the device and let Windows detect it again.

Use Update Driver first

1. Open Win+X > Device Manager.
2. Right-click the problem device > Update driver.
3. Select Search automatically for drivers.
4. If nothing useful appears, install the driver from the PC maker, motherboard support page, or device maker.

Updating the driver package is a standard fix reported by windowscentral.com. For Intel High Definition DSP Code 28 cases on Windows 11 or Windows 10, the system maker package is usually safer than a random driver utility.

Use Uninstall device when the current install is incomplete

1. Open Win+X > Device Manager > right-click the problem device > Uninstall device.
2. If shown, check Delete the driver software for this device.
3. Select Uninstall.
4. Restart Windows and reconnect the device.

Checking the delete box is recommended when reinstalling a corrupted driver package. After restart, watch whether the device returns under Other devices with Code 28 or installs into its normal class.

For USB storage devices, try the built-in storage model list

1. Open Device Manager > right-click the USB storage device > Update driver.
2. Select Browse my computer for drivers > Let me pick from a list of available drivers on my computer.
3. Choose Compatible USB Storage device if listed.
4. If needed, choose USB Mass Storage Device in the Model list, then complete the install and reconnect the drive.

One fix is to select Compatible USB Storage device in the driver list. Another is to choose USB Mass Storage Device in the model list.

Is this really a USB path problem rather than a driver problem?

If the device changes behavior by port, dock, or hub, treat Code 28 as a USB path issue before assuming the driver package is wrong. The clean test is a direct connection to another USB port, then a controller reset through Device Manager so Windows rebuilds the hub chain.

Test the path, then reset Universal Serial Bus controllers

1. Disconnect the device from any dock, adapter, or hub.
2. Move it to a direct motherboard port.
3. Open Win+X > Device Manager > Universal Serial Bus controllers.
4. Right-click each USB Root Hub and Generic USB Hub entry, then select Uninstall device.
5. Restart Windows and reconnect the device.

WinTips advises uninstalling all Universal Serial Bus controllers and USB devices, then restarting.

Why does Code 28 come back after restart or only happen on this PC?

When Code 28 returns after reboot, focus on things that interrupt a fresh install: hub power saving, USB selective suspend, chipset layers, or third-party software blocking the install. If the same hardware works elsewhere, repeated failure here points to the PC build rather than the device itself.

Check USB Root Hub power management

1. Open Win+X > Device Manager > Universal Serial Bus controllers.
2. Right-click each USB Root Hub > Properties > Power Management.
3. Clear Allow the computer to turn off this device to save power.
4. Select OK on each hub, then restart.

The power setting fix is to uncheck the option that lets Windows turn off the device to save power.

Disable USB selective suspend, then update chipset drivers

1. Open Control Panel > Power Options > Change plan settings > Change advanced power settings.
2. Expand USB settings > USB selective suspend setting.
3. Set it to Disabled. On laptops, check both On battery and Plugged in.
4. Then install the latest chipset package from the PC or motherboard support page.

USB selective suspend can be changed to Disabled. WinTips says the next step may be installing the latest chipset drivers.

Use clean boot when software may be blocking installation

1. Press Win+R, type msconfig, and press Enter.
2. On the Services tab, check Hide all Microsoft services, then select Disable all.
3. On the Startup tab, open Task Manager and disable startup items.
4. Restart, reconnect the device, and test the install again.

Use this later in the workflow when normal driver installation and direct-port testing do not stick. If the device installs in a clean boot state, re-enable services and startup items in stages to find the blocker.

What if the USB device is detected but still missing from File Explorer?

Once Code 28 is gone, stop treating the issue as a driver problem. If Device Manager now shows a USB storage device normally, but File Explorer stays empty, open Disk Management and look for a healthy disk that is online yet missing a drive letter.

Assign a drive letter only after the driver loads

1. Confirm the warning icon is gone in Device Manager.
2. Press Win+X > Disk Management.
3. Find the USB disk. If it is present and online, right-click the partition.
4. Select Change Drive Letter and Paths > Add or Change, then assign a free letter.
5. Reopen File Explorer by closing its current window and opening File Explorer again from the taskbar or Win+E.

This is the exact point where Disk Management becomes the real fix. WinTips recommends assigning a drive letter if the drive still does not show in File Explorer.

Still not working? What to collect before you escalate

Before moving to repair steps or vendor support, collect the details that separate a bad device from a bad Windows install. That record should include the device class, exact Device Manager wording, port behavior, another-PC test result, and whether Disk Management sees the disk after Code 28 clears.

If that did not work, move up this escalation ladder

1. Record the exact device name, class, and status text from Device Manager > Properties > General.
2. Note whether it works on another USB port and another computer.
3. For storage devices, note whether Disk Management sees the disk after the warning disappears.
4. If targeted driver, hub reset, power, chipset, and clean-boot steps fail, use an in-place upgrade repair install for Windows 10 or Windows 11.

WinTips lists an in-place upgrade as the final repair option for Windows 10/11. If the device fails on another known-good PC too, that is when hardware failure becomes a stronger suspect.

Prevention

When the fix is complete, keep chipset drivers current from the system maker and stop plugging problem devices back into the same flaky hub or front-panel port. A stable direct port can prevent the same failed state from returning.

Frequently asked questions

What is Code 28 in Device Manager?

Open Win+X > Device Manager > the device > Properties and read the status text first, because the next step changes if the device is USB storage, audio, chipset, or another class.

Why does Device Manager say drivers for this device are not installed?

Usually because Windows does not have the right package, the current package is incomplete, or installation was interrupted. Start with Device Manager > right-click device > Update driver, then use Uninstall device and restart if the status does not change. Hidden stale entries can also be checked through View > Show hidden devices.

Should the device be uninstalled to fix Code 28?

Yes, if Update driver fails or the current install looks broken. Use Win+X > Device Manager > right-click device > Uninstall device, and check Delete the driver software for this device if that box appears. Then restart and reconnect so Windows can rebuild the entry cleanly.

Does installing chipset drivers help with Code 28 on Windows 10 or Windows 11?

It can, especially when the device works on another computer but repeatedly fails on this one. Install the latest chipset package from the PC or motherboard support page after trying direct driver install, USB controller reset, and power-setting changes.

Can clean boot help if Code 28 keeps returning after restart?

Yes. A clean boot is useful when security software, management tools, or startup services interfere with driver setup. Run msconfig, hide Microsoft services, disable the rest, disable startup items in Task Manager, restart, and reconnect the device. If installation succeeds, re-enable items in stages to find the blocker.

What if the device works on another computer but shows Code 28 here, and what does “Code 28” mean outside Device Manager?

If it works elsewhere, focus on this PC’s USB path, power settings, chipset package, and clean-boot testing rather than declaring the device dead. Also, “Code 28” is ambiguous outside Device Manager; Cornell’s Title 28 page covers Judiciary and Judicial Procedure, so search results can mix unrelated meanings.