Uninstalled build 387 and installed build 353..... Build 353 works every time !!! Build 387 seems to be the issue.

Just reverted to 353 again. And back to working fine. Just need to put up with the update notice every time

Glad to have you back editing... hopefully they can sort out whatever it is causing your issue with the new version before too long.

We hope they can fix it soon. Pro 17 is still an amazing program when you step back and consider all of its functionality...

Hey sorry for the delay, see my specs below...

Common threads identified so far:

- All of you are using Vegas 17, build 387

- The issue isn't dependent on whether users were upgrading previous versions of Vegas or installing brand new versions.

- I've confirmed 3 of the 5 of you are using Nvidia GPUs (strat and ploan, can you please give us your specs @hadef-a and @Brett-Maloney?)

PLOAN: Intel Core i9-9900k CPU 3.6 Ghz. NVIDIA GeForce RTS 2080

Hope this helps. I'm also going to try to install the previous version to see if that works.

Best Wishes,

Ploan

Brett and hadef-a still haven't chimed in with their hardware setups, but so far everyone affected is using an intel/Geforce RTX setup. Of course, that doesn't narrow down much, as there are many others who have the same hardware that lack these issues... we should also focus on which version of windows 10 you are using, as in specifically which update version, that might yield some clues.

Hopefully reverting helps you as well, ploan.

Brett and hadef-a still haven't chimed in with their hardware setups, but so far everyone affected is using an intel/Geforce RTX setup. Of course, that doesn't narrow down much, as there are many others who have the same hardware that lack these issues... we should also focus on which version of windows 10 you are using, as in specifically which update version, that might yield some clues.

Hopefully reverting helps you as well, ploan.

Mine is a GTX 1080ti SLI setup, no RTX involved> the only common thing we identified so far is for those two tried, returning to a previous build worked. It is possible that the windows 10 version might have a clash, but if that was the case, I would expect much more people to have problems. Oh also, I think I did not mention previously, I'm on Win 10 Pro. What about the rest with problems? Are you on Win 10 Pro or the standard?

DragonInWhite, mentioned earlier -:My OS is Windows 10 Pro version 1909 build 18363.535

It could be that only those with a specific version (and build) of windows 10 and certain hardware experience the crash, or maybe you all are using the same antivirus or something... there's a common thread somewhere that is making this different for you than it is the rest of us.

Looking at the release notes for build 387, this seems the most likely one to provide a clue:

"Fix to prevent crash on startup when some third party scripts are read in at opening of the application"

Nick, you might be on to something as it does seem to crash early in the start up.

It doesn't get to that point in start up where it says ...Creating file I/O, initialising plugins, direct X... etc,etc

What's interesting is that it always loads once after a fresh install and then upon exit won't load again. Either the first load or first exit of the program changes something in the environment that causes all subsequent loads to fail with the KernelBase error.

The cause of this crash has to do with some new registration stuff. It has nothing to do with scripts or any .net versions. Information I would love to hear from anyone experiencing this problem:

• What flavor of Windows 10 are you running Home or Professional
• Have you at any point installed the VEGAS Post applications on your machine
• Do you have a VEGAS Post license which you are using

While we are able to see where the crash is happening on these machines, we are not able to determine what specific state a machine is in when we are seeing these problems. Any information would be greatly appreciated.

I've been out for holidays but had upgraded to 387 and it launched once, then crashed then I left town. Upon returning to town, I'm getting the exact same crash as described here. Going to revert to 353 and report.

Win 10 Pro 64 v1903 18362.535, Nvidia P6000 - updating GPU and Vegas reinstall had no effect on issue, but hopefully downgrade will. Will report shortly if it does. EDIT Build 353 works like a champ, so obviously same issue here.

The cause of this crash has to do with some new registration stuff. It has nothing to do with scripts or any .net versions. Information I would love to hear from anyone experiencing this problem:

• What flavor of Windows 10 are you running Home or Professional
• Have you at any point installed the VEGAS Post applications on your machine
• Do you have a VEGAS Post license which you are using

While we are able to see where the crash is happening on these machines, we are not able to determine what specific state a machine is in when we are seeing these problems. Any information would be greatly appreciated.

have never loaded Vegas Post, see previous posts for Windows version, I did install Boris Lens flare plugin the first time I installed Pro 17 but removed it and did not installed it subsequently, Have upgraded to Pro 17 from Vegas Moviestudio 16 Platinum (still installed)

I experienced the same issues as the other persons in this thread.

To answer some VEGASDerek questions:

• I have Windows 10 Home 1909 installed
• I never had Vegas Post installed nor had a license for it
• I upgraded my license from Vegas Pro 14 but uninstalled the version. Furthermore, before the new build, I never experienced this problem and I used Vegas on a weekly basis.

Here is my error message:

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 17.0 (Build 387)
   Problem:             Unmanaged Exception (0xe06d7363)
   Fault Module:        C:\WINDOWS\System32\KERNELBASE.dll
   Fault Address:       0x00007FFEA897A839
   Fault Offset:        0x000000000003A839

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 17.0\vegas170.exe
   Process Version:     Version 17.0 (Build 387)
   Process Description: VEGAS Pro
   Process Image Date:  2019-12-06 (Fri Dec 06) 02:51:16

I started having the same problem all of you are having when I went from Vegas Pro to Vegas Post on December 17th.
Installed Vegas Post, opened fine after install then crashes every time there after.
-Vegas version 17.0 Build 387

Here is my computer specs and windows version.

-NVIDIA GeForce GTX 1080 Ti with 11GB GDDR5X
-Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
-16GB Dual Channel HyperX(FM) FURY DDR4 XMP at 2933MHz
-Windows 10 Home 1909

I contacted Support back on December 18th and sent them all the necessary info they asked for. I know I am late posting on here but I did read every post on this thread and I can't think of anything else to add that might help.

Getting exact same kernel error on Vegas Pro 17 for subsequent startups (works fine on initial new install). I'm on a Ryzen 5 2600, 32 gig G-Skill DDR4, Radeon Rx580, Win 10 Pro 64 v1903, upgrading from VP16, no amount of uninstall/"clean" install nor registry changes nor changes in gpu acceleration settings, presence or absence of plugins, etc. seems to do anything.

Can confirm v .353 works

I enquired to Magix on my support Ticket number for this issue and got an automated response that it has been closed, but as far as I know there is no fix yet? Previous follow up on this issue got a reply.....

They've probably discovered the cause of the issue, and are working on an update, but don't have any info yet on when that update will be through the testing phase, therefore no news yet to share about when you should expect to see it.

They've probably discovered the cause of the issue, and are working on an update, but don't have any info yet on when that update will be through the testing phase, therefore no news yet to share about when you should expect to see it.

ok, cool. Hopefully the fix wont be too far away.

That's just speculation on my part, I too hope they can get it sorted soon, but at least the previous version was mostly stable, so you're not missing out on much until that next update drops.

Anyone have any further news on whether this issue has been fixed?