![]() |
Thank you. I had missed it. I am sorry.
|
Hello,
Any updates? Were you able to replicate this issue? |
Hello,
The identical thing as you has not been reproduced. We tested with a wider range of devices because we don't stock each device from manufacturers 7+ times (there are hundreds of devices and we are not notified of them all). Because the results were different, and the order had an impact, engineering has ordered the identical adapters in higher number to get the same setup. When they get to it and there is something tangible to say, I will post on that thread. Regards, Alban |
Hello,
After reproducing the bugs with the same setup as described and analysing it, our team has been able to reproduce this without DisplayLink driver loaded, by using the software GPU tool of Windows. We have handed over our findings to Microsoft. Kind regards, Alban |
Hello everyone,
I'm happy to report that this bug has now been investigated by Microsoft. We think the problem is understood and we will get a fix to check in the next few weeks. This fix will then go into Windows 10 Fall Creators Update. I will post when we have received the fix and when it becomes available through the Windows Insiders Program, if you wish to try then. Kind regards, Alban |
Hello,
We have verified that the OS is now fixed. We tested with 10 Plugable adapters on Windows 10 Fall Creators Update (build 16288) and all displays now work. That build is available through the Windows Insiders Programme. The official release for Windows 10 Fall Creators Update will be around 17th October. Kind regards, Alban |
| All times are GMT. The time now is 02:06 AM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2026, vBulletin Solutions, Inc.