To reiterate what I have said previously within this thread, for anyone experiencing unexpected behavior using DisplayLink Manager version 1.10, if you have not do so already, I would suggest reporting the issue to DisplayLink directly by following the process outlined here -->
https://support.displaylink.com/know...to-displaylink