Hello Modena,
Unfortunately, DisplayLinkManager.log is missing from the package. I am unable to find why the monitor identification details couldn't be read.
The DisplayLink chip in this product is always using the DisplayPort output, even for the HMDI out . I am wondering if you're meeting the same root cause as another thread
I looked at.
I understand you thankfully now have a solution. Should you wish this looked into, I would welcome another set of logs with DisplayLinkManager.log.
Kind regards,
Alban