VS 2019 has started hanging, a LOT!

Rod At Work 866 Reputation points
2022-02-08T21:37:42.233+00:00

So far, I've fought, and lost, this battle all morning. And it's continuing into this afternoon. I've remoted to my work desktop to do editing on some files. When I opened VS 2019 it shows me where I was at when I last edited the file. I see that the .csproj file has some changes which haven't been checked in yet (we use TFVC). I want to see what those changes are, so I click on the Team Explorer.

And that's it. Nothing after that. VS 2019 is hung. I've closed VS 2019, then reopened it. Same behavior. I've rebooted the desktop, then opened VS 2019, same behavior. I've rebooted the laptop I'm using to remote to my desktop to try and make this work. Same behavior. I've looked at Event Viewer. There is nothing there, until I forcibly close VS 2019, then there's an entry in Event Viewer saying that VS 2019 was hung. The only thing that's in it which might be useful is this entry:

The program devenv.exe version 16.11.32106.194 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

This is a showstopper. I cannot do my job. I'm not sure where the Security and Maintenance control panel in VS 2019 is. I need some help, please

Developer technologies | Visual Studio | Other
0 comments No comments
{count} votes

5 answers

Sort by: Most helpful
  1. Michael Taylor 60,326 Reputation points
    2022-02-08T21:55:54.497+00:00

    Firstly, does anyone else have this problem where you work?

    Have you tried disconnecting and reconnecting to your team project in VS?

    Delete the .vs folder in the solution and see if it recovers.

    Does the command line tf tool work?

    Run VS in safemode using the /safemode flag. Does it work now? If not then include the /log <file> option so it writes an activity log. Then take a look at the output.

    If none of that works then use Report a Problem in the top right of VS and send the information to MS so they can look into the issue.

    1 person found this answer helpful.
    0 comments No comments

  2. Rod At Work 866 Reputation points
    2022-02-08T23:18:02.787+00:00

    Hi @Michael Taylor , thank you for your suggestions.

    Others haven't reported having this problem.

    I don't know how to disconnect from a team project, then reconnect again, in VS 2019. How is that done?

    I've deleted the .vs folder and am testing that now.

    I'm familiar with git at the command line, not tf. I'll try it now...
    ... the tf command at the command line isn't recognized by PowerShell.

    I'll test the rest tomorrow - gotta run for another meeting. :(


  3. Krammig 6 Reputation points
    2022-06-18T12:09:52.413+00:00

    VS 2019 hangs a lot for me since a previious update, although I cannot say which one exactly, I think it was two updates ago.

    Microsoft Visual Studio Community 2019
    Version 16.11.15
    VisualStudio.16.Release/16.11.15+32510.428
    Microsoft .NET Framework
    Version 4.8.03761

    I am mainly using Xamarin projects.

    Opening a project, after a short while it just hangs. Restarting the project sometimes hangs again, other times it opens Ok.
    On other occasions it will just randomly hang somwhere.

    HP i5 16GB Ram
    1TB SSD
    Windows 7 Ultimate

    0 comments No comments

  4. Ken Tucker 5,861 Reputation points
    2022-06-18T14:18:06.643+00:00

    Do you have any visual studio extensions installed? Did you try disabling them if you do? If you look in windows task manager is the CPU or memory maxed out when vs hangs? It could not hurt To add antivirus exclusions for devenv.exe (visual studio), and the directory your source code is in.

    0 comments No comments

  5. 블๑Albert Zakhia 1 Reputation point
    2022-09-02T14:44:39+00:00

    We are the 2nd of September 2022, and this problem persists!

    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.