Crash on startup - Initializing UI -

Cruxal wrote on 5/17/2018, 8:13 PM

https://gyazo.com/2625748e5267f3e2c90679c67d49c3a1

PC:

Windows 10

24GB RAM

i7 4790k

SK Hynix 240GB

GeForce GTX 1080

Never had problems before, didn't change anything recently.

Tried booting it up with CTRL + SHIFT, didnt work.

I tried a system restore. Didn't work.

Tried uninstalling, clearing registries, and erased all files and traces I could find. Didn't work.

Don't know what's going on at all. Couldn't find anything online either.

Comments

Kinvermark wrote on 5/17/2018, 9:34 PM

Is it tied to a specific project? Remember, Vegas will typically open the last project worked on unless you launch it from a different .veg file.

Grazie wrote on 5/17/2018, 11:57 PM

@Kinvermark +1.

@Cruxal : Well something has changed. How’s your spare real estate doing? Are you running out of space to load VP14?

BTW :

Is this, Build 270, the most recent/latest Build?

Cruxal wrote on 5/18/2018, 2:34 AM

I have around 50GB of free space on my main drive. I tried installing it on my 3TB drive, no difference. I tried opening Vegas using all sorts of different project files, doesn't work either. :(

NickHope wrote on 5/18/2018, 2:55 AM

There are suggestions for troubleshooting startup in this post: https://www.vegascreativesoftware.info/us/forum/faq-vegas-pro-won-t-start-what-can-i-do--104784/

Cruxal wrote on 5/18/2018, 4:50 AM

Yeah, I've tried everything in there. Only thing I haven't obviously is doing a clean boot. I'd rather try and isolate the issue rather then reseting my PC. Windows is up to date, all my drivers also. It's a fresh install of Vegas which is up to date also.

Kinvermark wrote on 5/18/2018, 9:26 AM

I had a similar problem a few weeks back, and could not remember changing anything...but in the end something, somehow had been changed, and by following Nick's guide I did get it working again (it was a plug-in preset misbehaving.) So think very carefully and try everything in that post (again?). Good luck!

Cruxal wrote on 5/18/2018, 5:18 PM

Finally got it to work. I did an sfc scan, it had errors, but it still didn't work. I did reinstall of Visual Studio C++ and most recent Net Framework, now it boots! Don't ask me what happened as to why it stopped working, I have NO IDEA.4

ItsHyperComplicated wrote on 1/13/2019, 2:31 AM

Finally got it to work. I did an sfc scan, it had errors, but it still didn't work. I did reinstall of Visual Studio C++ and most recent Net Framework, now it boots! Don't ask me what happened as to why it stopped working, I have NO IDEA.4

Due to my other work, I had to install the CUDA development kit from Nvidia for GPU-based work, along with that came the need to install the latest Visual Studio C++ 2017 Redistributables (14.16.27024 x64) along with the latest .NET Framework version (ver 4.7.2).

Needless to say, everything went awry with Vegas Pro after that. Upon lauching the program, it gets stuck on "Initializing UI" in the exactly same way as in your case. I am using Win7 Ultimate, 64bit. Trying right now to run a repair setup for both VC++ 2017 x64 and .NET Framework. Sheesh ...

ItsHyperComplicated wrote on 1/13/2019, 2:41 AM

Alright. I solved the problem.

If your Sony Vegas (Pro, v15 or v16 - applies to at least both of them) is stuck in "Initializing UI ..." upon starting the software, get the latest .NET Framework Installer from Microsoft and run it, even if you already have .NET Framework installed on your computer. From the setup options, choose "Repair".

After the repair process is finished, you need to reboot the computer and then it should be business as usual.

If not, try running a repair install / uninstall + re-install on the Micorosft Visual Studio C++ 2017 Redistributables as well.

Cheers!

Grazie wrote on 1/13/2019, 3:09 AM

C++ Redistrib and .NET strike again.

ItsHyperComplicated wrote on 3/2/2019, 7:43 PM

C++ Redistrib and .NET strike again.

And how many years have problems alike persisted? More than a decade already?

I can't believe the complete lack of interest in developing the overall program stability, and I'm a former SCS closed beta tester. Just had the latest VP16 crash for some other, completely unknown cause upon opening up a project file. These things just pile up ... *sigh*

maxime-lebled wrote on 9/11/2019, 7:40 PM

Was just facing the same problem. For me, it turns out that MSI Afterburner & Rivatuner Statistics Server (a popular resource monitoring overlay for games) was trying to hook into Vegas. Happened on both 15 and 17.

zdogg wrote on 9/11/2019, 8:14 PM

C++ Redistrib and .NET strike again.

And how many years have problems alike persisted? More than a decade already?

I can't believe the complete lack of interest in developing the overall program stability, and I'm a former SCS closed beta tester. Just had the latest VP16 crash for some other, completely unknown cause upon opening up a project file. These things just pile up ... *sigh*

Yes, let's all put the kibosh on buying the next update that is "new feature rich" and short on real nuts and bolts fixes to the basic routines in this software, and I want to include a less glitchy and jumpy GUI in that "core" list. Or they fix 17 in exactly the exact way I'm discussing. Who's with me???

I'm sick to death of a slow playback, glitchy, crash all the time program. Bells and whistles mean almost zero to me.....I mean, I'll take them, but they are secondary.

joseph-desaavedra wrote on 9/11/2019, 10:37 PM

I'm sick to death of a slow playback, glitchy, crash all the time program. Bells and whistles mean almost zero to me.....I mean, I'll take them, but they are secondary.

Here here! I second motion. at least wait till out of beta before release.

joseph-desaavedra wrote on 9/11/2019, 10:43 PM

the most complicated thing I ask it to do it key frame titles and slow playback. nothing else. it is a light simple interface NLE. embrace the concept. make it stable as a rock, could give a crap about the glitzy stuff.

Ralf wrote on 9/12/2019, 6:21 AM

Was just facing the same problem. For me, it turns out that MSI Afterburner & Rivatuner Statistics Server (a popular resource monitoring overlay for games) was trying to hook into Vegas. Happened on both 15 and 17.

I just had a UI initialization hang and thought, "Eh, maybe it will just take a few minutes...it's a glitch," and decided to check the forum in the mean time. Lo, I stumbled to the above and went, "Hey, I use Afterburner... I'll close that and see." I closed Afterburner and perhaps didn't wait long enough? I brought up task manager and killed the Vegas process (the program was still running) (I killed the process because that was the tab that was open upon calling up the task manager and the Vegas process was at the top of the list. So rather than switch tabs...). Soon as I killed the process...Vegas opened(!). I ended up rebooting afterwards since a temp file from a failed render was still locked to I/O sub process (not visible)(?).

This all occurred because I tried to cancel a render and well...renders don't cancel no more without calling up task manager and killing the program....leaving a mess behind.

Windows 7 - i7 6959X - 128GB RAM - GTX1080Ti - custom water loop - NVME OS drive - SSD and 15TB HDDs