I share other's concerns about an editor that relies on a usb connection.
USB doesn't have to cause such problems. I've got other types of gear which functionality never has been impeded by anything connected to its USB-port. What I fear is that the problem is at driver-level which puts a fix out of reach of CK and his team. I believe the KPA is based on some minimalist, preferably real-time, operating-system which would be responsible for handling networking/USB I/O. A network-scan I did some time ago by hooking the network-port to my LAN was unable to clearly identify the system, but the exposed part of the network protocol-stack was pointing to some form of Windows. You'd need internal knowledge of the design to be certain.
That said, I think we should drop the bug-discussion from this thread. My point was only to emphasise that I wish CK and his team are able to solve this issue with a firmware-update accompanying the editor when it finally arrive. A failure to do so makes the KPA/editor combo a lot less desirable for uses where the editor will be left idle, but remain connected, for longer periods of time.