For IT professionals, a cluttered Device Manager makes troubleshooting difficult. If you have 15 hidden "HID-compliant mouse" entries because you’ve tested various mice over the year, tracking down an actual driver conflict becomes a guessing game.
is a command-line and GUI utility developed by Uwe Sieber (a respected German software engineer known for low-level Windows tools). Unlike commercial system cleaners that bundle bloatware, DeviceCleanup.exe is a single executable file (typically under 200 KB) that requires no installation.
void PrintUsage() std::wcout << L"DeviceCleanup.exe - Remove non-present (ghost) devices\n\n"; std::wcout << L"Usage:\n"; std::wcout << L" DeviceCleanup.exe [/list] - List all non-present devices\n"; std::wcout << L" DeviceCleanup.exe /remove <id> - Remove device by instance ID or hardware ID\n"; std::wcout << L" DeviceCleanup.exe /remove-all - Remove all non-present devices\n"; std::wcout << L" DeviceCleanup.exe /force - Bypass pending restart flag (use with /remove or /remove-all)\n"; std::wcout << L" DeviceCleanup.exe /verbose - Show detailed info\n"; std::wcout << L"\nExample:\n"; std::wcout << L" DeviceCleanup.exe /list\n"; std::wcout << L" DeviceCleanup.exe /remove "USB\VID_1234" /force\n"; std::wcout << L" DeviceCleanup.exe /remove-all /verbose\n"; DeviceCleanup.exe
is a popular third-party utility for Windows used to manage and remove "non-present" (ghosted) devices from the system's registry. While it is not a Microsoft tool, it is widely recommended in technical forums for troubleshooting USB and peripheral connectivity issues. Core Functionality
| Scenario | Ghost Devices Created | |----------|----------------------| | Frequently plugging USB drives into different ports | One entry per port per device | | Switching mice/keyboard between USB and Bluetooth | Two separate stacks per peripheral | | Cloning a drive or migrating OS from old hardware | Complete device tree from source machine | | Testing drivers (virtual audio, virtual network adapters) | Many left after uninstall fails | | Using a docking station with multiple laptops | Every combination of dock+device persists | For IT professionals, a cluttered Device Manager makes
DeviceCleanup.exe /remove-all /force /verbose
Sometimes, when you plug a device into a specific USB port, Windows tries to assign it a resource (like an Interrupt Request or IRQ) that is technically still "reserved" for a ghost device that was previously plugged into that port. This can lead to devices not being recognized, failing to start, or behaving erratically. Core Functionality | Scenario | Ghost Devices Created
A third-party driver package or software (like printer suites) reinstalls the device entry. Fix: Uninstall the associated software first, then run DeviceCleanup.exe, then reboot.
| Risk | Likelihood | Mitigation | |------|------------|-------------| | Deleting a currently connected device (rare) | Low (GUI excludes by default) | Check "Show present devices" before deletion | | Deleting a critical hidden device (e.g., system timer) | Very low (protected by Windows) | Run as Admin; system won’t delete active enumerators | | Breaking a virtual device that is offline but needed (like a VPN adapter) | Moderate | Use filters – do not delete VPN or SAN devices if you will reconnect later | | Deleting a Bluetooth keyboard that is currently disconnected but will be reconnected | Low (re-pairing is easy) | Re-pairing takes seconds |
std::wcerr << L" -> Failed to remove device. Error: " << cr << std::endl; return false;