Unfortunately we are unable to support Kitkat versions. We rely on the operating system to get the pixels to display. This was only implemented from Android 5 Lollipop. That means we are unable to make it work on non-modified Kitkat versions because there is nothing for us to interface with.

http://support.displaylink.com/knowledgebase/articles/557862-known-issues-and-limitations-with-displaylink-for

It’s not “stupid” but necessary due to changes in Intel graphics drivers your machine uses. We do not put any update in Windows Update as critical unless we absolutely have to.

Please create a support ticket with your log files so we can investigate your particular case. Details on support.displaylink.com/knowledgebase/articles/544810-how-can-i-report-windows-installation-issues-to-di

This needs a better description as to specific issues on Mac that need addressing. Some issues are already documented and being worked on by DisplayLink. as documented in knowledgebase articles.

V7.9 M3 is required to be compatible with the latest Intel and NVIDIA graphics drivers on Windows 10.

If you are having issues, please let us know through the contact area of the support site, including as much information as possible and your DisplayLink log files so we can look into it further.

Are you running the Apple operating system from the external drive as well?

DisplayLink is not responsible for the product design. We provide ICs which can be integrated into products. Physical hardware failures such as this, should be fed back to the product manufacturer.

This can be done today, using standard OS interfaces. DisplayLink displays can be managed using OS APIs.

Any known issues or problems that can be detected or worked around are already done today.

Thanks for the idea, but this is not something specific for DisplayLink to do.

This would be a product built by a DisplayLink partner who would take the DisplayLink technology and build a KVM around it.

Thanks for the suggestion. For Linux we intend to supply and support a driver for Ubuntu, but have designed it to be repackaged for distribution to other Linux distributions.

We cannot be the experts to maintain this for all Linux distros. We intend to provide the tools to enable it to be ported and added to package managers by those familiar with the particular distro they wish to package it for.

If you have repackaged it for a package manager, please let us know and we can build a list of supported distros.

The touch screen controllers are separate from DisplayLink and there is no touch screen technology built into our ICs.

Touch screen support is enabled by customers integrating DisplayLink and a touch screen controller into the same product.

This means that the drivers for the touch screen controller differ between products and are not part of the DisplayLink driver.

For touch support on Android, the touch screen drivers would need to be integrated into the Android OS, and this is not something DisplayLink can do as we do not own the OS on phones or tablets.

See the comment from Carlo on this being an OS X feature, which can be disabled.

The reason a reboot is needed is that the DisplayLink graphics driver is uninstalled. It is not possible to complete a graphic driver uninstall on Windows without rebooting the system. This is a Windows restriction.

This requires fixes from Apple on later versions of OS X.The crashes do not occur on 10.8, even though it is the same driver.