Visual Studio 2022 has stopped showing errors and intellisense

Question

Visual Studio 2022 has stopped showing errors and intellisense

Dave Barnard 70

For the last 7 days Visual Studio 2022 no longer shows red squiggles under any errors in the IDE text editor and no errors in the Errors List window. If I try to build it fails and I can see the errors in the Output window, but no errors are listed in the Errors List window. It has also stopped showing or responding to any intellisense commands. I have the Show error squiggles option under Tools -> Options -> Text Editor -> General, enabled.

I've attached a screenshot and gif showing the problem VS2022 - no errors2

VS2022 - no errors

.

Matt MacDonald 25 Reputation points

2024-07-25T12:41:39.2566667+00:00

This has been happening for me as well since the latest update. The only way I've found to work around it is to use "Build Only", or try to find the errors in the output log after a build. Otherwise I just get "Build Failed" if there are errors, but no indication as to what they are. I am not working off of a network share. However, in my case, the errors show if I have the file open that has the error, but not if the error is elsewhere.
Andrey Talanin 0 Reputation points

2024-11-01T23:21:41.0533333+00:00

Visual Studio 2022 Community 17.11.5, the same issue here without extensions, as well as with them. Changing the error source to "Build Only" shows the errors, "Build + Intellisense" does not.
edward 10 Reputation points

2025-01-08T11:12:30.9933333+00:00

I experienced the same problem. I had error squiggles in VS Code, but the error squiggles weren't showing in Visual Studio, even though I had all the necessary tools enabled. Then, I found the solution: I had to open the project folder through file ->open -> project/solution -> and then open the .sln file in the project folder. This made the squiggles work right away
edward 10 Reputation points

2025-01-08T11:13:00.0733333+00:00

I experienced the same problem. I had error squiggles in VS Code, but the error squiggles weren't showing in Visual Studio, even though I had all the necessary tools enabled. Then, I found the solution: I had to open the project folder through file ->open -> project/solution -> and then open the .sln file in the project folder. This made the squiggles work right away
Anthony Griggs 5 Reputation points

2025-11-14T14:45:36.0533333+00:00

I am experiencing the same issue within .razor pages using Blazor WASM. Blazor WASM has always been a #hotmess with hot reload. But this is a whole other level and is making it practically unusable and absolutely killing dev time! It's like the .razor pages no longer recognize the @code{} blocks anymore? Thus as reported here intellisense doesn't work. Errors are no longer flagged... really nothing works. It's become a dumb text editor suddenly!

6 answers

Your answer

Matt MacDonald 25 Reputation points

2024-07-25T12:41:39.2566667+00:00

This has been happening for me as well since the latest update. The only way I've found to work around it is to use "Build Only", or try to find the errors in the output log after a build. Otherwise I just get "Build Failed" if there are errors, but no indication as to what they are. I am not working off of a network share. However, in my case, the errors show if I have the file open that has the error, but not if the error is elsewhere.
Andrey Talanin 0 Reputation points

2024-11-01T23:21:41.0533333+00:00

Visual Studio 2022 Community 17.11.5, the same issue here without extensions, as well as with them. Changing the error source to "Build Only" shows the errors, "Build + Intellisense" does not.
edward 10 Reputation points

2025-01-08T11:12:30.9933333+00:00

I experienced the same problem. I had error squiggles in VS Code, but the error squiggles weren't showing in Visual Studio, even though I had all the necessary tools enabled. Then, I found the solution: I had to open the project folder through file ->open -> project/solution -> and then open the .sln file in the project folder. This made the squiggles work right away
edward 10 Reputation points

2025-01-08T11:13:00.0733333+00:00

I experienced the same problem. I had error squiggles in VS Code, but the error squiggles weren't showing in Visual Studio, even though I had all the necessary tools enabled. Then, I found the solution: I had to open the project folder through file ->open -> project/solution -> and then open the .sln file in the project folder. This made the squiggles work right away
Anthony Griggs 5 Reputation points

2025-11-14T14:45:36.0533333+00:00

I am experiencing the same issue within .razor pages using Blazor WASM. Blazor WASM has always been a #hotmess with hot reload. But this is a whole other level and is making it practically unusable and absolutely killing dev time! It's like the .razor pages no longer recognize the @code{} blocks anymore? Thus as reported here intellisense doesn't work. Errors are no longer flagged... really nothing works. It's become a dumb text editor suddenly!

Answer 1

Matt MacDonald 25

This had been working for a while, and now suddenly started with the same behavior as before. Builds are failing, but nothing errors are shown in the error list if it's set to "Build + IntelliSense". If I switch to "Build Only" I can see the errors, but only after a build. It won't show any syntax errors just from loading the project. This started happening again a few days ago. I am fully up to date using VS 2022 17.11.2.

J A 0 Reputation points

2024-09-06T04:49:45.76+00:00

I am having the same issue immedately after starting a new project in 17.12.0 Preview 1.0
Kyaku Kumo 0 Reputation points

2024-10-18T07:59:56.8733333+00:00

Same issue in 17.11.5

Use “devenv /ResetSettings”,it work, but it happend again next day.

Answer 2

Tre4b 161

I came here looking for a solution to the same thing. I have found if I change the view to Build only I can see the errors. If I have the view as Build + Intellisense then the errors do not show.

This has only recently started happening so possibly with a recent update?

Answer 3

Anonymous

I am trying this on 01/28/2025 and none of the suggestions are working for me. It is a Visual Studio bug. Microsoft needs to fix this.

I uninstalled or disabled every extension I had. I reset settings, I opened the project / solution through the Open command. None of these steps made any difference.

Microsoft, please figure this out.

Answer 4

Anna Xiu-MSFT 31,186 Microsoft External Staff

Hi @Dave Barnard ,

Welcome to Microsoft Q&A!

Please try the following:

Update your VS2022 to the latest version with Visual Studio Installer and launch it again.
Enter “devenv /ResetSettings” at Developer Command Prompt for VS 2022 to restore your Visual Studio default setting.
Close all running VS instances and delete the hidden .vs, bin and obj folders in the project folder.
Rebuild the project.
Create a new project and check that it works properly.
Ensure you are using "Build + IntelliSense" in the Error List window.

User's image

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.

Dave Barnard 70 Reputation points

2024-05-10T08:00:46.75+00:00

Hi Anna Xiu-MSFT,

Thank you for your quick response. I tried resetting my VS settings with "devenv /ResetSettings" from a VS Dev Prompt, deleting all my .vs bin and obj folders, rebuilding my solution and creating a new project. I've confirmed I have the latest available VS version. Unfortunately the behaviour is still the same in new and existing projects - I've attached new screen shots.

Kind regards,

Dave
Anna Xiu-MSFT 31,186 Reputation points Microsoft External Staff

2024-05-10T09:29:24.8+00:00

Did you have any third-party extensions installed?
Dave Barnard 70 Reputation points

2024-05-10T14:09:25.3566667+00:00

I do, but I disabled them before restarting and got the same behaviour.

I've also just tried uninstall and re-installing VS2022 completely, and the behaviour is still the same.
Dave Barnard 70 Reputation points

2024-05-10T15:40:48.5233333+00:00

I have a SonarLint extension installed, but I tried disabling that - it had no effect on the behaviour. I also tried uninstalling and reinstalling VS altogether - also no impact on the behaviour.
Pasan Jayasinghe 0 Reputation points

2024-05-12T13:31:45.92+00:00

Facing the same issue with C++
Dave Barnard 70 Reputation points

2024-05-14T08:14:32.58+00:00

Hi @Anna Xiu-MSFT do you have any other suggestions or feedback?
Anna Xiu-MSFT 31,186 Reputation points Microsoft External Staff

2024-05-14T09:33:07.2733333+00:00

Hello, sorry for my delay reply! I tried to reproduce the issue on my side, but it works fine.

Have you tried to run the VS as administrator?

If it is the same, could you install another edition of VS to check it again?
Pasan Jayasinghe 0 Reputation points

2024-05-14T11:22:46.7233333+00:00

For me, I deleted my build folder (including the .vs folder) and rebuild the whole thing and now it seems to work fine.

Answer 5

Vivek Reddy Sripathi 5

Please check this. It helped me.

https://learn.microsoft.com/en-us/answers/questions/1722865/vs-2022-not-showing-red-squiggles-under-errors-whe

Share via

Visual Studio 2022 has stopped showing errors and intellisense

6 answers

Your answer