"Feature 'XXX' is currently unavailable due to an internal error."

Nathan Sokalski 4,111 Reputation points
2021-12-25T04:05:33.293+00:00

Visual Studio 2022 recently started (for absolutely no reason) displaying the following message(s) at the top of the Visual Studio 2022 window:

Feature 'Diagnostic analyzer runner' is currently unavailable due to an internal error.

Similar messages are displayed for many other features (the list is endless!). This started happening for no reason, I did not change (or even open) the settings or preferences, I did not create (or even edit) any files, I did not install any updates, I barely used my computer. Here is a screenshot of the messages:

160270-screenshot-2021-12-24-225853.png

If I close all the files, it sometimes lets me click the X on the right to get rid of the messages, but then they come back when I reopen the files. What is the problem? I have not tried to repair Visual Studio 2022 (that is, in my opinion, a last resort, since it doesn't always fix the problem). I currently have:

Microsoft Visual Studio Community 2022 (64-bit)
Version 17.0.4

Developer technologies | Visual Studio | Other
{count} votes

20 answers

Sort by: Most helpful
  1. Nathan Sokalski 4,111 Reputation points
    2021-12-26T16:17:02.91+00:00

    I finally resorted to using Repair, and it (supposedly) fixed it, so I guess I'm good for now, but just as a suggestion/reminder to others, if you can find any other way, use it, because as most of us know, reconfiguring all the settings & configuration of Visual Studio is a major pain, even if you do export & import the settings. I'll consider it fixed (or repaired) for now, but it would still be good to know what happened & how else I could have fixed it for the future.

    1 person found this answer helpful.
    0 comments No comments

  2. Ernie Banzon 5 Reputation points
    2023-03-11T19:53:48.84+00:00

    I have 17.5.1 and it's started misbehaving after I updated to this version. However, I tried running in administrator mode and it worked! At least for me.

    1 person found this answer helpful.

  3. Ken Tucker 5,861 Reputation points
    2021-12-25T22:40:16.823+00:00

    I would do a repair on visual studio 2022. If it is still happening after you do the repair I would disable any visual studio extensions you have installed to see if that fixes the issue

    0 comments No comments

  4. Martin Kariuki 1 Reputation point
    2022-11-26T08:15:57.823+00:00

    I closed my project and restarted again. The issue was gone , at least by the time I am writing this feedback.


  5. Devon Lehman 16 Reputation points
    2022-12-05T18:20:26.027+00:00

    Lately it's been fine for me on 14.0.0. I saw a post saying this was addressed in 14.0.2, so i updated. The next solution i opened it immediately happened again so i rolled back to 14.0.0

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.