The Mac people are pointing to this and trying to get me to move to Mac related editing. The dark side. I am not happy with all this running of the programs but atleast I can close them. How can Microsoft let such things happen.

From my experience this happens when you are primarily using an Intel gpu. When I used a desktop with an NVidia 1080ti (no igpu) this never happened, then for a while I switched to a laptop that only had an Intel Iris Xe gpu and Vegas would never close properly. Now I use a different laptop with an NVidia 3050ti and once again Vegas closes properly. As others have said it's a bug that has been there for many many years so I presume it will never be fixed.

For what it's worth I also have a Mac Mini M1 as I was trying out both Final Cut Pro and Davinci Resolve to compare to Vegas. In my normal use Final Cut Pro crashed the most in some cases multiple times in just one hour, for me it was the least stable of the three. Also my Dell XPS 9510 with an NVidia 3050ti runs Davinci Resolve noticeable faster than the Mac Mini M1 and has better render quality at the bitrates I use.

From my experience this happens when you are primarily using an Intel gpu. 

I don't think that this is a universal reason. My CPU, an Intel i9 10900KF, does not have an inbuilt GPU yet I get program "ghosts" in the Task Manager with the two current programs that I mentioned earlier.

Yeah, its somewhat a Vegas Memory leak issue that affects some users. You can us the script that Musicvid suggested, which is by killing all instances of Vegas from your system once you close it.

Yeah, its somewhat a Vegas Memory leak issue that affects some users.

Just curious. Why then does the same thing affect other non-MAGIX programs? But perhaps they also have memory leaks.

Pretty sure it's a plug-in that prevents proper closing. FWIW I don't have this issue and have an Intel iGPU.

Final Cut X is a great program, I've used it before. Others in my film school had catastrophic crashes with it losing projects so I was very careful with my backups (and never experienced problems). I had originally planned to learn video on Premiere, as I am experienced with other projects, but it was unstable on my system so I went to Vegas. Funny how things work out.

Yes @Dexcon, when any program has this problem, although it can be due to other issues as well, memory leak is often times the main cause for this.

Once in a while i had this issue back with Vegas 18, but not anymore with Vegas 19 on the same system, and i don't do windows updates.

My system with an Intel UHD 630 GPU also would hang on exit, Vegas 18 or 19. Unlike @RogerS, my system only had 16 Gigs of ram. I raised mine to 32 gigs, and I think it went away. I created another system with Intel UHD 730 and only 16 gigs and it has the hang problem.

The task manager shows the Intel GPU claims 7.9 Gigs of shared memory. Maybe that is part of the (many) problem(s) in an Intel-only system with only 16 gigs of ram.

Edit: adding another 16 gigs to my 2nd system didn't fix the hang issue

Odd, I had 8GB of ram for years.

If this only happens for some, or actually very few applications why would it be a Windows issue? Also, even if it is a Windows issue couldn't Vegas, upon exit have it's last command be to kill itself in task manager as a workaround until MS gets it sorted?

I recall this becoming an issue for users around the time of Vegas 8, released in 2007. It's been with us in various forms ever since. If it were as simple as some seem to suggest; well... carry on.

In the past 20yrs i've had 4 PC's, i've always maxed out the amount of Ram, & have had this occasional problem with different programs, the problem always seems to go away by itself, prob with updates but it's so varied & inconsistent i never have worked out why, on this PC just a couple of times Vegas has prevented shut down of the PC. 🤷‍♂️🤷‍♂️

I recall this becoming an issue for users around the time of Vegas 8, released in 2007. It's been with us in various forms ever since. If it were as simple as some seem to suggest; well... carry on.

Since there is a script to kill all Vegas processes the solutions is simple and actually exists. Vegas could run such a script on the way out;)

Since there is a script to kill all Vegas processes the solutions is simple and actually exists. Vegas could run such a script on the way out;)

Absolutely. Here's the powershell command I issue from a shortcut:

%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe "taskkill /IM vegas180.exe /F"

Btw, I only see the issue on a single machine: my laptop which has both Nvidia & Intel igpus. Do not see it on machines with Amd + Intel igpus like a Nuc. Or on machines with Amd + Nvidia discrete gpus or machines with Amd gpu + Intel igpu.