[Windows 7] Vegas Pro 19 stuck at "Creating Windows"

WorkStation7 wrote on 1/29/2022, 11:48 AM

Hello everyone!

I have been using Vegas Pro 12 and all above versions on Windows 7 64-bit Ultimate and never had issues with composing, rendering or any other features. However, in Vegas Pro 17 I noticed that the Render As menu broke down overnight — but it didn't bother me as I could still use the Batch Rendering feature with my custom settings. I also noticed that the special Options menu (accessed by holding down Shift) opens a blank window but this is probably because of the non-Win10 operation system.

I recently purchased Vegas Pro 19 (Build 458) and installed it on my system where the last Vegas Pro 18 edition was also installed. Everything worked fine after the installation and system restarts and I configured Pro 19 the same way as 18. This new 19 edition was still not able to open the Render As menu (without crashing VP19) so I tried replacing the RenderAsDialog.dll file from earlier versions as suggested in other Resolved forum threads. I tried restoring default settings with the Ctrl+Shift launch method, completely uninstalling and reinstalling Vegas Pro 19 (and Pro 18 is not on the system anymore at all), .NET Framework 4.8 (and earlier but they get upgraded automatically by 4.8), DirectX 9.0, about 7 NVIDIA drivers (from the latest to earlier versions), and .NET ucrtbase.dll files for last resort fixing attempts based on procmon logs (where the last IRP_MJ_CREATE event is in vegas190.exe is looking for "C:\Program Files\VEGAS\VEGAS Pro 19.0\models\colorization_model_v2.xml" before exiting with Process Profiling event; but I doubt this helps).

I have another system which runs the latest Vegas Pro 19 completely with the same Windows 7 Ultimate configuration and updates, and I could not find any leads on what could be working differently.

Long story short: Vegas Pro 19 on my system Windows 7 64-bit Ultimate can not launch after crashing at the "Creating Windows" splash screen. It was working before and stopped working after I tried replacing the RenderAsDialog.dll in hopes with fixing the broken Render As window. I have been looking at similar and different Resolved threads here (including all official support guides) and none of the provided methods changed the situation.

Is there anyone who knows how the above problem could be fixed without re-installing Windows 7 Ultimate (which runs every other program or game without issues)?

I say thanks in advance to anyone with an advice — have a nice day, fellow video editors! :)

Comments

walter-i. wrote on 1/29/2022, 2:14 PM

You do realize that Vegas Pro 19 requires Windows 10?
https://www.vegascreativesoftware.com/us/specifications/#productMenu

There are some (few) here who apparently still have it running under Windows 7, but some functions that require Windows 10 decidedly do not work then just.

WorkStation8 wrote on 1/29/2022, 2:40 PM

You do realize that Vegas Pro 19 requires Windows 10?
https://www.vegascreativesoftware.com/us/specifications/#productMenu

There are some (few) here who apparently still have it running under Windows 7, but some functions that require Windows 10 decidedly do not work then just.

As mentioned above, Vegas Pro 18 and 19 are working perfectly on my Windows 7 machines — the issue is not coming from OS compatibility. (Windows 10 is not a requirement but a strong recommendation as the UI and other features are much more compatible in utilising resources and displaying the new design.)

walter-i. wrote on 1/29/2022, 2:59 PM

You don't need to create a new username for every post, one is enough!

vkmast wrote on 1/29/2022, 3:25 PM

FYI, Community rule #7. Double registration.

@WorkStation7 @WorkStation8

WorkStation8 wrote on 1/30/2022, 2:01 AM

FYI, Community rule #7. Double registration.

@WorkStation7 @WorkStation8

Thank you for pointing out. My apologies for using 2 accounts but it seems like I put the wrong e-mail address when creating my first account — after I wrote my original post, I lost access to WorkStation7 immediately (because its e-mail address has a typo, thus I can not request even a password reset). :(

The issue I described above is genuine and I have reached out here for advice before opening a support case with the vendor.

Yelandkeil wrote on 1/30/2022, 3:00 AM

You are forgiven.

😍😍😍

48 Hours ago a sweet fellow claimed even a VEGAS Linuxversion.

Steve_Rhoden wrote on 1/30/2022, 6:11 AM

Simply re-install the .NET Framework 4.8, and install the .NET Runtime 6.0.1

WorkStation8 wrote on 1/31/2022, 11:23 AM

Simply re-install the .NET Framework 4.8, and install the .NET Runtime 6.0.1

I reinstalled both frameworks and Vegas Pro 19 itself and nothing changed — the launch issue (Creating Windows) appears the same in Safe Mode, as well. The registry entries were also fully uninstalled/removed during my recent attempt.

WorkStation8 wrote on 2/4/2022, 6:30 AM

[RESOLVED]

I finally solved this case, so here is my ‘Solution Summary’ for other users who might stumble upon this topic ↓

• After installing the currently available ‘19.1.0.0’ version of the ‘VEGAS Deep Learning Models’ package, VEGAS Pro 19 launched successfully, so it clearly passed the ‘Creating Windows’ last step. Note that the ‘Deep Learning Models’ are not prerequisites for VEGAS Pro 19 on Win10, so only users on Windows 7 must install this for a proper program launch.

• I went further to solve the ‘Render As’ issue — I found that the current ‘RenderAsDialog.dll’ (Build 458) looks for ever newer ‘.dll’ files.

After seeing the file names, I remembered those are present in the ‘Windows Desktop Runtime version 6.0.1’, which has already been installed on this system — but only the ‘x64’ edition. I downloaded and installed the ‘x86’ edition, too (note that this runtime package is basically a larger and extended release of the ‘.NET Runtime 6.0.1’ package), so now I had those files installed in 32-bit version along with the 64-bit version. VEGAS Pro 19 still thinks those files are not present on the system for the ‘Render As’ function, but now I know why — it does find the files but it looks for different versions (than the latest ones), as well, which are only able to operate under Windows 10 (and no further installation is required).

At this point, I knew that the current ‘RenderAsDialog.dll’ (257 888 bytes) cannot operate on Windows 7 as it uses files which are programmed/designed to work on a Windows 10 environment. I have the previously purchased VEGAS Pro 18 (Build 482) so I checked my backup installation files and found its ‘RenderAsDialog.dll’ (Build 482 | 115 520 bytes) — it is a lot smaller than the VEGAS Pro 19 version and when called, it uses files which are all present after installing the 32-bit and 64-bit versions of ‘Windows Desktop Runtime version 6.0.1’ on Windows 7. So after replacing the VEGAS Pro 19 ‘RenderAsDialog.dll’ with the one I have from VEGAS Pro 18, the ‘Render As’ function started working properly and flawlessly!

joelsonforte.br wrote on 2/4/2022, 6:48 AM

@WorkStation8

I also have Vegas 19 installed in one machine with Windows 7. The only things I can't do is go into the built-in preferences and import AVCHD files with Dolby Digital ac3 audio.

Do you have any alternative solution on how to resolve these two issues?

WorkStation8 wrote on 2/8/2022, 2:00 AM

@WorkStation8

I also have Vegas 19 installed in one machine with Windows 7. The only things I can't do is go into the built-in preferences and import AVCHD files with Dolby Digital ac3 audio.

Do you have any alternative solution on how to resolve these two issues?

Those two cases cannot be solved: the ‘preferences’ window (Shift options menu) has been designed to work on Windows 10, plus (to my knowledge) an ‘AVCHD’ video might only be loaded in the program if the container is not .ts or .m2ts (the other way would be trying to separate the video and audio streams from the file in order to import them indepedently).

joelsonforte.br wrote on 2/8/2022, 9:00 AM

Those two cases cannot be solved: the ‘preferences’ window (Shift options menu) has been designed to work on Windows 10, plus (to my knowledge) an ‘AVCHD’ video might only be loaded in the program if the container is not .ts or .m2ts (the other way would be trying to separate the video and audio streams from the file in order to import them indepedently).

Separating the video and audio streams will only work for importing the video stream (AVC codec in the .m2ts container), but the audio stream (ac3 codec in the .ac3 container) will not be imported as there is no native codec in Vegas for import this type of file. To import ac3 audio in Vegas pro you will need to convert it to a Vegas compatible audio format such as .aac format.

In my tests I can correctly import AVCHD files to Vegas Pro 19 on Windows 7 by rewrap the files to the .mp4 container encoding only the audio stream to .aac format.