Vegas Pro 19 has stopped working on shutdown

Cmin7669 wrote on 3/4/2022, 3:07 AM

Vegas Pro 19 has stopped working on shutdown: is there any answers to this problem?

I have reset, and un-installed, reinstalled.

Here is my system:

OS Name   Microsoft Windows 11 Home
Version   10.0.22000 Build 22000
Other OS Description    Not Available
OS Manufacturer   Microsoft Corporation
System Name   -----------------
System Manufacturer   System manufacturer
System Model   System Product Name
System Type   x64-based PC
System SKU   ASUS_MB_CNL
Processor   Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz, 3600 Mhz, 8 Core(s), 16 Logical Processor(s)
BIOS Version/Date   American Megatrends Inc. 2811, 27/05/2020
SMBIOS Version   3.2
Embedded Controller Version   255.255
BIOS Mode   UEFI
BaseBoard Manufacturer   ASUSTeK COMPUTER INC.
BaseBoard Product   ROG STRIX H370-I GAMING
BaseBoard Version   Rev X.0x
Platform Role   Desktop
Secure Boot State   Off
PCR7 Configuration   Elevation Required to View
Windows Directory   C:\WINDOWS
System Directory   C:\WINDOWS\system32
Boot Device   \Device\HarddiskVolume5
Locale   United Kingdom
Hardware Abstraction Layer   Version = "10.0.22000.527"
Username   cvcvcvcvcvcvcvcv
Time Zone   New Zealand Summer Time
Installed Physical Memory (RAM)   32.0 GB
Total Physical Memory   31.9 GB
Available Physical Memory   27.2 GB
Total Virtual Memory   36.7 GB
Available Virtual Memory   29.9 GB
Page File Space   4.75 GB
Page File   C:\pagefile.sys
Kernel DMA Protection   Off
Virtualisation-based security   Not enabled
Device Encryption Support   Elevation Required to View
Hyper-V - VM Monitor Mode Extensions   Yes
Hyper-V - Second Level Address Translation Extensions   Yes
Hyper-V - Virtualisation Enabled in Firmware   No
Hyper-V - Data Execution Protection   Yes

Comments

Dexcon wrote on 3/4/2022, 4:01 AM

Vegas Pro 19 has stopped working on shutdown

Could you please more fully explain what has happened. Stating the obvious, Vegas Pro is not supposed to work after it's been closed because, well, it's been closed down.

You say that you've reset it, but that suggests that Vegas Pro 19 has opened again. Is that right? If yes, how did you get it to open again?

Cmin7669 wrote on 3/4/2022, 4:14 AM

Everytime I shutdown Vegas after I have finished working on my project, It closes, but I then get the Vegas has stopped working panel, with the send report or exit.

Dexcon wrote on 3/4/2022, 4:18 AM

Next time it happens, please check the 'show details' (can't remember exactly what its called), screen dump it and upload it to this thread. The more detailed info will show the error module.

BTW, I had that happen with Vegas Pro 19 a few times earlier today for no apparent reason. I rebooted the computer and the problem went away.

Cmin7669 wrote on 3/4/2022, 4:29 AM

Well, I have sort of fixed it by going into the program folder for Vegas and changed (renamed) the errorReporting.dll so it cannot call up that panel. I shouldn't have to do this, but it has been driving me mad. Magix really needs to get off their backsides and fix some of these problems.

Former user wrote on 3/4/2022, 6:05 AM

I've had that quite a few times, Close project, shut down Vegas but the Vegas has stopped working msg pops up, this has only started in the last couple of wks, it doesn't always happen tho & i can't find why it does & why it doesn't 🤷‍♂️

Cmin7669 wrote on 3/4/2022, 1:13 PM

Here is what I changed (see picture)

To use this fix first right click in the Vegas Pro 19 icon and click on "Open Flie Location"

This will take you to a sub folder (see pic), right click and once again click on "Open Flie Location"

This will take you to the Vegas folder where you will find the ErrorReportClient.exe file.

Rename this file to (ErrorReportClient 2.exe)

This will fix the issue with the error panel poping up evertime you close Vegas Pro 19.

(Note: I had originally made an error and incorrectly said that I had changed a .dll file)

gary-rebholz wrote on 3/9/2022, 9:28 AM

While I appreciate @Cmin7669's effort to help you solve this, please don't follow that advice. The crash on shutdown is merely an annoyance...it doesn't affect your project file in any way. If you disable error reporting, then you can't give us any details about the crash and we have less information to use in finding a fix.

Additionally, and for you more importantly, that change could have unpredictable ramifications in other operations of the application. Things rarely stand alone in the code, so you are messing with something that is potentially problematic for you later.

Please use the error reporting system and include your name or some other identifying information in the details that will make it easy for us to search for your report.

Jack S wrote on 3/9/2022, 9:57 AM

@Cmin7669 Do you have Titler Pro 7 installed? I have, and the error report pops up every time I exit Vegas 19. This is a problem with Titler Pro 7 since it was updated with the latest build. I've informed NewBlue about this, but have yet to receive a response. As @gary-rebholz says, the error reporting system is important. This error report for me is just an annoyance. The only problem I have is that, if I forget about it popping up and go to click on something else, the focus is left onto the Send button and I end up sending the error report when I didn't mean to.

dape wrote on 3/9/2022, 12:24 PM

Vegas Pro 19 has stopped working on shutdown: is there any answers to this problem?

I have reset, and un-installed, reinstalled.

Here is my system:

OS Name Microsoft Windows 11 Home

Same for me. Latest version that just dropped today: each time i exit it prompts me the error and send screen like yours.

dape wrote on 3/9/2022, 12:25 PM

@Cmin7669 Do you have Titler Pro 7 installed?

I also have it !

jetdv wrote on 3/9/2022, 12:39 PM

And I also have Titler Pro 7 installed and have no issues starting or closing VEGAS.

Cmin7669 wrote on 3/9/2022, 3:38 PM

While I appreciate @Cmin7669's effort to help you solve this, please don't follow that advice. The crash on shutdown is merely an annoyance...it doesn't affect your project file in any way. If you disable error reporting, then you can't give us any details about the crash and we have less information to use in finding a fix.

Additionally, and for you more importantly, that change could have unpredictable ramifications in other operations of the application. Things rarely stand alone in the code, so you are messing with something that is potentially problematic for you later.

Please use the error reporting system and include your name or some other identifying information in the details that will make it easy for us to search for your report.

Well I have just installed the latest build 532, and to be honest didn't expect that they would fix all of the many problems with "19" but had hoped for a remedy to some of the more obvious bugs. In reply to Gary I would say that with regard to the "Error Report Client", yes it's and annoyance and not a fatal bug, nether the less it needs to be fixed. I hear some people suggest that it is Titler pro 7 that is the culprit and not VP19. The problem with that argument is that it marketed as an add-on by Magix so it should not cause issues.

I have just tried the GL transitions and though they rendered correctly on the first style, when I tried another it crashed Vegas and of course that in turn opened the error reporter. Do I have confidence that we will get a fix for this anytime soon….No.

I shall alter the error report once again to stop the error reporter popping up every time I close Vegas, Gary says that could make Vegas unpredictable with other ramifications, but I think that horse has already bolted.

Just so users know I have not had any unpredictable ramifications with altering the ErrorReportClient.exe file, but if there were, it's pretty easy to reverse the alteration back to what it was.

Jack S wrote on 3/9/2022, 5:28 PM

@jetdv Which build of TP7 do you have installed?

Cmin7669 wrote on 3/9/2022, 5:49 PM

Titler Pro 7 that came "free" with MSP.

jetdv wrote on 3/9/2022, 8:56 PM

@Jack S It says 210621 but I have TotalFX 220115 installed so I'm sure it's 220115.

Jack S wrote on 3/10/2022, 4:35 AM

@jetdv Mine's build 210922. Update yours and see if you still don't get the crash on VP19 exit.
It only happens if you don't use TP7 in your project. If you do, the crash doesn't happen.

jetdv wrote on 3/10/2022, 8:57 AM

@Jack S, I've confirmed mine is 220115. I've had to install some more recent beta versions based on some other work I've been doing with NewBlue which is why I now have a newer, non-released, version. I open and close VEGAS all the time without using Titler and haven't seen an issue. I also haven't seen an issue the times I also do use Titler Pro.

Former user wrote on 3/10/2022, 9:26 AM

210922 on mine, I very rarely use TP7 but sometimes get the crash msg, sometimes don't, regardless of whether i use TP7

Jack S wrote on 3/10/2022, 9:54 AM

@jetdv, @Former user Thanks for that. I've checked my NB account and the latest download build is 210922, so I guess I'll just have to wait.

gary-rebholz wrote on 3/10/2022, 9:57 AM

If it was a magic act, I'd fix all the bugs right now. But it's not. It's hard-working developers doing what they can do. And to imply that they aren't working because all of the "obvious" bugs haven't been fixed in this update does them a diservice. I'll take the blame for not properly prioritizing the team's work, which is my job. Hopefully I get it right next time.

jetdv wrote on 3/10/2022, 9:59 AM

@gary-rebholz, you're doing a great job. With x hardware configurations times y software configurations, it's impossible to try every combination.

Jack S wrote on 3/10/2022, 10:16 AM

@gary-rebholz And to imply that they aren't working because all of the "obvious" bugs haven't been fixed in this update does them a diservice.
I'm going to assume that that is a 'if the cap fits, wear it' statement, because It certainly doesn't fit me. I think, and have always thought, that you and your team do a fantastic, but sadly sometimes, thankless job. There will always be some users who find fault, but who don't understand the full story.
Keep up the good work.

gary-rebholz wrote on 3/10/2022, 11:16 AM

In my neighborhood we say, "if the shoe fits", but yes.

Cmin7669 wrote on 3/10/2022, 7:59 PM

If it was a magic act, I'd fix all the bugs right now. But it's not. It's hard-working developers doing what they can do. And to imply that they aren't working because all of the "obvious" bugs haven't been fixed in this update does them a diservice. I'll take the blame for not properly prioritizing the team's work, which is my job. Hopefully I get it right next time.

With all due respect Gary, I’m sure you will agree that some of these bugs have been around for a long time.

I feel that Magix is simply releasing newer versions, before fixing the very irritating bugs that let down your program.

The Magix website publishes a list of minimum requirements to run Vegas Pro, most users, including myself, are operating machines with specs well above these requirements, yet still the bugs are bypassed in newer versions.

I know programming is hard, and that some bugs will get through, even with extensive testing, but in my opinion it is not acceptable to keep pushing out newer versions with bugs that have been around for a long time.

You have mentioned in a previous post that you don’t recommend altering the ErrorClinentReporter.exe as this will stop your programmers from discovering the problems, but I have sent dozens and dozens of reports on the same exact issue. The issues are still there.

Maybe it would be a good idea to issue a regular update, only with bug fixes along with a list of those that the team is working to fix. This would give all users confidence that Magix is serious about catching up on the issues that frustrate the hell out of us.

One last comment, Windows 11 has been out now for 7 months and it is now almost impossible to buy a new computer with the old windows installed. It is time to recognize this fact and ensure that Vegas Pro is up with the newer system.

I want Vegas Pro to do well, it is fundamentally a good application. I have personally invested a lot of time and money in learning and keeping up with developments. So please don’t go the way that Boeing went with the 737 max, taking shortcuts to satisfy the accountants and profitability.