Vegas 17 and Windows update 20H2

Blaine-WItherow wrote on 5/3/2021, 1:06 PM

Windows update 20H2 has caused many of our Vegas projects to not launch. I assume the problem is MTS files or possibly MP4 files that are in certain projects. I do not know if this is something Magix or Microsoft will address to fix. IF you did not install this update, I warn you not to install it. If anyone has a solution, let me know. Fortunately right now, I have one workstation that did not install the Windows update 20H2, but two did.

Comments

diverG wrote on 5/3/2021, 1:20 PM

Restore the 2 non working pc's with a system image from say about a month back. Then stop updates until we know problem is cleared. I trust you do take regular system images. Less than 10 minutes to restore an image. Acronis & macrium work well, likewise' Back up and Restore' found in the control panel. Leftover from W7 but still reliable.

john_dennis wrote on 5/3/2021, 2:16 PM

https://www.vegascreativesoftware.info/us/forum/vegas-pro-17-crashes-when-loading-mts--128572/#ca799527

Howard-Vigorita wrote on 5/3/2021, 2:20 PM

Before rolling back or freezing windows updates, suggest you try updating all your graphics drivers first. The graphics makers all updated most of their drivers to accommodate 20H2 so if they're out of date, that may fix the problem.

Also, Microsoft just re-issued the March cumulative as KB4023057, apparently to cancel out the April KB5001330 one, so doing another windows update to install KB4023057 may fix the problem for you too. There's also a 20H2 update for net framework that's probably crucial to Vegas so make sure you have that. Fwiw, my practice is to install every windows and graphics driver update and only on a few occasions, but not lately, have I had to roll back a graphics driver. My recent windows update history looks like this:

VEGASDerek wrote on 5/3/2021, 2:53 PM

I do not know if this is something Magix or Microsoft will address to fix.

We are working hard to get a fix out for this problem in both VP 18 and VP 17 (along with VMS 17 and VMS 17 Platinum). We hope to have this delivered within the next 2 or 3 weeks. I know that seems a bit slow and quite a long time to wait, but coordinating updates for 4 different applications at the same time is a bit tricky and is creating a massive backlog for our QA team as they verify these releases. We are working as quickly as possible to resolve this for all of you.

JN- wrote on 5/3/2021, 3:59 PM

@VEGASDerek Thanks for the timescale.

walter-i. wrote on 5/3/2021, 4:10 PM

@VEGASDerek Thanks for the timescale.

👍

BobMoyer wrote on 5/4/2021, 10:01 AM

@VEGASDerek: Thank you VERY much for the information. It may seem like an eternity for some but at least a remedy is on the horizon.

Doug-Buseck wrote on 5/5/2021, 12:43 AM

Thanks so much for the update VEGASDerek! Having even a ballpark estimate as to when the fix will be available will help us manage our editing schedule. I appreciate it! 😀

robbif2 wrote on 5/8/2021, 6:42 PM

Thanks! I'll be watching!

JohnCorda wrote on 5/11/2021, 4:36 PM

Is the combination of Windows updates and stuff also the culprit for constant CTDs? I always had to deal with crashing with Movie Studio Platinum - v16 and v17 and probably older, but currently on v17 it's like every 4 minutes, it's making it impossible to use...

Blaine-WItherow wrote on 5/11/2021, 5:14 PM

I don't think it is the same thing. As far as I know, V16 was not affected by the problem introduced by the windows update that I refer to. MTS files would not import or play at all in V17 or V18 after the 20H2 update. In our case, a current project had some MTS video files in it, and we could no longer even open the project. That is a lot different from crashing. (I don't know anything about CTDs)