[Manufacturer] %MfgName% = MediaTekDevices, NTamd64 [MediaTekDevices.NTamd64] %DeviceName% = USB_Install, USB\VID_0E8D&PID_7663
The Silent Handshake
The device was a prototype IoT gateway powered by a MediaTek MTK chipset. It was supposed to speak to Windows 10 over USB, presenting itself as a standard Ethernet adapter. Instead, Windows saw a ghost.
MediaTek’s reference design used the CDC Ethernet Control Model —a standard USB class. On Linux, it worked instantly. On macOS, it worked after a kext. But on Windows 10? Windows expected a specific CDC subclass, or worse, a proprietary driver with a signed INF. mediatek cdc driver for windows 10
Four replies. 24ms.
[MediaTek.AddReg] HKR, NDI, HardwareID, 0, "USB\VID_0E8D&PID_7663"
But it wasn't enough. Windows 10’s driver signing enforcement was the final boss. Leo had to boot into "Disable Driver Signature Enforcement" or submit the driver to Microsoft’s Hardware Dev Center for attestation. MediaTek’s reference design used the CDC Ethernet Control
And Leo? He still doesn't trust the yellow exclamation mark.
He closed the Device Manager, leaned back, and whispered to the empty lab: "Handshake accepted."
MediaTek CDC ECM Data →
He opened a text editor and wrote:
Windows 10 ships with cdc_ecm.inf , but it’s notoriously picky. It demands exact interface associations and will reject the device if the endpoint descriptors are one byte off. Leo’s gateway had three interfaces: a control interface, a data interface, and a third for debugging. Windows saw the third interface and threw a "Code 10" error: Device cannot start .
The icon turned green. The gateway got an IP. Leo pinged 8.8.8.8. But on Windows 10
Leo stared at the Device Manager. Under "Other Devices," a single entry blinked with the yellow exclamation of damnation: .