Will Vegas 14 be ready for windows 10 creators update?

I was visionary😉https://www.vegascreativesoftware.info/us/forum/will-vegas-14-be-ready-for-windows-10-creators-update--105728/

 

 

Vegas 14 works on Windows 10 Creator update. The visionary question should have been when Microsoft should stop pushing buggy updates and break the functional computers with their updates. If you read my detail post, it seems that Microsoft may have deprecated Visual C++ 2010 libraries, which were difficult to uninstall, but were not migrated to Windows 10 install by Windows updater. However, leaving Windows registry entries which caused all the software linked to VC++ 2010 runtime crashed.

However, I would say Vegas still use the ancient VC++ runtime libraries and.NET 3.5 libraries. MAGIX should start using never versions of Microsoft VC++ and .NET 4.6.x libraries. Linking to ancient libraries in newer updates of Vegas makes life easier for MAGIX developers, and customers on old version of Windows, but breaks the software upon each update for customers using newer version of Windows. MAGIX needs to decide to clean up the Vegas code dependency on ancient Microsoft libraries or keep only old Windows' version customer base. In case of later option, eventually, customers with newer version of Windows will have enough of fixing and trouble shooting and move on to other software. For example Davinci Resolve 12.5 is free and has all the features which a professional NLE offers. It is just a time issue to go through a learning curve which is holding me back to switch to Davinci Resolve as my primary NLE.

Vegas would not open for me after this latest update either. I had to roll back windows 10 build and now it works.

Vegas would not open for me after this latest update either. I had to roll back windows 10 build and now it works.

You need to provide a bit of more information. Does it crash or nothing happen when you click on Vegas icon? If it crashes, then see my previous detail email about VC++ runtime errors. If it does nothing, then you have permission issues. Windows 10 update did not set permission correctly. I had permission issue too. I used Tweaking.com's Auto Repair to fix Windows permissions to default. If you can resolve all the mess with Windows 10 Creators update 1703 creates, then, Vegas would work on it. However, it may be better to skip the update 1703 of Windows and wait for a couple months for the next update with bug fixes.

There was a report from another user that was getting crashes whenever they clicked "Render as..." after they installed the Windows 10 Creators update. That user solved their issue by "updating the Rivatuner Statistics Server". This info is niche but may help someone.

For me, Vegas Pro 14 worked initially after upgrade to Windows 10 Creators Update (a quick load to make sure it worked but not really using the product.) When I returned to work on my project a few days later, Vegas Pro 14 would crash on the opening splash screen when it got to "Creating Windows..." I had to rollback Windows 10 and now Vegas Pro 14 loads fine and I am able to finish working on my project. Hopefully this will get resolved soon.

For me, Vegas Pro 14 worked initially after upgrade to Windows 10 Creators Update (a quick load to make sure it worked but not really using the product.) When I returned to work on my project a few days later, Vegas Pro 14 would crash on the opening splash screen when it got to "Creating Windows..." I had to rollback Windows 10 and now Vegas Pro 14 loads fine and I am able to finish working on my project. Hopefully this will get resolved soon.

I had those crashes with Vegas. It is a strange work around. It usually crashes when hit hit FileIOPlugins... creating Windows. I moved the C:\Program Files\MAGIX\Vegas Pro 14\FileIOPlugin directory out, start Vegas, then quit it. Out the FileIOPlugin directory back in the Vegas Pro 14 folder. Now Vegas would start wityhout problem. The work around, does not make sense to me, but it work. I assume after FileIOPlugin is removed and Vegas start, it builds the cache, which is not corrupted. Therefore, I assume something in FileIOPlugin directory has a bug.

I'm having some weird interface issues which I believe point to the Windows Developers Update. When I grab the timeline and move it to the left, the "hand" jumps to the track below it and highlights a section of the clip. Also, sometimes when I connect with the beginning or end of a clip in order to trim, it's very sticky and won't trim properly.

At first I suspected Nvidia driver and have since updated it. I do need to try rolling back the driver to an older version. The mouse driver wasn't really new, although I updated it to no avail.

There was a report from another user that was getting crashes whenever they clicked "Render as..." after they installed the Windows 10 Creators update. That user solved their issue by "updating the Rivatuner Statistics Server". This info is niche but may help someone.

This fixed it for me. I quit Rivatuner and MSi Afterburner and the software works. Nice. Thanks a lot.