JamesH
I did another test last night with a different DisplayLink device using the same Surface Pro 3. Same problem so it doesn't seem to be tied to any particular DisplayLink device.
From the Bernie post (another sufferer) referenced in JP2015's post, I would suggest to replicate the problem you need a Surface Pro 3 with the latest display drivers from MS (November Update).
So who is going to fix this, DisplayLink or Microsoft? Or will we get the blame game?
|