Vegas Pro 17 wont load at all

Comments

Stratman wrote on 12/24/2019, 2:53 AM

Very pleased with eveyones suggestions, It does take time to cover every suggestion in every post. I have disabled anti-virus tho, no change. I'll work through some of the other suggestions as well.

Previoulsy I have had Movie Studio Platinum 13 & 16 running on same PC with no issues at all.

OS is Windows 10 Pro version 1909 build 18363.535

Stratman wrote on 12/24/2019, 3:58 AM

additional things checked ...Ran Microsoft .Net repair tool. -> no change

Firmware and GPU drivers are latest.

I'm working through the FAQ's but my gut feel the FAQ's wont fix it. I have no other issues with any software except P17.

Surely when you unistall / reinstall P17 and it runs once, then it won't run again, it is an issue with Pro 17 changing something and causing the issue in the first place.....

Musicvid wrote on 12/24/2019, 7:40 AM

I used Regedit to look for .NET Framework and all I can see is folders with 4.0

 

Any 64 bit version should work. I was good on 4.5. Look in Uninstall Programs / Windows to see what you have.

Musicvid wrote on 12/24/2019, 7:57 AM

Surely when you unistall / reinstall P17 and it runs once, then it won't run again, it is an issue with Pro 17 changing something and causing the issue in the first place....

That's usually not the case. Did you install new graphics drivers or such?

ploan wrote on 12/24/2019, 11:59 AM

Thanks for this post, did my due diligence and went through the FAQs and found the following...

Vegas Pro 17 build 387

  • Intel Core i9-9900K CPU
  • NVIDIA GeForce RTX 2080 (v 26.21.14.4166)
  • Win 10 (Version 1909)

Checklist

  • Fr0sty - Command Unregister/Register

Result: Error Message 'The module 'KernelBase.dll was loaded but the entry-point DllUnregisterServer was not Found. Make sure that 'KernelBase.dll' is a valid DLL or OCS file and then try again'. Tried to reinstall vegas after that with same crash at Vegas startup

  • Check Windows Installation - Done
  • Windows Troubleshooter - Done
  • SFC - Done
  • Update MB BIOs - Done
  • Update MB chipset drivers & GPU Drivers (All drivers updated via Drive Booster 7)
  • Furmark - Ran for 10 minutes looks fine (GPU 1: NVIDIA GeForce RTX 2080, GPU: 62°C, power: 21.5% TDP)
  • Ran ccleaner - Done (Clean and reg clean)
  • uninstall all VP and all VP Plugins + delete all VP related folds + uninstall all magix software - Done
  • Reinstall after uninstall - Done
  • GPU preference (GPU acceleration of video processing) set to off - Done
  • create new user & reinstall VP - done
  • .NET framework v4.8.03752 - done
  • Anti virus - Off (default win10 antivirus)

I think I just went through all the FAQs and this thread, and it still crashes.

Interestingly enough, if I start the program 7 times in a row (crashes each time with this error message), the 7th or 8th time, it actually starts up with no problem.Also, the package I bought has Boris FX Continuum LensFlare3D and if I install this, it won't start the 7th or 8th time (I uninstalled it afterwards, so I could keep testing)

Right now, with only VP 17 installed, looks like it will crash eachtime with KernalBase.dll error - but will startup under the following conditions...

  • First install
  • opening program 7 to 8 times in succession

Any other thoughts of what I could do guys?

Thanks!
Pat

 

j-v wrote on 12/24/2019, 12:31 PM

@ploan

Where is Windows installed?
Where is Vegas Pro 17 installed?
What's the location of your Windows Documents/Pictures/Video/etc. ?

met vriendelijke groet
Jan

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home, version 1903 build 18.362,295 CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17 and VMS PL 16 are installed, all latest builds
Both Nvidia GPU's have driver version 441.66 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

ploan wrote on 12/24/2019, 12:50 PM

Thanks for the response.

Answer: Windows, Vegas PRO 17 (C:\Program Files\VEGAS\VEGAS Pro 17.0) and windows docs/pictures/video (i.e. C:\User\ploan) are all installed on the main hard drive Was this what you were asking?

j-v wrote on 12/24/2019, 12:59 PM

Do you have other harddrives?

met vriendelijke groet
Jan

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home, version 1903 build 18.362,295 CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17 and VMS PL 16 are installed, all latest builds
Both Nvidia GPU's have driver version 441.66 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

ploan wrote on 12/24/2019, 1:02 PM

Yes I do.

1 8GB one

1 9TB one

 

j-v wrote on 12/24/2019, 1:18 PM

OK,
- In this edit world the 8GB is worthless to work with, maybe some small sourcefiles.
- The 9TB you can make partitions for those Windows files as W. Documents by replacing them with the biggest for Your Video's where you store your sourcefiles for the program.
- Plus make a partition there for your rendered files and set this one in Vegas as your renderlocation.

met vriendelijke groet
Jan

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home, version 1903 build 18.362,295 CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17 and VMS PL 16 are installed, all latest builds
Both Nvidia GPU's have driver version 441.66 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

ploan wrote on 12/24/2019, 1:26 PM

Thanks for the heads up. Definately was planning to use the 9 TB for editing.

That being said, this is a new computer and I haven't ported over my files yet from my old PC; so there's barley anything on this computer. I just bought and installed VP17 and have not worked on it yet (just opened it upon first install and changed vid pref to off)

Should i reinstall it on the 9 TB drive? Perhaps that should solve my startup issue? Will try that.

j-v wrote on 12/24/2019, 1:33 PM

Should i reinstall it on the 9 TB drive? Perhaps that should solve my startup issue? Will try that.

What would you reinstall there?
Always hold Windows and Programs on the C"/ and the rest, if possible, elswhere.
 

 

met vriendelijke groet
Jan

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home, version 1903 build 18.362,295 CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17 and VMS PL 16 are installed, all latest builds
Both Nvidia GPU's have driver version 441.66 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

ploan wrote on 12/24/2019, 1:36 PM

ok. Thanks.

Sorry misunderstood what you were talking about. What do you think of this thread? Any insight on the startup issues of VP? (information on what i did on previous post)

j-v wrote on 12/24/2019, 2:01 PM

Any insight on the startup issues of VP?

I have never startup problems. I install the program as it is with all the choosen options of the program itself for the settings.
Two times only there were some difficulties, but never crashes or so.
A few years back there was a problem loading NB FX effects and with the first VPro 17 the settings in the I/O file Preference was not good choosen by the program, it beame resolved in the first update. So I'm a happy user of the program with all my hardware settings learned in seeking workarounds with Pinnacle software in the first 10 years of this era.

 

met vriendelijke groet
Jan

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home, version 1903 build 18.362,295 CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17 and VMS PL 16 are installed, all latest builds
Both Nvidia GPU's have driver version 441.66 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

hadef-a wrote on 12/24/2019, 2:47 PM

DID YOU FIND A SOLUTION TO THIS???? I ALREADY PAID FOR IT

Last changed by fr0sty on 12/24/2019, 10:09 PM, changed a total of 1 times.

Reason: The foul language isn't necessary. I was careful to express the same point while not using as colorful language.

Stratman wrote on 12/24/2019, 2:49 PM

Seems Brett, Ploan & myself all have the same KernelBase issue. I have dumped heaps of files and sent to Vegas support with no response / suggestions /fix so far. It will be gold when we find the fix!

BTW, given the surface Book I'm using has 2 GPU's (intel & NVIDIA) I detached the base (which houses the NVIDIA GPU ) and used in tablet mode. The I7 processor, 16GB RAM and Intel GPU reside in the screen /tablet . Loaded Vegas which therefore has to use the Intel GPU. Same error. The other guys are having the exact same KernelBase error with different hardware so I don't think its a hardware issue.

fifonik wrote on 12/24/2019, 5:43 PM

When VP successfully started after cleanup, you can try to provide information from Help | About | Computer and Help | About | Components.

@ploan Good job for checking all of this. You can try to use regasm instead of regsrv32 to re-register the dll. However, at this stage I'd try to re-install Windows over existing installation with keeping programs and data. In my case this fixed BSOD after hardware upgrade once. Process is quite slow (15+ minutes) but simple. Be careful while selecting what to do with existing data.

Last changed by fifonik on 12/24/2019, 8:54 PM, changed a total of 3 times.

Camcorder: Panasonic X920

Desktop: MB: MSI B450M MORTAR TITANIUM, CPU: AMD Ryzen 3700X, RAM: G'Skill 16 GB DDR4@3200, Graphics card: MSI RX470 4GB, SSD (OS): Samsung 850 EVO SATA 250MB, HDDs: Seagate & Toshiba 2TB, OS: Windows 10 Pro 1909

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17

fr0sty wrote on 12/24/2019, 6:50 PM

Those of you that haven't already, make sure you file a support ticket with Magix.

VEGAS Support | MAGIX Support https://support2.magix.com/customer/en/vegas/form

"The other guys are having the exact same KernelBase error with different hardware so I don't think its a hardware issue."

And Kernelbase errors are usually related to the OS. Perhaps something corrupted that DLL, like a bad windows update or something.

EricLNZ wrote on 12/24/2019, 8:42 PM

@hadef-a This is a user forum. Your fellow users appreciate that you are getting frustrated but abusive and vulgar language is not tolerated and has been edited by a moderator.

Anyway how about doing something useful and contributing sensibly to this thread. To start with what are the full specs of your system? Also I wonder if third party plug-ins might be involved in the problem. What plug-ins do you have installed?

Merry Christmas.

NickHope wrote on 12/24/2019, 9:52 PM

There is some overlap with the FAQ posts already mentioned, but the best FAQ post for troubleshooting this issue is here: https://www.vegascreativesoftware.info/us/forum/faq-vegas-pro-won-t-start-what-can-i-do--104784/

ploan wrote on 12/25/2019, 12:45 AM

Those of you that haven't already, make sure you file a support ticket with Magix.

VEGAS Support | MAGIX Support https://support2.magix.com/customer/en/vegas/form

"The other guys are having the exact same KernelBase error with different hardware so I don't think its a hardware issue."

And Kernelbase errors are usually related to the OS. Perhaps something corrupted that DLL, like a bad windows update or something.

Yeah submitted a ticket in parallel to posting here =P

Doing some research on other sites; there doesn't seem to be a consistent message about the problems - some saying it's something to do with corruption in the .NET framework others disagreeing with that statement. Tried to use the.NET framework repair tool - which did absolutely nothing - and I don't know enough about the technical to fiddle around with it more.

Haven't done Windows over existing installation with keeping programs and data yet so I guess that's the next step, kind of scared of it tbh in case something goes wrong, time to find that external usb/hard drive to back up stuff I guess; especially since this is the only program that doesn't work. Logically it still perplexes me why it would work if I run the darn thing 7-8 times. It should fail all the time right?

Anyway, thanks for the tips, will keep scouring for an answer. This is a very active forum, which is cool as not all software forums are as responsive or helpful.

fifonik wrote on 12/25/2019, 2:23 AM

You can try to check Windows Event Logs. May be there are some warnings prior the exception in log that can give some clue.

Also, if you have other HDD, you can try to do clean windows installation on it (disconnecting your current system drive). Then install only chipset driver, video driver and Vegas. Just to check that the issue is not causing by hardware combination you have.

Camcorder: Panasonic X920

Desktop: MB: MSI B450M MORTAR TITANIUM, CPU: AMD Ryzen 3700X, RAM: G'Skill 16 GB DDR4@3200, Graphics card: MSI RX470 4GB, SSD (OS): Samsung 850 EVO SATA 250MB, HDDs: Seagate & Toshiba 2TB, OS: Windows 10 Pro 1909

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17

Stratman wrote on 12/25/2019, 5:12 AM

Those of you that haven't already, make sure you file a support ticket with Magix.

VEGAS Support | MAGIX Support https://support2.magix.com/customer/en/vegas/form

"The other guys are having the exact same KernelBase error with different hardware so I don't think its a hardware issue."

And Kernelbase errors are usually related to the OS. Perhaps something corrupted that DLL, like a bad windows update or something.

Yeah submitted a ticket in parallel to posting here =P

Doing some research on other sites; there doesn't seem to be a consistent message about the problems - some saying it's something to do with corruption in the .NET framework others disagreeing with that statement. Tried to use the.NET framework repair tool - which did absolutely nothing - and I don't know enough about the technical to fiddle around with it more.

Haven't done Windows over existing installation with keeping programs and data yet so I guess that's the next step, kind of scared of it tbh in case something goes wrong, time to find that external usb/hard drive to back up stuff I guess; especially since this is the only program that doesn't work. Logically it still perplexes me why it would work if I run the darn thing 7-8 times. It should fail all the time right?

Anyway, thanks for the tips, will keep scouring for an answer. This is a very active forum, which is cool as not all software forums are as responsive or helpful.


It s perplexing in as much as it is Vegas that is corrupting the KernelBase.dll or Vegas thinks the file is corrupted and its only Vegas that gives the KernelBase error... Glad we have all logged tickets hopefully after their Christmas break the developers can provide a timely fix.

I may be wrong but I suspect prior to the break something has probably been changed or an iteration within build 387 because the KernelBase issue is seems only to be happening to people who purchased and downloaded VEGAS pro 17 in the past week.

fr0sty wrote on 12/25/2019, 6:38 PM

Though most of us are using 387 without issue, having upgraded from previous versions.