The issue is that when the device first boots if the GPS device begins communicating "too soon" windows will assume that it is a serial mouse and enumerate it as such. I deploy hundreds of these devices in my environment and this issue literally almost drove me insane in the beginning. Intel Dynamic Platform and Thermal Framework, Intel Grpahics HD., Intel Chipset Device Sfotware, O2 Micro memory card reader. I went to the support site and ran the automatic driver detection (I know). I also appear to be missing the 'intel WiUSB' 'UoIP Hub' devices that the factory tablet has in Device Manager.
And there is no 'Serial Ballpoint Mouse' in the device manager. The reg key I'm applying has been left untouched (set to a "3" instead of my fix of setting to a "4"). The reg key I'm using: ĮDIT1: I just unboxed one that hasn't been reimaged yet to see what the device manager looks like. I have the Dell driver cabs for this model getting automatically applied, but maybe there is some way for the imaginary 'Ballpoint' device to not get detected in the first place? There is a reg key that disables this behavior, but before I apply it to my task sequence, I wanted to see if anyone else has come up with a better fix. They have an onboard GPS device that appears to be working properly, but Windows likes to also detect a Microsoft Serial Ballpoint device that ends up making the mouse pointer jump around like crazy and makes the device generally unusable. I'm imaging a few Dell Rugged 12 (7202) touchpad devices with Windows 10 Enterprise 圆4.