Hi Steve,

Thanks. I have built my own apps to do this (and more similar stuff).

I was just submitting this as an issue with v22.

Thanks again,

P.

This has been a minor annoyance for me since v18.

If you watch task manager for, say, 60 seconds or so, it should self-terminate.

In my case, on one PC it records an error in the the event log.

This has been a minor annoyance for me since v18.

If you watch task manager for, say, 60 seconds or so, it should self-terminate.

In my case, on one PC it records an error in the the event log.

Same here. I use killallvegas from tools4vegas.

I guess it is an individual issue. I just shut down VP22 B194 and it disappeared immediately in Task Manager.

So I would have to ask the OP, which version of Vegas Pro?

I do not have the issue at all on desktops... only on Intel laptops with Intel igpu and Nvidia mobile gpus. It was reported here and widely discussed when vp18 came out. My 1st reported workaround script was posted when vp19 failed to fix it. And again. And repeatedly whenever anyone else needs a workaround. The strange thing is that the powershell functions to search and terminate child processes are the same C-functions that get called by most Windows applications to exit... unless they intend to terminate and stay resident like device drivers. Or system hooks used by debuggers, performance monitors, spyware, malware, and viruses.

Btw, it's never been a problem for me on an Intel Nuc8 which has a dual-igpu i7-8809g cpu containing Intel hd630 and Amd VegaM igpus. So my theory is that it's an Nvidia-specific laptop problem. My signature has links to the powershell scripts I still use.

I don't have the issue on my notebook (iGPU). Only my desktop (Nvidia)

Both have identical software, codecs, and VC++ runtimes. The primary difference is the desktop is running the studio driver (v565.90), and has an Audient ID14.

I do notice that the WER dumps have a lot of amd64*.inf noise, and yes, I've been down the DDU road. No joy.

I am guessing it might be either a driver issue, or Vegas is using an unexpected method to self-terminate. Or a comination of both.

Vegas is the only software where I have this exit weirdness, though Sound Forge Pro 17 occasionally records BEX64 errors.

I am not using it to land aircraft, so I consider the errors annoying but benign.

I used to have this issue all the time on my desktop (AMD RX470 GPU, also Intel built-in).

It completely went away for the past year probably (YAY!)

And now it's back. Even when I close Vegas properly there still seems to be a process running, which is causing all sorts of mayhem if I forget to check that, since preferences I save while that background other Vegas is running, don't get saved. Grrr... :(

I'm running latest build for Vegas.

@RedRob-CandlelightProdctns It has been indeed been better last year, and indeed there are now recently moments it does not close properly, I experienced it to occasionally, but it is not easy to reproduce. When trying to force the issue to reproduce, it closes fine. So there must be something that triggers it, being something peculiar done in the editing or a plugin, some windows update, maybe some anti virus sw in the background acting up, who knows.