DEVICE-MANAGER-CODE-45
What it means
Usually much simpler than most other Device Manager codes: this is a leftover entry for a device that was once connected but genuinely isn't plugged in right now — Windows keeps a record of previously-connected devices, and this code just reflects that.
Also seen as: Currently, this hardware device is not connected to the computer (Code 45), Code 45 error
Quick fix steps
- Check whether the device is actually plugged in and powered on — this resolves the large majority of Code 45 cases, since it's the expected, correct message for a disconnected device.
- If the device genuinely is connected and you're still seeing this, try a different USB port or cable, since a bad physical connection can also produce this code.
- If it's a leftover entry for a device you no longer own or use, it's generally safe to just ignore it — right-click and Uninstall device if you'd like to clear it from the list, though it's not causing any actual problem by sitting there.
Frequently Asked Questions
Why does Windows keep a record of devices that aren't connected?
Should I clean up these leftover entries regularly?
Other error codes
DEVICE-MANAGER-CODE-10 — Device Manager Code 10: This Device Cannot Start
One of the most common, generic Device Manager codes — Windows tried to start the device and couldn't, usually because of an outdated or corrupted driver, though it can also point to a temporary hardware fault.
DEVICE-MANAGER-CODE-28 — Device Manager Code 28: The Drivers for This Device Are Not Installed
Exactly what it says — no driver is currently installed for this device at all, as opposed to a driver being present but broken.
DEVICE-MANAGER-CODE-39 — Device Manager Code 39: Windows Cannot Load the Device Driver for This Hardware
Different from Code 28 — here a driver is present, but Windows can't actually load it, usually because the driver file itself is corrupted or missing a required component.
DEVICE-MANAGER-CODE-43 — Device Manager Code 43: Windows Has Stopped This Device Because It Has Reported Problems
A deliberately vague, catch-all code — the device itself reported a problem to Windows, which stopped it as a protective measure, but the specific reason isn't included in the code itself. Common causes range from a genuinely failing piece of hardware to a driver conflict to, on graphics cards specifically, a crashed or hung GPU.