"The specified module could not be found." when attempting to use profiler in Visual Studio 2013

Chris Guin 21 Reputation points
2020-10-01T15:46:28.173+00:00

So I recently attempted to upgrade my copy of Visual Studio 2013 to the VS2019, but ran into some compatibility issues with some other software so for now I have uninstalled 2019 and reinstalled 2013. Everything seems to be working fine, except now, whenever I go "Analyze/Performance and Diagnostics," I get a weird error. The project launches successfully and completes, but once it's done, all I see is an error message:

Microsoft Visual Studio was unable to create a diagnostics report. Check Output window for errors.

The "Diagnostics Hub" in the Output window only shows "The specified module could not be found."

I have attempted running a repair of Visual Studio 2013, deleting my .suo file, and rebooting - no change so far. Any ideas for what I could do to get profiling back?

Thanks!

Visual Studio Debugging
Visual Studio Debugging
Visual Studio: A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.Debugging: The act or process of detecting, locating, and correcting logical or syntactical errors in a program or malfunctions in hardware. In hardware contexts, the term troubleshoot is the term more frequently used, especially if the problem is major.
909 questions
{count} votes

Accepted answer
  1. Tianyu Sun-MSFT 24,896 Reputation points Microsoft Vendor
    2020-10-02T05:53:50.897+00:00

    Hi Chris,

    Thank you for posting this issue in Microsoft Q&A forum.

    please try to close all Visual Studio instances and rename(or delete) every ComponentModelCache folders under this path: C:\Users\user name\AppData\Local\Microsoft\VisualStudio\12.0 and try to start Visual Studio 2013 as administrator, then test again.

    If this issue still persists, I’m not sure if this issue is caused by the missing of some corresponding files(modules) of VS 2013. You can try to uninstall and reinstall VS 2013.

    Besides, will this issue persist if you create a new simple project? Did it work well when you used previous installed VS 2013?

    Sincerely,
    Tianyu

    • If the answer is helpful, please click "Accept Answer" and upvote it.
      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.
    0 comments No comments

0 additional answers

Sort by: Most helpful