Please help me

[GitAlboBis]

Description

The KmBox Net "Network" cable uses a WCH CH397 USB-to-Ethernet chip (USB\VID_1A86&PID_5397).
This chip does not work on Windows 11 ARM64 devices because there is no ARM64-compatible kernel-mode driver available.

Environment

• Device: Microsoft Surface Pro 11 (Snapdragon X Elite)
• OS: Windows 11 ARM64 (24H2)
• KmBox: KmBox Net
• Cable: Blue USB "Network" cable (port 2)

Problem

When connecting the Network cable to the Surface Pro:

1. The device appears in Device Manager as unknown (USB\VID_1A86&PID_5397)
2. Windows cannot find a compatible driver automatically
3. Manually installing the WCHUSBNIC driver fails — it is compiled for x86/x64 only
4. Forcing the generic RNDIS driver also fails — the device does not function

The "Game Console" cable (port 1) works perfectly — it enumerates as a standard HID device which does not require architecture-specific drivers.

What I Tried

• Installing kmboxNetDriver.zip from the KmBox docs — fails (x86/x64 only)
• Forcing "Remote NDIS Compatible Device" driver in Device Manager — fails
• Forcing "USB CDC ECM" class driver — not available / fails
• Windows Update scan for drivers — no results

Expected Behavior

The Network cable should be recognized as a USB Ethernet adapter on Windows 11 ARM64, allowing UDP communication with the KmBox Net on the 192.168.2.x subnet.

Request

1. Does KmBox have an ARM64-compatible version of the network adapter driver?
2. Is there a firmware setting to force the CH397 into standard CDC-ECM/RNDIS mode so that Windows built-in class drivers can handle it?
3. Are there plans to support ARM64 Windows devices (Surface Pro, Snapdragon laptops) in future firmware updates?

Notes

• The CH397 chip is manufactured by WCH (Nanjing Qinheng). I have also contacted them at tech@wch.cn requesting the ARM64 driver (WCHUSBNIC_ARM64).
• ARM64 Windows does not emulate kernel-mode drivers — only user-mode x86/x64 apps are emulated via Prism. Hardware drivers must be natively compiled for ARM64.

Thank you for your support.

[ZCban]

The key difference is this:

x86/x64 applications → can be emulated on Windows ARM.
x86/x64 kernel-mode drivers → must match the kernel architecture. An ARM64 kernel cannot load an x64 driver compiled for a different CPU.

For example:

An x64 program communicating with a printer can be emulated.
The printer driver running in the kernel must be ARM64.

Essentially, you won't be able to communicate with the device via ARM.