Hello,
Thank you for the details. It is helpful.
The problem comes from the OS not loading the driver (that's what Code 31 is supposed to mean as well). Not been flagged yet, until you did.
This is why you see a generic name for the device and that's why I don't have much logs to look at: the driver doesn't start so doesn't write any log.
The message about compatibility is slightly misleading. This migration blocker is voluntary and expected, we worked with Microsoft to remove the old driver architecture but the new driver was silently installed at the same time... So there was nothing to do in theory.
The driver architecture changed between Windows 10 initial (Threshold) and Windows 10 Anniversary Update (Redstone) as we know native support in the OS.
The SetupAPI log for the setup and device installation gives a few elements around access rights issues. Also, you will notice that another device is failing exactly the same way (VID_8087&PID_0AC2 HID Sensor Collection V2 failing on 25th January more than once).
Is your computer IT managed and do they have Windows group policies in place around device driver installation?
I see that only the video diver is not loaded: you get network access through the dock (even if the name of the adapter is unbranded). So I don't think an end point protection software (antivirus) is blocking us. Because it is very early stage, the device you plug wouldn't have any impact: that's linked with the Windows installation, not the type of hardware.
In order to see a bit clearer in the logs (so I can follow the operations you do with what Windows logs as being done), could you please do the following:
1. Disconnect all USB devices from the laptop.
2. Run the cleaner (that will create an entry in the Windows logs and remove all devices from hidden in device manager).
3. Reboot, just in case some files are locked and login waiting a minute for it to complete the startup.
4. Plug only the Dell D1000 without any monitor/TV or any USB device connected to it, just the powered dock (to limit noise in the logs).
5. Windows will fetch the device driver from Windows Update and try to install it.
6. Check the progress of the installation.
7. Gather new logs once the process has either succeeded and failed.
Kind regards,
Alban
|