SONY VEGAS DOESNT OPEN

wayn10 wrote on 10/13/2024, 9:45 PM

Hello, I upgraded from Sony Vegas Edit 2021 to Sony Vegas Pro 2022 and I cant open Vegas at all. Its stuck on Scanning VST PLUGINS 100% (check screenshot) and doesnt move from there. Ive tried everything I could think of, I unnistalled everything from my pc and did a clean install back and still doenst work, also tried a command (/NOVSTGROVEL) that I saw someone comment here in the forum and still didnt open. Im lost to be honest and I dont know what else to do and Im pissed because I payed for something that I cant even use lol. Its the first time Ive encountered this problem with any sony vegas version and Ive bought different sony vegas versions in the past. Please if someone can help me I would really appreciate it!
 

Comments

Dexcon wrote on 10/13/2024, 9:50 PM

See if anything in https://www.vegascreativesoftware.info/us/forum/stuck-at-scanning-for-vst-plug-ins-100-when-trying-to-launch--147471/ particularly about renaming VST folders to help identify which vst plugin may be the cause of the problem. It may possibly be that you've got a 3rd party plugin that is not compatible with Vegas Pro.

Please note that Sony has not been involved with Vegas Pro since 2016 - https://www.vegascreativesoftware.info/us/forum/sony-vegas-vs-vegas--119881/

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2024.5, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

wayn10 wrote on 10/13/2024, 9:52 PM

See if anything in https://www.vegascreativesoftware.info/us/forum/stuck-at-scanning-for-vst-plug-ins-100-when-trying-to-launch--147471/ particularly about renaming VST folders to help identify which vst plugin may be the cause of the problem. It may possibly be that you've got a 3rd party plugin that is not compatible with Vegas Pro.

Please note that Sony has not been involved with Vegas Pro since 2016 - https://www.vegascreativesoftware.info/us/forum/sony-vegas-vs-vegas--119881/

Can u explain to me like Im 5 ? Because I dont know how to do that. Thanks
 

Dexcon wrote on 10/13/2024, 10:25 PM

It might be easier to start off with asking if you have any 3rd party VST audio plugins installed on your computer? If yes, could you please list what those plugins are so that it will probably be more straightforward to suggest what needs to be done to specific folder names rather than playing around with all the folder possibilities. If there are exotic VST plugins, the trick might be knowing which folder that they are installed in on the C:\ drive.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2024.5, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

wayn10 wrote on 10/13/2024, 11:07 PM

It might be easier to start off with asking if you have any 3rd party VST audio plugins installed on your computer? If yes, could you please list what those plugins are so that it will probably be more straightforward to suggest what needs to be done to specific folder names rather than playing around with all the folder possibilities. If there are exotic VST plugins, the trick might be knowing which folder that they are installed in on the C:\ drive.

How can I check if I have any 3rd party VST audio plugins installed on my computer? Thanks

Dexcon wrote on 10/14/2024, 12:20 AM

How can I check if I have any 3rd party VST audio plugins installed on my computer? 

In most cases, you would have had to have purchased them from companies such as iZotope, Waves, Native Instruments, Celemony or from any of dozens of small audio plugin creators. Or if you have any audio editors or DAWs, there may have been audio plugin packages with came with them.

One way to check is to look for any plugins that have been installed in any of the following locations on your computer's C drive:

C:\Program Files\Steinberg\VstPlugins

C:\Program Files (x86)\Steinberg\VstPlugins

C:\Program Files\Common Files\VST3

C:\Program Files\VstPlugins

C:\Program Files (x86)VstPlugins

 

Plugins will have a .dll file extension name.

Vegas Pro's native audio plugins should not be in any of these folders because they are held in a differently named folder.

 

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2024.5, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

wayn10 wrote on 10/14/2024, 12:43 AM

How can I check if I have any 3rd party VST audio plugins installed on my computer? 

In most cases, you would have had to have purchased them from companies such as iZotope, Waves, Native Instruments, Celemony or from any of dozens of small audio plugin creators. Or if you have any audio editors or DAWs, there may have been audio plugin packages with came with them.

One way to check is to look for any plugins that have been installed in any of the following locations on your computer's C drive:

C:\Program Files\Steinberg\VstPlugins

C:\Program Files (x86)\Steinberg\VstPlugins

C:\Program Files\Common Files\VST3

C:\Program Files\VstPlugins

C:\Program Files (x86)VstPlugins

 

Plugins will have a .dll file extension name.

Vegas Pro's native audio plugins should not be in any of these folders because they are held in a differently named folder.

 

The ones located in Steinberg doesnt even exist in my pc but the C:\Program Files\Common Files\VST3 one I got and also one with VST2 , these 2 C:\Program Files\VstPlugins ; C:\Program Files (x86)VstPlugins also. What do I do now?

 

Dexcon wrote on 10/14/2024, 12:55 AM

Could you please let us know the name of those vst plugins - they'll be named 'pluginname.dll'

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2024.5, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

wayn10 wrote on 10/14/2024, 1:30 AM

Could you please let us know the name of those vst plugins - they'll be named 'pluginname.dll'

This is all I could find

Dexcon wrote on 10/14/2024, 1:57 AM

That's excellent ... thank you very much.

It looks like that they are all Audio Plugin Union VST2 and VST3 plugins which are MAGIX products. On MAGIX's APU product website, all three APU suites list the Vegas Family as being a supported host for the suites so in theory there shouldn't be a problem with opening Vegas Pro.

@rraud ... as you're way more familiar with MAGIX audio products then me, would you have any suggestions about APU plugin compatibility in Vegas Pro especially with version 22?

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2024.5, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

wayn10 wrote on 10/14/2024, 2:11 AM

That's excellent ... thank you very much.

It looks like that they are all Audio Plugin Union VST2 and VST3 plugins which are MAGIX products. On MAGIX's APU product website, all three APU suites list the Vegas Family as being a supported host for the suites so in theory there shouldn't be a problem with opening Vegas Pro.

@rraud ... as you're way more familiar with MAGIX audio products then me, would you have any suggestions about APU plugin compatibility in Vegas Pro especially with version 22?

What do you mean thank me? Thank you dude for all the help and support, I really appreciate it alot. All I want is to be able to use vegas thats all, all this made me really upset/frustrated. This never happened to me before.

Dexcon wrote on 10/14/2024, 2:47 AM

As an interim possible solution, if you are not currently using any of those APU plugins, try uninstalling them and see if Vegas Pro 22 opens successfully so that the registration/activation can take place, then close Vegas Pro 22. reinstall the APU plugins and see if VP22 opens successfully. If it does, all is good; if it doesn't, uninstalling the plugins should then again be necessary.

If after uninstalling the plugins Vegas Pro 22 still gets stuck on opening, try running the registry cleaner module in the free CCleaner as there may still be APU gremlins occupying the registry. Please get back to the forum if the above does not prove successful.

Of course, if you still need the APU plugins, then the above is not a practical interim solution.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2024.5, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

wayn10 wrote on 10/15/2024, 11:18 PM

As an interim possible solution, if you are not currently using any of those APU plugins, try uninstalling them and see if Vegas Pro 22 opens successfully so that the registration/activation can take place, then close Vegas Pro 22. reinstall the APU plugins and see if VP22 opens successfully. If it does, all is good; if it doesn't, uninstalling the plugins should then again be necessary.

If after uninstalling the plugins Vegas Pro 22 still gets stuck on opening, try running the registry cleaner module in the free CCleaner as there may still be APU gremlins occupying the registry. Please get back to the forum if the above does not prove successful.

Of course, if you still need the APU plugins, then the above is not a practical interim solution.

Hey again, so I tried unnistalling everything again and installed back these 3 only (Also used CCleaner like u said):


I still get the same error of stuck at vst-plugins 100% ...I dont get it how since supposely now I didnt install anything other than mocha, deep learning models and vegas itself. This is beyond frustrating tbh and I dont know what else to do.

ChrisD wrote on 10/15/2024, 11:37 PM

Not sure if it helps, but maybe check here?

mark-y wrote on 10/15/2024, 11:39 PM

@wayn10

Here's some basic video editing vocabulary and definitions for you. None of us got this stuff overnight, so let's take it one step at a time; @Dexcon and others here are very patient teachers, and if you don't understand something, stick it in the back of your mind and one day it will make more sense to you.

https://www.vegascreativesoftware.info/us/forum/speaking-good-video-a-beginner-s-guide--104463/

Welcome to the discussions!

wayn10 wrote on 10/15/2024, 11:52 PM

Not sure if it helps, but maybe check here?

Hey Chris, I checked that to see if I had something in the Protection History but nothing, its empty.
Dont know what else to check, also have my c++ up to date. Thanks still for the help, much appreciated.

wayn10 wrote on 10/15/2024, 11:55 PM

@wayn10

Here's some basic video editing vocabulary and definitions for you. None of us got this stuff overnight, so let's take it one step at a time; @Dexcon and others here are very patient teachers, and if you don't understand something, stick it in the back of your mind and one day it will make more sense to you.

https://www.vegascreativesoftware.info/us/forum/speaking-good-video-a-beginner-s-guide--104463/

Welcome to the discussions!

Hey Mark, the thing Is I cant even open VEGAS at all. Im totally fine about being a newbie still in VEGAS and that I have alot to learn still, I get that and Im okey with It, but on this case Im not complaining about a struggle inside the program itself, Im complaining about the fact that it wont even open. Thanks still.

wayn10 wrote on 10/16/2024, 12:45 AM

UPDATE: After messing around VEGAS folder in C:\Program Files\VEGAS\VEGAS Pro 22.0 and deleting everything that had a plugin in the name until I managed to open the program, I finally managed to open VEGAS and found the plugin (Check the screenshot below) that was stopping my vegas from loading and opening.

 



I wanna thank everyone again for the help, especially @Dexcon thank you so much for the patience and help, really appreciate it! Have a good day everyone!

andyrpsmith wrote on 10/16/2024, 5:37 AM

That is a normal Vegas file as I have it in the same folder and V22 loads fine. There must be be some other conflict somewhere.
Maybe add it back and explore some of the Vegas log files to try and find what is conflicting with that file.

   File:                C:\Users\Username\AppData\Local\VEGAS Pro\22.0\fileio_x64.log
   File:                C:\Users\Username\AppData\Local\VEGAS Pro\22.0\persist.prefs
   File:                C:\Users\Username\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionError.log
   File:                C:\Users\Username\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionOutput.xml
   File:                C:\Users\Username\AppData\Local\VEGAS Pro\22.0\dx_video_grovel_x64.log
   File:                C:\Users\Username\AppData\Local\VEGAS Pro\22.0\svfx_video_grovel_x64.log
   File:                C:\Users\Username\AppData\Local\VEGAS Pro\22.0\ocio_x64.log
   File:                C:\Users\Username\AppData\Local\VEGAS Pro\22.0\dx_grovel_x64.log
   File:                C:\Users\Username\AppData\Local\VEGAS Pro\22.0\vst_grovel.log
   File:                C:\Users\Username\AppData\Local\VEGAS Pro\22.0\vegas_script_x64.log
   File:                C:\Users\Username\AppData\Local\VEGAS Pro\22.0\gpu_video_x64.log
   File:                C:\Users\Username\AppData\Local\VEGAS Pro\22.0\hub.log

Last changed by andyrpsmith on 10/16/2024, 5:45 AM, changed a total of 3 times.

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

RogerS wrote on 10/16/2024, 8:46 AM

That isn't the plugin, it's the program that scans for plugins!