Windows 7 diagnostic tools not working

Collectives on Stack Overflow. Learn more. Visual Studio diagnostic tools no longer working Ask Question. Asked 5 years, 4 months ago. Active 1 year, 7 months ago. Viewed 24k times. Community Bot 1 1 1 silver badge. Add a comment. Active Oldest Votes. Thank you. That fixed it for me. This did the trick! Just curious, are there references on MSDN that you may have found that lead to just deleting the. Andrew Laughlin.

Full disclosure: I work at Microsoft, specifically on the Diagnostic Tools team. Nik Nik 3 3 silver badges 9 9 bronze badges. There are no Error or Warning entries in the log. Yes, that corresponds to our check of whether or not CPU profiling while debugging is enabled for the OS. In your case since you are on Win 7 it is not supported. The graphs and memory tool should still work though. It's so easy to accidentally click the close button when you meant the pin button as they are so tiny and close together in VS.

Could you put the buttons a lot further apart? The Original Poster indicated that the diagnostic tools worked in a previous version. What happened e. In order to work while debugging we need multiple sessions, as we need to spin a second one up and shut down our first one each time you want to look at data to get the results. If we don't have overlap in the sessions we can and probably would miss events, making analysis impossible. We still allow you to use the "Performance Profiler" option which is the traditional collect a single trace and analyze.

Show 1 more comment. I had som issues with that a while ago. Frode Frode 3, 1 1 gold badge 20 20 silver badges 32 32 bronze badges. Enable diagnostics tools while debugging is checked. Will you use it in the future? As always, if you have comments or information to share about this topic, please take a moment to drop by the TechRepublic Community Forums and let us hear from you. Greg Shultz is a freelance Technical Writer. Previously, he has worked as Documentation Specialist in the software industry, a Technical Support Specialist in educational industry, and a Technical Journalist in the computer publishing industry.

For more information on these troubleshooting tools, see my articles: Better troubleshooting capabilities with Windows 7 Event Viewer Learn how to use the Windows 7 Resource Monitor for effective troubleshooting Track stability in Windows 7 with the Reliability Monitor One of the other tools that you can use is called the System Diagnostic Report , which is a part of Performance Monitor and can display the status of hardware resources, system response times, and processes on your computer along with system information and configuration data.

Editor's Picks. The best programming languages to learn in Check for Log4j vulnerabilities with this simple-to-use script. TasksBoard is the kanban interface for Google Tasks you've been waiting for. Paging Zefram Cochrane: Humans have figured out how to make a warp bubble.

Show Comments. I believe. I don't think it is a hardware based error. I get this error whenever I try to use the net diagnostic wizard. I attempted to start the service manually from the services windows and receive another message that says "The diagnostic policy service on local computer started and then stopped.

Please advise before I go completely bald from pulling my hair out trying to solve this problem. Thanks in advance 32 bit windows 7 enterprise on an IBM think pad 1. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.

I have the same question Report abuse. Details required :. Cancel Submit.