This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 28.999999999999996%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
During debugging, nothing is displayed in the diagnostic tool window
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(176, 46%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMW%3C/text%3E%3C/svg%3E)
I have run into the same issue, diags not working not showing anything. I have tried restarting the service, does not start. Tried repairing VS, to no avail. Still diags are not working.
Rolling back to prior versions for now. Build tools rolled back fine. VS encountered errors, but on restart, I'm not positive some of that was blocked by perhaps needing the Windows Service removed, which happened on restart. Repairing to rolled back version now... Fingers crossed.
After some trials and tribulations, decided to roll back to 17.11.4, and after a restart (which cleared the Windows Services cache), and repair, that apparently fixed it.
Current assessments based on the available information, it seems like the 17.11.5 migration is borked somehow in the aforementiond manner. Or may be sensitive to whatever other preconditions, maybe an SDK is necessary, I don't know exactly. Maybe there are some release notes behind it I am unaware about.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 10%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAX%3C/text%3E%3C/svg%3E)
Hi @永达 文 ,
Welcome to Microsoft Q&A!
What is your project type? If you create a new project, does the Diagnostic Tools window appears normally?
Please try to update your Visual Studio to the latest version and reinstall the “.NET profiling tools” in Visual Studio Installer > Modify > Individual components.
Sincerely,
Anna
*
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Thank you for your answer.
My project type is ASP.NET Web API, the creation of a new project is still the same, and the Visual Studio version is up to date (17.4.3).
I also tried to reinstall the ".NET profiling tools", but the problem remains the same, but I also installed Visual Studio 2019, which will display the Diagnostic tools properly.
Can you find the “ASP.NET Core” overview page when creating a new ASP.NET Web API project? If you can’t find it, please refer to the similar issue and check if the webview2 is installed. You can also try to reinstall the webview2.
Sorry, I don't quite understand your reply.
I can see the ASP.NET Core overview page, WebView 2 has also been installed.
My problem is that the diagnostic tool does not display properly during debugging, as in my previous picture.
Hello, this is the "ASP.NET Core" overview page:
Yes, I see it, but that's not my problem.Except for the ASP.NET Core project, none of the other projects will display Diagnostic tools normally, only an empty form with nothing in it.
Including the Performance Profiler, the generated analysis reports are blank!
Sorry for my delay reply!
Can you check if the installed extensions affect? Please temporarily disable or uninstall the installed extensions under Extensions > Manage Extensions > Installed.
If it persists, you can try to reinstall VS2022.
It doesn't matter. I've tried what you said, including reinstallation, many times, but the problem still exists. I have asked the question in the Developer Community. By checking the log, the engineer suspected that it was caused by webview2, but there was no clear answer.
Have you tried to reinstall webview2? You can also update your VS to the latest version and check again.
I tried to reinstall WebView2, but the problem remained the same
I tried to reinstall WebView2, but the problem remained the same
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(195.2, 22%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EO%3C/text%3E%3C/svg%3E)
You need to enable the service (under the Services tool setting it to automatic and restarting VS):
VSStandardCollectorService150
Visual Studio Standard Collector Service 150
Visual Studio Data Collection Service. When running, this service collects real-time ETW events and processes them.