Jordan
04-25-2014, 03:29 PM
Hi,
We have been having an issue with our Microsoft Surface Pro 2 tablets (March firmware) and the DisplayLink software 7.5 M2, 7.5 M1, 7.5 M0 & 7.4 M2 (didn’t try other versions). The problem is when this software has been installed the HID Sensor Collection in device manager after booting up would intermittently have a yellow exclamation mark next to it which appears to cause the Surface to freeze up when browsing "Devices & Printers".
After some investigation, it appears this only happens when the Surface Type Cover 2 is connected to the Surface Pro 2, the original Type Cover does not have the same issue, neither does the original Surface Pro (with Type Cover 2). We have found that a way round this is to disable " Surface type cover 2 firmware update device" under Human Interface Devices within Device Manager. Not sure what other issues this causes but from our quick tests everything still appears to work OK.
Just thought I would mention in case anyone else has the same issue, maybe it will properly be fixed in the next Surface firmware update....
We have been having an issue with our Microsoft Surface Pro 2 tablets (March firmware) and the DisplayLink software 7.5 M2, 7.5 M1, 7.5 M0 & 7.4 M2 (didn’t try other versions). The problem is when this software has been installed the HID Sensor Collection in device manager after booting up would intermittently have a yellow exclamation mark next to it which appears to cause the Surface to freeze up when browsing "Devices & Printers".
After some investigation, it appears this only happens when the Surface Type Cover 2 is connected to the Surface Pro 2, the original Type Cover does not have the same issue, neither does the original Surface Pro (with Type Cover 2). We have found that a way round this is to disable " Surface type cover 2 firmware update device" under Human Interface Devices within Device Manager. Not sure what other issues this causes but from our quick tests everything still appears to work OK.
Just thought I would mention in case anyone else has the same issue, maybe it will properly be fixed in the next Surface firmware update....