![]() |
![]() |
#1 |
Junior Member
Join Date: Mar 2015
Posts: 4
|
![]()
Just got the Kensington USB 3.0 DisplayLink adapter. Pluged it in, and got an error message in the tray (screenshot attached). Came to this forum and saw that there is a Windows 10 Alpha driver. I used the Clean tool here to remove everything I already had and installed the Win10 Alpha driver. Still get the same error that's attached here.
|
![]() |
![]() |
#2 |
Junior Member
Join Date: Mar 2015
Posts: 4
|
![]()
And here's the support file I see included in other threads...
|
![]() |
![]() |
#3 |
Junior Member
Join Date: Mar 2015
Posts: 4
|
![]()
updated to Alpha 8 driver released today - still have same issue
|
![]() |
![]() |
#4 |
Member
Join Date: Jul 2010
Posts: 83
|
![]()
Hi bryan,
I believe you are also suffering from the issue commented on in this thread: http://www.displaylink.org/forum/showthread.php?t=63689 Thanks, Paul |
![]() |
![]() |
#5 |
Junior Member
Join Date: Mar 2015
Posts: 3
|
![]()
Think we all are, is there a view from DisplayLink as to when it will be fixed, as it is a show stopper for me?
I have just clean built to 10041, but get exactly the same results. Cheers Alastair |
![]() |
![]() |
#6 |
Member
Join Date: Jul 2010
Posts: 83
|
![]()
We are working on this at high priority right now. Unfortunately we're not in a position to give timescales for a release quite yet.
|
![]() |
![]() |
#7 |
Junior Member
Join Date: Mar 2015
Posts: 3
|
![]()
Thanks for the update Paul, I will keep an eye out on here for the next release.
|
![]() |
![]() |
#8 |
Junior Member
Join Date: Mar 2015
Posts: 4
|
![]()
newest alpha driver (v9 (7.8.62016.0)) has fixed this issue for me. everything is working great now. thanks!
|
![]() |
|
|