@FisherDanyel: Based on the .corp internal hostname, I’m going to assume my guess about your Redmond-based employer is correct. I worked in Building…43? for about a year in '99.
I know that everything has changed since then, but my recollection is that at the time internal Windows builds were…just a bit different than shipped builds.
I also know that local domain policies can lock down a lot of behavior that would be perfectly acceptable on a vanilla install.
Sadly, since I was in the Exchange org an not the Windows org, I never actually learned that much about the internals.
I 100% believe we’re doing something that Windows sees as weird (and the Code 43 error does give me some hints), but I’d love to be able to repro before I start blindly trying to fix it.
The good thing is that I’m 99.99% certain this can be fixed over USB with a firmware update.
The USB VID and PID aren’t showing up as what we send, but if Windows is flipping out and refusing to talk to the device, that’s not too surprising.
If you hold in the Prog key when you connect the keyboard, you should see it start to glow Red. That’s the bootloader mode. I’d love to know if that throws the same errors. If it does, this is potentially more serious, but not necessarily insurmountable.