The Surface Dock and DisplayLink products are compatible and our drivers are tested with the different Surface Pro, Surface Book, Surface Docks and different adapters/docks before we release them.
We certainly can have bugs, and we look into them. For instance, a screen blanking bug was reported to us by a user at the end of January which we fixed in our latest release 7.9 M5 (
release notes).
However, if a device does not enumerate, would you explain why you believe this is a host software driver problem? Enumeration is the preliminary, low level, introduction to the host controller and OS. Windows does not invoke the drivers at that early stage (getting device descriptors) because it doesn't know which drivers to use until it knows the Device ID (here built from the USB Vendor and Product IDs) from what is connected and how (PCI, USB...).
In the personal experience I stated, DisplayLink drivers were not even installed yet as it was the first connect. That's why I find it difficult to make the link.
Your host software log files (what runs on Windows) indicate that the drivers doesn't get any reply when trying to get the
USB descriptors. Elsewhere in these logs, your device gets USB communications errors. Both are low level problems.
On the firmware side (what runs on the microchip we make which AOC put in the monitor they manufacture), we detect a USB Disconnect event. Again, a low level problem.
Would you be able to try in USB2 to see if this changes something? You can do that by using a USB2 cable or USB2 port to force the AOC monitor in USB2 mode. As it's using a different low level communication mechanism, you could see variations.
If we believe content on Microsoft Answers, people who don't have any DisplayLink software or hardware are advising other Surface Dock users to switch the graphics card off/on in the Device Manager. Microsoft employees are involved in the discussion. That's why I directed you to Microsoft. Especially as you report your AOC monitor connected directly to the Surface Pro works correctly, as it should.
To answer your question, it is standard procedure for developers to
exchange bugs with Microsoft through their hardware developer site.
There is nothing like that assigned to us by Microsoft today.
When we have an issue we can resolve, we do try to look into it.
I do understand your frustration. Still, I prefer giving you the most likely reason of the problem, so you have a chance of getting a resolution and can take an informed decision.