I had the same problem, for me it was due to the fact that I was not a local administrator on my development machine.
If I started Visual Studio under an elevated account that was a local administrator (shift + right click> run as ...), then the diagnostic session will begin.
source share