Vid 346d Pid 5678 ((exclusive))

Sometimes forcing a hardware scan helps after the driver is installed but not recognized:

Every USB device uses hardcoded identity markers to request specific operating system drivers. For this device, the standard hardware ID string reads: USB\VID_346D&PID_5678&REV_0200 .

The Vendor ID is the fingerprint of the manufacturer. It is assigned by the USB Implementers Forum (USB-IF). A quick lookup of 0x346D reveals the manufacturer: vid 346d pid 5678

Are you looking to for a specific use case, or are you trying to recover a drive that isn't working? FirstChip FC1178/FC1179 MpTools V1.0.5.2 (2022-06-01)

When a user connects a USB device, the host controller initiates an enumeration process. The device responds with a descriptor containing, among other data, its VID (assigned by the USB Implementers Forum) and a PID (chosen by the manufacturer). The operating system then matches “346d:5678” against its driver database to locate the appropriate software. Without this mechanism, every device would require manual driver installation, reminiscent of early computing’s interrupt request (IRQ) conflicts. The VID/PID system thus automates what would otherwise be a technical nightmare, enabling seamless compatibility across thousands of manufacturers. Sometimes forcing a hardware scan helps after the

: Can range from older USB 2.0 to modern USB 3.2 interfaces. ⚠️ Common Use Cases & Risks

One of the most insidious attacks in modern computing is device impersonation. A malicious USB drive can report “VID 046d PID c52b” (legitimate Logitech receiver) while actually being a keystroke injector. Similarly, an attacker could use “346d:5678” to masquerade as a trusted device if that pair corresponds to a known peripheral. Without cryptographic authentication—something the USB standard has only recently begun to address—operating systems trust the VID/PID at face value. It is assigned by the USB Implementers Forum (USB-IF)

This ID commonly appears on: