This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(86.4, 84%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECJ%3C/text%3E%3C/svg%3E)
I am using Visual Studio 2019. I have 64 gb of ram, use 1tb NVMe drives, 12 core 4.10 GHz processor, Windows 10 OS. And even with this decent machine, Visual Studio hangs and freezes very often. I am a programmer by trade, I code at least 8 hours a day and I'd say Visual Studio locks up, stops responding around 5 times per day and randomly crashes and restarts itself around 3 times per day. The crash/restarts don't come with a hang or any warning at all. The program just completely and instantly closes itself with no warning at all. When the program freezes, in the device manager, Visual Studio will often be consuming >50% of my CPU and >33% of my RAM - which seems like a lot given my machine. I generally give the hangs about a minute to try and resolve themselves. Maybe 10% they actually resolve themselves and I can continue on. 50% of the the time, it hangs for over a minute and I have to end task in task manager. The rest of the time, it crashes after hanging for a bit. I have notices that in the rare chance that the program recovers by itself, it often feels less stable afterwards - slow to respond, much slower to think about things, delayed typing (press keys and they don't show up on screen for a few seconds, then appear all at once). Sometimes it gets like this without any hangs first. When it gets like this, I end up killing visual studio and restarting it to try and get back to a usable state.
I code unreal engine projects mostly and use the engine source so my projects are always rather large. The only plugins I use are Visual Assist and CodeMaid but the crashes/hangs happen without these plugins as well.
What can I do to make my Visual Studio more stable? These crashes and hangs are very disruptive.
P.S. the tag system on this forum is really frustrating and unintuitive to use. The user should be able to see all available tags or add their own. Or there needs to be a smarter lookup. I tried tagging this issue with 'crash' 'hang' 'unresponsive' 'visual studio' 'vs2019' and a few others and none of them were valid tags and it gives you no clue what tag it does have that might be similar. I ended up having to search for similar issues on this site to this one and see what tags they used. I had to use 'vs-general'. For your system to guess what tag you're trying to add, you have to give at least 3 characters (why? you can do better. It should guess from the very first character.) Do you see the problem? Provide 3 characters? 'vs-general'? How on earth is someone supposed to guess that the magic 3 characters they need to type in is 'vs-'? Please do better.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 56.00000000000001%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDW%3C/text%3E%3C/svg%3E)
Same here. Frequent freezes for me. I run VS all day long and have maybe 2-3 freezes per hour. They last a few seconds to 30 seconds, greatly disrupting my flow. This is all C# development, pretty simple stuff. Repairs and updates do not help. And, like with the lame answer below, none of the bots at Microsoft recognize the issue.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 68%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAP%3C/text%3E%3C/svg%3E)
Same here. January 3 2022 and this problem keep persisting.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 0%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
Exactly the same here. It freezes randomly when you open solution and during the debug in most of the cases. Nothing works to fix this issue.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 95%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEM%3C/text%3E%3C/svg%3E)
Same here. I run VS 2019 all day long and have maybe 2-3 freezes per hour.
It happens more frequently if I visualize/interact with large files, but I did the same with VS2017 and VS 2015 without any freeze + reboot.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 38%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJB%3C/text%3E%3C/svg%3E)
After having this issue for several months I seems to have found a solution unrelated to Visual Studio which I am posting in case this assists anyone. I am running Visual Studio on a Windows 10 Vmware Fusion virtual machine on a Mac. After struggling to find a solution I started looking at the virtual machine settings and in desperation decided to increase the shared graphics memory without expecting it to make a difference and to my surprise it seemed to resolve the issue. To my knowledge the setting had been what it was before I changed it for as long as I have had the machine, which is several years, and the issue only started a few months ago so there was no reason to expect this setting to be a factor. Nothing on any Vmware, Windows or Visual Studio forum gave me this answer I just stumbled on it by chance.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(182.40000000000003, 28.999999999999996%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
VS 2022 locks up frequently; .NET 6, 24GB RAM, SSD with lots of space, Intel I5.
Microsoft, this needs to be fixed ASAP. The product is unusable.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 91%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDC%3C/text%3E%3C/svg%3E)
Same issue here. It is VS-2022 with version 17.1.2.
I have to restart VS in every 10 minute. sometime key pressing also become very heavy operation and complete VS unresponsive.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 3%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Same problem with VS2019 16.11.18 on Windows 11
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 63%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
I had this problem and it was fixed after I changed a UEFI setting from power saving/quiet mode to performance mode.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(195.2, 91%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPP%3C/text%3E%3C/svg%3E)
Using VS Community 2022(64-bit) v17.2.0 and it crashes after about the 3rd or 4th run of my code every time. I'm just taking a tutorial and code is super basic. Should I downgrade to 2019?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 67%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAE%3C/text%3E%3C/svg%3E)
I found the following in my search, which seems to have solved the problem for some VS 2019 users:
https://msicc.net/how-to-work-around-ide-freezes-in-visual-studio-2019-when-switching-between-build-configurations/
My VS 2022 (admin mode) still freezes without warning and I don't find a pattern. CPU usage is under 1% and RAM usage 1,7GB.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 4%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPW%3C/text%3E%3C/svg%3E)
I've been dealing with VS2019 constantly freezing/hanging for a year now. It's getting really old. At one point, I deleted AppData/Local/Temp and that fixed it. Another time I freed some extra HDD space and that fixed it. Now, none of that works - 100G of free space and still have this problem.
I've spent countless hours trying to debug this issue with no results at this point. I've followed the very many suggestions here, from toggling options on and off, disabling all extensions (that is really not a solution, BTW - it is the equivalent of saying "just remove all the rear view mirrors from your car, then you will be safe"...), making sure virus scanning omits the project folders, etc.... I've got 8G RAM and 1T SSD.
My current situation is that VS2019 now freezes for 10 seconds literally three times every minute. Yes, half of each minute I spend with this software is wasted while waiting. Sometimes I get the white-screen overlay and "Not Responding" message but usually it just freezes. The keystrokes are not all cached. As I type "through the freeze" stuff gets lost when it un-freezes.
I'm at the end of my rope here. I was going to switch to VS2022, but judging by the comments, it is just as bad or worse.
Does anyone have any kind of useful suggestion here? I'm on Win10 and VS2019 16.11.20 (latest version as of today).
Really sad to see that so many other people have this issue....
I waited a while and didn't upgrade to VS2022 until a month or so ago. I'm on newest MacOS (13.0.1).
When I start debugging things run fine for some time. Then it suddenly shows the rainbow coloured wheel and hangs. I can then force-quit it. But it doesn't really recover until I have restarted the computer. Even tried a very small app after a force quit - but it hang almost instantly again.
/John
Really sad to see that so many other people have this issue....
I waited a while and didn't upgrade to VS2022 until a month or so ago. I'm on newest MacOS (13.0.1).
When I start debugging things run fine for some time. Then it suddenly shows the rainbow coloured wheel and hangs. I can then force-quit it. But it doesn't really recover until I have restarted the computer. Even tried a very small app after a force quit - but it hang almost instantly again.
/John