Why do the diagnostic tools fail unexpectedly?
The primary cause for this is a known issue for those of you that have upgraded from an earlier preview version of Windows 10. If you are on Windows 10 you can confirm the issue by switching to the “Diagnostics Hub” tab of the output window, and you will see “No such interface supported” in the output. More information, including workaround steps to resolve this issue please read the post on No such interface supported in Visual Studio 2015 on Windows 10. Other causes of the window failing unexpectedly are being actively investigated, if you experience other failures please report these using User Voice.