“No such interface supported” in Visual Studio 2015 on Windows 10
If you upgraded your Windows 10 machine from an earlier version of Windows 10, and are running Visual Studio 2015, this post describes a workaround to a known issue. If you installed Windows 10 cleanly, or upgraded directly from Windows 7 or 8.x, then there is no issue, feel free to skip this post.
Once again, thanks to the efforts of users filing bug reports with the Feedback tools in Visual Studio 2015, we became aware of a previously unknown issue with the Diagnostic Tools window when running on Windows 10 machines that were upgraded from preview Windows 10 builds. This issue will be fixed in an upcoming release, but for now there is a manual workaround that will get the Diagnostic Tools window running on Windows 10.
When you start debugging, the Diagnostic Tools window (Debug -> Show Diagnostic Tools) shows the following error message instead of displaying the diagnostic tools:
“The diagnostic tools failed unexpectedly. The Diagnostic Hub output in the Output window may contain additional information.”
If you then examine the Diagnostic Hub output from the Output window [Debug -> Windows -> Output -> Show output from: “Diagnostics Hub”] you will see the following entry:
“No such interface supported.”
The issue occurs when running Visual Studio 2015 RTM on Windows 10, if Windows has been upgraded in-place from an earlier version of Windows 10. The Windows upgrade process leaves files behind that interfere with the operation of the Diagnostic Tools window. This is not an issue if Windows was upgraded directly from Windows 7 or 8.x.
The workaround is to remove the out-of-date files. Before the files can be removed, you’ll need to take ownership of them, and grant yourself full permissions. Here are the instructions:
1. Close Visual Studio 2015
2. Open an Administrator Command Prompt
3. Enter the following commands:
takeown /f DiagnosticsHub.*
icacls DiagnosticsHub.* /grant %username%:F
del /q DiagnosticsHub.*
The final del command only produces output if the files were not there. If the files were not there, you have an unrelated issue.
After starting VS, if you’re debugging a supported project, the Diagnostic Tools window should now be working.
If the workaround doesn’t work for you, or if you’re seeing other bugs in Visual Studio 2015, please let us know via the Feedback tool. Once you’ve alerted us to the problem, try restarting Visual Studio as that can clear up some issues.