How to fix Error 636 on Windows 11

by

Why This Error Happens

Error 636 is logged by the Kernel-PnP driver when the Plug and Play manager detects that a USB device was physically disconnected (or lost power momentarily) while Windows was still in the process of enumerating its descriptors. This is most commonly caused by a loose USB connection, a failing USB port/hub, insufficient power delivery to the device, or a corrupted/outdated USB driver that mismanages the enumeration handshake. It is largely a hardware-communication timing issue rather than a software corruption problem, though driver bugs can trigger it even with a stable physical connection.

Step-by-Step Resolution Guide

  1. Check Physical Connections
    Unplug the affected USB device, inspect the cable/port for damage, and reconnect it directly into a rear/motherboard USB port (avoid front-panel headers, hubs, or USB extension cables during testing).

  2. Update or Reinstall USB Controller Drivers

  • Open Device Manager (Win + X → Device Manager).
  • Expand Universal Serial Bus controllers.
  • Right-click each USB Root Hub and Generic USB Hub entry → Uninstall device (do not check “delete driver software”).
  • Restart the PC; Windows will reinstall the drivers automatically.
  1. Disable USB Selective Suspend
  • Go to Settings → System → Power & Battery → Additional power settings.
  • Click Change plan settings → Change advanced power settings.
  • Expand USB settings → USB selective suspend setting and set both On battery and Plugged in to Disabled.

  1. Update Chipset Drivers
    Download the latest chipset driver package from your motherboard/laptop manufacturer’s support page and install it, as this often resolves USB enumeration timing issues at the firmware-driver level.

  2. Test with Minimal USB Load
    Disconnect all other USB peripherals temporarily and test the problematic device alone to rule out a power-draw conflict on a shared hub or port.

Alternative or Verification Steps

  • Open Event Viewer (eventvwr.msc) → Windows Logs → System, filter by Event ID 636, and confirm the error no longer reoccurs after reconnecting the device.
  • If the issue persists, test the device on a different PC/USB port; if it still fails, the device itself (or its cable) is likely defective and should be replaced.