Good evening Pysco,

I have created the case to Microsoft and added the repro steps from the other people I had.
I'm flagging this to their graphics team in my (weekly) meeting with them tomorrow so my bug report is directed to the right team. I see it's passed the first stage and is now pending triage.

They may give me a script to gather information for them to investigate, but the detailed called stack provided may be sufficient.

Kind regards,
Alban

Bug tracked at Visual Studio Connect
 

Hi,

the issue is also tracked at Visual Studio Connect:
https://connect.microsoft.com/Visual...etails/3101540

I've flagged this up to the Microsoft graphics team.
They don't see how this could be a DisplayLink problem and they are contacting the Visual Studio people to look into the bug I raised to them before.

Thanks!

I hope it will be fixed before RS2.

:-)

Hello,
I will ask tomorrow but I would expect this to be linked to Visual Studio not dealing with this new OS feature correctly rather than the OS as otherwise all other applications would trip on the carpet the same way.

On VS Connect, MS asked for logs. I'm not sure anyone who has a reproduction has chimed in, yet, but I think it would be helpful to get this progressed.
https://connect.microsoft.com/Visual...etails/3101540
My ticket to the Microsoft Sysdev portal has not been looked at yet.

Kind regards,
Alban

Hello,
Our bug report has been handed over to the Visual Studio team. I've been told they should now have an internal reproduction of the crash to debug it.
MS graphics team did not see how DisplayLink driver could be the root cause and they explained to the VS team the change made in the new Windows 10. I understand that doesn't really help the immediate resolution of the problem, but we have assistance and interest from within MS, and that is always helpful to get a solution. DisplayLink also uses VS.
Kind regards,
Alban

Hi Alban,
Thanks for the update :-)

Best regards,
ckruhs

Hi everyone,

I have some news. A solution has been found and we are discussing how this can be rolled out.
Unfortunately, this is not a VS fix but an OS fix. If you could tell me how many people are affected in your organisations, this would be most helpful for me to explain why this should be serviced in build 14393 as opposed to wait until the next OS version.
I already got that DisplayLink is losing business over this as some of you have been buying the non-universal TB2 solution instead of the universal USB one...

Kind regards,
Alban

Hi Alban,

we are a Microsoft Gold Certified ISV Partner with 20+ developers.

Best regards
Carsten

Hi!
We have only 6 developer. But it's currently stopped us to use DL things. We have to do our development with only one direct connected HDMI monitor instead of two.