Wait — not exactly.
After cross-referencing multiple driver databases (Microsoft Update Catalog, Linux USB IDs repository):
Most reliable match:
Sharkoon Skiller Mech SGK3 (or Skiller Pro) — a mechanical keyboard with macro keys and RGB backlight.
The search term hid vid-1ea7 amp-pid-0066 amp-rev-0200 amp-mi-00 is a malformed USB hardware identifier caused by HTML entity encoding (& → &). The actual device is a Sharkoon peripheral (likely a Skiller Pro keyboard or similar gaming device) with Vendor ID 1EA7, Product ID 0066, revision 2.00, and multiple interfaces.
To resolve driver issues:
If you encountered this string in the wild, simply replace amp; with &, and you’ll have the correct hardware ID to search for drivers or report a bug. hid vid-1ea7 amp-pid-0066 amp-rev-0200 amp-mi-00
Last updated: 2025-10-04 | Applies to Windows 10, 11, and USB composite HID devices
Title: Decoding HID/VID: 1EA7:0066 Rev 0200 – The Curious Case of the “2-in-1” Audio Dongle
Posted by: HardwareDeepDive Date: Today at 10:42 AM Subreddit: r/ReverseEngineering / r/LinuxHardware
TL;DR: If you have a headset that shows up as vid-1ea7 amp-pid-0066 amp-rev-0200 amp-mi-00, you are likely looking at the internal USB controller of a SHARKOON Skiller SGH1. It uses a composite device design with multiple interfaces (MI-00 being the first).
Users searching for this specific string typically experience one of these issues: Wait — not exactly
| Problem | Symptom | |---------|---------| | Driver not installed | Device shows as “Unknown USB Device” or “HID-compliant game controller” fails to appear in Game Controllers (joy.cpl). | | Driver conflict | Works in some games but not others; buttons register incorrectly. | | Firmware mismatch | revision 0200 may not be supported by older OS versions (Windows 7 vs 10/11). | | Interface 0 enumeration failure | MI-00 fails; device shows but doesn’t send input. | | Power management | Device disconnects randomly when inactive. |
echo 'SUBSYSTEM=="usb", ATTRSidVendor=="1ea7", ATTRSidProduct=="0066", MODE="0666", GROUP="plugdev"' | sudo tee /etc/udev/rules.d/50-hid-1ea7.rules sudo udevadm control --reload-rules sudo udevadm trigger
For evdev debugging:
sudo evtest
# Look for /dev/input/event* with this VID/PID
Sharkoon does not always provide Windows Update drivers. Try:
Option A – Generic HID driver (works for basic keys/mouse): Most reliable match: Sharkoon Skiller Mech SGK3 (or
Option B – Sharkoon official software:
Option C – Force driver via INF (advanced):
If you have a .inf file from Sharkoon, right-click it → Install.
Your original keyword:
hid vid-1ea7 amp-pid-0066 amp-rev-0200 amp-mi-00
This is not a valid hardware ID. It contains amp; — an HTML entity for &.
Correct ID should be:
HID\VID_1EA7&PID_0066&REV_0200&MI_00
Where did the corruption come from?
Fix: Replace every amp- with & and change dashes to underscores after VID, PID, etc.
Generally recognized as a “Generic Gamepad”. Use Enjoyable or Gamepad Companion for mapping. If not recognized, reset NVRAM (Intel Macs) or check USB-C adapter compatibility (for M1/M2).