@bitman - I missed that? Where is that?

@Grazie Eh you are joking right? Uninstall Firefox like you uninstall any program through windows the normal way.

@bitman - Joking? Nope. I was wanting to know where/when you’d asked me to uninstall FF? I do know how to uninstall a Program.

Why FF should be uninstalled? This change nothing. It is just local html file. Many programs these days create logs as html because they are more readable by human as they might have some formatting as headers, bold, tables etc. FF is just default program associated with these files on that system (in my case it would be PaleMoon, on other it might be Google Chrome, IE, Edge etc). If uninstalled, another program will be associated with the file but it change nothing with a way how the the local file is created.

P.S. I do not have such issue on Win 10 with VP15.

@bitman - Joking? Nope. I was wanting to know where/when you’d asked me to uninstall FF? I do know how to uninstall a Program.

@Grazie I understand your confusion & question now, my fault, I used the word "already" which I suppose implicates I asked something before (which I obviously did not). Sorry, English is not my native language.

@fifonik Well it is just a long shot as Grazie had issues in another post with Vegas files being associated with FF.

Yes, this is a real issue where an unwanted VEGAS process hangs around. It's actually a very old one that we've discovered stretches way back several versions. It mostly affects Win 7, but as Marco reports, it can also happen on Win 10. We're looking into it and hope to fix it in a future update. For now, I'm afraid the workaround is that which has already been discussed: kill the rogue process in Task Manager before attempting an install. Hopefully now that we all know about it, we can help other users here who stumble across it. Thanks for reporting and discussing so that we could find it.

@gary-rebholz - Thanks for the reassurance. I was concerned that my work would NOT be saved with killing the process in TM. What’s odd is that the behaviour had only surfaced after I installed this recent Build. Is that helpful?

Same to me. Vegas still running after exit. (last build)

Same happening here. Just purchased upgrade to Vegas Pro 16
(I’m on windows 7). When I close Vegas Pro, having opened and closed with
various projects, there are loads of vegas160.exe still running in task
manager. I noticed it because when I tried to eject my audio interface and shut
down my computer, it reported a programme was still running which was using it.
Turned out to be several instances of vegas160.exe still running in the task
manager. So I’m having to force shutdown. Or stop all the vegas160.exe in task
manager manually. Please fix this.

Please fix this.

Acky, please refer to the post 3 above yours … the MAGIX Vegas Pro development team has already advised:

We're looking into it and hope to fix it in a future update

Thanks Dexcon.

Here's hoping this gets sorted out.

Are you mixing metaphors? I don't think Vegas has a smell. If it did, I assume it would smell like coffee.

Please fix this bug, it is really annoying! Amount of my RAM is limited. :(

@OldaC - Yes . . Just had it again whilst working hard on a Tutorial. I had to again kill VegasPro in WTM. It gobbles RAM and leaves me unsure and queasy about what damage is being done to my work. And again, for me this ONLY appeared in the latest Build, along with that FireFox HTML taking up residence in my TEMP folder.

@Grazie

Your theory. (other thread) makes perfect sense to me.

My version is 14, and about the same as VP8 in the memory dept (kind of acceptable). I don't have much RAM, so my save-restart-render ritual has been the same for seventeen years. Back then, I was convinced that buffer overflow was the problem, owing to the nature of the freezes and blue screens (then on Win98SE and Vista 32).

So yes, our minds our running parallel. Again. And Autosave behavior in newest build may have reintroduced poor buffer regulation. The nature of all the inconsequential things that go into buffer memory may warrant a fresh look, too.

Please, fix this bug.

Please, any news about this issue??? It is really boring to killing Vegas processes. :(
Thank you very much!

See -> here.

I'm using WAAG's Vegas "Save 'n Kill" Tool working well.

Haven't commented yet because it has not shown up on any of my Win10 machines. But I recently fired up an old Win7 machine that never had v16 on it before. Only up to v14. But after installing v16.424, it started hanging for the 1st time ever after doing only a handful of successive renders. Glad I remembered seeing this thread. Investigated and there's more. Looks like it's not what folks once called a memory leak... those processes might not be dead. Documented it with a video... it's a little crude and occasionally I get tongue tied.

@Grazie Do you still have the issue now that you have your new beast (which I presume runs on windows 10)?

@gary-rebholz I never had the issue on windows 10, but if it helps I forgot to mention, I always disable any autosave. I always save manually in any application. Regular manually saving has become second nature to me as a gamer (and even at work).

@Howard-Vigorita Interesting, I observed the TCP connections for Vegas 16 on windows 10: you can do this via the taskmanager, then tab performance, next open resource monitor (bottom left of window) , next select network.

After opening Vegas, you see a few connections (license check?, upgrade offers?), but then after a brief period all is cleaned up.

@Grazie to you still have the issue now that you have your new beast (which I presume runs on windows 10)?

@bitman - No and yes.