Visual Studio 2019 constantly crashing

Question

Hi. I'm at my wit's end with this. I've used VS2017 for years, it was mostly solid. Just a few little quirks. I recently installed 2019 Community so I could use .NET 5 and it's nothing but headache after headache. It's laggy, has a lot more quirks (like toolbox taking 30+ seconds to load, component properties blank, last opened class totally blank when opening a project, etc) but the most aggravating is constant crashing. I've lost so much work to it. It crashes and in the event log I have two errors:

Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Microsoft.DotNet.DesignTools.Client.DesignToolsClientException
   at Microsoft.DotNet.DesignTools.Client.DesignToolsClient+<SendRequestAsync>d__49`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at Microsoft.VisualStudio.Threading.JoinableTask.CompleteOnCurrentThread()
   at Microsoft.VisualStudio.Threading.JoinableTask`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].CompleteOnCurrentThread()
   at Microsoft.VisualStudio.Threading.JoinableTaskFactory.Run[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Func`1<System.Threading.Tasks.Task`1<System.__Canon>>, Microsoft.VisualStudio.Threading.JoinableTaskCreationOptions)
   at Microsoft.VisualStudio.Threading.JoinableTaskFactory.Run[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Func`1<System.Threading.Tasks.Task`1<System.__Canon>>)
   at Microsoft.DotNet.DesignTools.Client.DesignToolsClient.Microsoft.DotNet.DesignTools.Protocol.Endpoints.IRequestSender.SendRequest[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.String, System.__Canon)
   at Microsoft.WinForms.DesignTools.Protocol.Endpoints.ToolStripInSitu.GetIgnoreMessagesEndpoint+Sender.SendRequest(System.Object)
   at Microsoft.WinForms.DesignTools.Protocol.Endpoints.WinFormsEndpoints+ToolStripInSituImpl.GetIgnoreMessages(System.Object)
   at Microsoft.WinForms.DesignTools.Designers.ToolStrips.ClientToolStripInSituService.get_IgnoreMessages()
   at Microsoft.DotNet.DesignTools.Client.Designers.PbrsForward.System.Windows.Forms.IWindowTarget.OnMessage(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)

and

Faulting application name: devenv.exe, version: 16.10.31321.278, time stamp: 0x60a85eca
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1023, time stamp: 0xcbf6f7d1
Exception code: 0xe0434352
Fault offset: 0x0012a6f2
Faulting process id: 0x2a48
Faulting application start time: 0x01d7566331a916e1
Faulting application path: C:\Apps\VS2019\Common7\IDE\devenv.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 5c4b4194-b42a-4328-9024-993ea5287035
Faulting package full name: 
Faulting package-relative application ID: 

I can't go more than 10 minutes before it blows up. I'm about to uninstall this garbage and go back to 2017 and just try to find an alternative to that for which I needed .NET5. Funny thing is I wasn't even aware community existed, I was ready to drop $500 on a 2019 Pro license before someone clued me in. I'd be livid if I had paid $500 for this hot mess.

So I'm doing a repair right now, but does anyone have insight into anything I can do to fix this?

Answer 1

I'm having the same issue. I get the identical stack trace and details in the event viewer. Same .dll and same exception code, same version numbers and same public key tokens.

I've tried the steps suggested above by Anna, but no luck.

My installation is in the default location on C:\

Mine will crash when clicking on a [Design] tab in the editor of a form. I've gotten to the point where I always manually save before clicking on those tabs because it crashes more times than not.

I have no extensions or nuget packages installed. The only configuration changes I've made from stock have been in the preferences of Visual Studio itself. Nothing external.

I'm using .NET 5 in the project's properties. The only other options are .NET Core 3.1 and 3.0. I've tried selecting those, but still end up with crashes.

It's solid as a rock as long as I don't go into the form designer. I can use the forms designer, it doesn't crash every time. But if it's going to crash, that's what does it.

Thanks,

Mike

Edit: Another bit that might be helpful - I've noticed that when I reopen the solution after a crash, sometimes the designer won't display properties for selected controls. I can click on them, and they'll appear to be active, with the appropriate resizing handles and such, but the properties panel on the right will be blank. Not blank properties, but no properties at all. I have to close the designer tab and reopen it to fix it. Could something in the rendering of the display be getting corrupted, crashing the editor, then fixed only by closing and reopening the tab?

Answer 2

Try -SafeMode. If the crashes do not happen in safe mode then you know it is an extension causing the problem.

Answer 3

Hi DougMatthews-8586,

Welcome to Microsoft Q&A!

Have you created a new project to check if there is the same issue?

The code 0xe0434352 usually means the exception of .NET Framework.
Please check the project target framework by right-clicking on the project > Properties. And try to change the target framework and check if the issue happens or not.

In addition to try the solution from SimpleSamples, you can repair your .NET Framework by using the tool:
https://learn.microsoft.com/en-us/dotnet/framework/install/repair

Sincerely,
Anna

• If the answer is helpful, please click "Accept Answer" and upvote it.
  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.

Answer 4

I had the same problem. I just tried something that worked for me. My solution files were on OneDrive. When the problem occurred, I tried all of the suggestions mentioned in this thread. Nothing worked. Finally, I copied my solution folder to my local drive (C:\tmp) and the problem went away. I was able to open a Form in the designer. Then interestingly, I copied the solution folder from my local drive back to the OneDrive, opened it in Visual Studio, and the problem went away. I was able to open the Form in designer. I don't know why it worked, but it did.

Answer 5

update a new one,haha