If Windows plays the "Device Disconnect" chime when nothing was unplugged, the usual culprit is a USB device that selective suspend powers down and that then fails to wake cleanly: it drops off the bus for a moment and re-enumerates, which Windows treats as a removal. Your logging tools stay silent because of how they sample events, not because nothing happened.
Why USBLogView and WMI queries come up empty
Two independent blind spots explain the silence. First, a WMI query such as SELECT * FROM __InstanceDeletionEvent WITHIN 2 WHERE TargetInstance ISA 'Win32_PnPEntity' is not a push notification: the WITHIN 2 clause makes WMI poll every two seconds, and a device that vanishes and reappears between two polls is never "deleted" at the moment of sampling, so no event ever fires. Short dropouts can hide from any polling interval.
Second, USBLogView only tracks USB, while the chime is played by the Plug and Play subsystem for any device removal — HID collections of a composite device, Bluetooth peripherals, even the audio endpoint a monitor exposes over HDMI or DisplayPort. A USB-only tool can sit completely empty while the sound still plays.
The prime suspect: USB selective suspend
USB selective suspend lets Windows idle individual devices and hubs to save power. On resume, some devices — wireless dongles especially — or some hubs don't come back cleanly and re-enumerate, producing exactly this kind of random, untriggerable chime. Disabling the setting is both the quickest test and, on a desktop, a reasonable permanent fix: Control Panel → Power Options → Change plan settings → Change advanced power settings → USB settings → USB selective suspend setting → Disabled. From an elevated prompt, the same applies to the active power scheme:
powercfg /setacvalueindex scheme_current 2a737441-1930-4402-8d77-b2bebba308a3 48e6b7a6-50f5-4782-a5d4-53bb8f07e226 0
powercfg /setactive scheme_current
The two GUIDs identify the USB settings subgroup and the selective-suspend setting itself; the trailing 0 disables it. If the chime stops with the setting off, the trigger is confirmed — but you still don't know which device is dropping.
Finding the offender without losing the power savings
Turn selective suspend back on, then exempt devices from it one at a time. In Device Manager, open a device or hub, switch to its Power Management tab, and untick Allow the computer to turn off this device to save power. Work through candidates in this order:
- Wireless headset and headphone dongles
- Keyboard and mouse receivers
- USB hubs — external ones plus the Generic USB Hub and root hub entries
- Card readers, external drives, and anything else permanently attached
Leave each configuration for a day or two; the change that silences the chime points at the misbehaving hardware. Then fix the root cause: move the device to a rear motherboard port instead of a front-panel header or hub, update its firmware or driver, or replace the cable. Keeping just that one device exempted is a good compromise.
Catching the device in the Kernel-PnP log
setupapi.dev.log records driver installations, so a device that resumes with its existing driver often adds nothing there. The Kernel-PnP log is a better witness: open Event Viewer → Applications and Services Logs → Microsoft → Windows → Kernel-PnP → Configuration and sort by timestamp around the moment the sound played. A device that dropped and re-enumerated leaves entries containing its instance ID, which encodes the vendor and product ID — enough to name the hardware even when no USB logger saw anything.
What about the DeviceSetupManager network errors?
The events about Network List Manager connectivity, Windows Update, and WMIS describe a brief network outage, not a device removal, and they identify nothing. Treat them as one of two things: unrelated background noise that happened to be logged near the chime, or — if your network adapter is a USB dongle — a side effect of the very same suspend/resume cycle dropping your link. Either way, they are not the lead to follow.
Keeping the problem away
A few habits reduce the chance of recurrence:
- Install current chipset and USB controller drivers from the motherboard vendor, not only through Windows Update.
- Check the dongle maker's site for firmware updates; flaky suspend/resume behavior is a known class of bug.
- Avoid chaining receivers and latency-sensitive devices through front-panel headers or unpowered hubs.
- If no specific device ever stands out, simply leave selective suspend disabled — on a desktop the energy savings are marginal.
Frequently Asked Questions
Why does the disconnect sound play when I haven't unplugged anything?
The operating system plays it for any Plug and Play device removal, including a device that drops off the bus on its own and reconnects seconds later. You'll often hear the connect chime immediately afterwards.
Does disabling USB selective suspend hurt anything?
You only give up a small idle power saving — typically a few watts on a desktop. On a battery-powered laptop the trade-off matters more, so prefer per-device exemptions there instead of turning the feature off globally.
Could my monitor be causing the sound?
Yes. A monitor connected over HDMI or DisplayPort presents an audio device that counts as a PnP device, so a power-state change or a failing cable can trigger the chime — one more case that USB-only logging misses.
Why did my WMI __InstanceDeletionEvent query miss the drop?
Because WITHIN n polls on an interval rather than streaming events. A dropout shorter than the interval, with the device back before the next sample, produces no deletion event at all.
Where exactly is the Kernel-PnP log?
In Event Viewer, under Applications and Services Logs → Microsoft → Windows → Kernel-PnP → Configuration. Sort by timestamp around the moment the chime played and look for entries containing a device instance ID.
Should I re-enable selective suspend once I've found the culprit?
Only if you want the power savings back. Keep the feature enabled and leave the offending device or hub exempted through its Power Management tab, or simply leave it disabled if the savings don't matter on your machine.