1,934 questions
Does visual studio crash with a new windows forms app? Does deleting the hidden .vs folder in your solution that is crashing directory help?
Visual studio Not Responding
![](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(172.8, 50%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
mm ss
6
Reputation points
I had Visual Studio 2019 and it was crashes Always and shows not responding, but after "not responding" message, it goes good. Recently i upgraded to version 2022 and crashes It's in place.but in dotnet core windows forms app it crashes all of the time and don't get stable.
Please help me
Developer technologies | Windows Forms
Developer technologies | Visual Studio | Other
5,454 questions
Developer technologies | C#
11,578 questions
{count} vote
-
![](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(316.8, 9%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPA%3C/text%3E%3C/svg%3E)
P a u l 10,761 Reputation points2021-11-28T10:55:45.62+00:00 If you run VS in safe mode do you still run into the same issue?
https://learn.microsoft.com/en-us/visualstudio/ide/reference/safemode-devenv-exe?view=vs-2022If not then it could be due to an extension you have installed. Do you see any error when it crashes - if so could you copy/printscreen it & paste here? It's definitely worth checking Event Viewer for any related errors if you haven't already.
There's also an ActivityLog.xml that's worth checking too, if you navigate to this location:
%APPDATA%\Microsoft\VisualStudio, open the correct folder version (should be the one that begins with17_) and open ActivityLog.xml and see if there are any hints as to what's happening.If you're not able to identify the cause then you can report a problem to the VS support team & see if they can help you identify the cause.
Sign in to comment