Vegas Pro 17 wont load at all

Stratman wrote on 12/20/2019, 5:10 PM

Hi,

My first post here...

I purchased Pro 17 (previous Movie Studio 16 Platinum user) yesterday and installed it. It loaded ok first time, all looked good then l and I loaded first project to try out the colour grading. Saved project exited.

Now when I try to start the program every time I get a crash and cant use Pro 17 at all

I have logged a support ticket and sent them the dump files.

In the meantime thought I would also ask on this forum for help as well. I have also tried the holding down ctl & shift keys when loading , cleared the cache but error persists and program wont load. Also tried renaming Boris FX folders so they don't load but same error.

Part of the error report on trying to load is -:

Problem : Unmanaged Exception 0ex06d7363

Fault Module: c:\WINDOWS\System32\KERNELBASE.dll

update -: Vegas Pro 17 build 387; Installed on Microsoft Surface Book 1, WIn10 Pro (update 1909), Intel i7,16GB, NVIDA graphics NVIDA driver 441.66 (I installed latest driver to try something else to fix issue)

Appreciate any help :)

Back to post

Comments

Stratman wrote on 1/21/2020, 6:55 PM

ok thanks fr0sty, encouraging to hear they still onto it. I guess I'll just sit tight for now. I got a refund (was done relatively quickly) when I could not get it going and before we knew a roll back to build 353 worked for the time being. I have been testing 353 as a trial version since, although that has just expired. Not sure if they let you extend trial..

Been a MovieStudio user for years and thought I would jump up to Pro 17 for Christmas. I will consider buying it again when the issue is fixed. Understand there are plenty of happy users without this issue as well.

fr0sty wrote on 1/22/2020, 9:41 AM

There's a pretty extensive testing process that must be completed before any updates roll out (there is a crew of folks within Vegas Creative Software that test it, and for major updates, there's another crew of beta testers that it then goes to before release, though unfortunately not even that can be enough to catch every bug on every hardware/software configuration out there in the wild), so even if the update is done, the testing may not yet be... hang in there!

Stratman wrote on 1/22/2020, 9:38 PM

I certainly don't underestimate developers challenges with all of the hardware and software permutations out there. I'm hanging in there waiting patiently for the fix :)

Stratman wrote on 2/6/2020, 4:12 PM

Any news on the next build release date?

fr0sty wrote on 2/6/2020, 8:34 PM

They will make sure everyone knows once it's ready... best I can say at this point.

Stratman wrote on 2/7/2020, 1:42 AM

Hopefully not too far away!

DragonInWhite wrote on 3/1/2020, 4:08 AM

For those following, update 4 (Build 421) is out. I hope it solves our problems. Keeping my fingers crossed. I'll let you guys know how it goes.

Edit: After installing, testing by closing and opening several times, and restarting the computer before repeating the close and open test several times again, Vega 17 Pro can be opened without a problem. The lastest patch likely fixed whatever problem I faced in update 3. Hopefully it does for you guys as well.

vkmast wrote on 3/1/2020, 4:49 AM

@Stratman commented on this issue further here.

tut-m wrote on 3/2/2020, 3:02 PM

@DragonInWhite For those following, update 4 (Build 421) is out. I hope it solves our problems. Keeping my fingers crossed. I'll let you guys know how it goes.

Edit: After installing, testing by closing and opening several times, and restarting the computer before repeating the close and open test several times again, Vega 17 Pro can be opened without a problem. The lastest patch likely fixed whatever problem I faced in update 3. Hopefully it does for you guys as well.

Nope! Unfortunately, build 421 has the same issue about kernelbase.dll as build 387 or 353. The only builds that go flawlessly are 284 and 321.

In my case, VP opens every time, but the error about kernelbase.dll occurs when I want to open existing projects.

Bogdan-Mlachkov wrote on 8/15/2020, 6:10 AM

Hi guys, I bought Movie Studio Platinum 17.0 today, but I have a similar issue. Has anyone an idea how to fix it? I also send a ticket, but still decided to try here too. Thank you very much in advance!

EricLNZ wrote on 8/15/2020, 6:15 AM

Hi guys, I bought Movie Studio Platinum 17.0 today, but I have a similar issue. Has anyone an idea how to fix it? I also send a ticket, but still decided to try here too. Thank you very much in advance!

Suggest you repost in the Movie Studio section as your problem relates to VMS, not Pro albeit a similar issue.

1 … 2 3 4 5

of 5