Visual Studio - Designer process terminated unexpectedly

After opening a project (new or old), Visual Studio displays a warning “Designer unexpectedly completed” (see the figure below). What can cause this error? And how to fix it?

enter image description here

+7
visual studio
source share
6 answers

I had a similar problem. I tried:

  • Clicking on reloading the constructor
  • Cleaning my solution
  • Restart Visual Studio
  • Visual Studio Repair
  • Uninstall and reinstall Visual Studio!

In the end, it was due to the graphics, as you mentioned.

I have hybrid graphics (Intel and NVIDIA) and I used NVIDIA for Visual Studio. Changed this for Intel and it worked.

If this helps, a screenshot of my NVIDIA control panel is below:

Before (broken):

Before (NVIDIA control panel set to NVIDIA)

After (working):

After (NVIDIA control panel set to Auto-select)

+2
source share

Launch Visual Studio As Administrator ~!

I had the same problem when I started working in Team Projects , so almost everything did not work, including the designer, the property menu, debugging, etc. (which is completely unusual for anything to cause all these problems, except for the Administrator. Privileges, probably in most cases).

I don't know why and what caused this, but at least it works.

0
source share

The graphics card was a problem for me. I have an external USB video with DisplayLink, and when I turned it off, the problems disappeared. in fact, it didn’t come back when I connected displaylink again.

0
source share

I had the same problem and it turned out that my Oracle VirtualBox was causing the problem. My Visual Studio runs in a virtual Windows 10 environment.

After I turned off "Enable 3D Acceleration" in the Display options, my Visual Studio Designer worked fine again.

0
source share

In my case, it was a problem using system brushes as ThemeResource . Yes, this is obviously a mistake, like other strange bugs in MS products. So I had to comment on them until I finished my project. I don’t know, maybe another factor, such as my graphics hardware, was not inefficient, but it does not free MS.

0
source share

Some people have found the file "c: \ program" that calls it, often created by a typo creating a log file. Check if this file exists, and if so, move or delete it.

0
source share

All Articles