Movie Studio Platinum Stop Working When Trying to Add Videos

Demetrius-Taylor wrote on 4/22/2021, 9:02 AM

I am getting an error message after selecting Add Media, I click on a video to add and I immediately get an the error message that Movie Studio Platinum Stop has Stopped working. Once I sent the error log, the application shuts down. I have version 16.0 Platinum.

I have the application installed on my Surface.

Anyone else encounter this issue and/or has any thoughts on how to fix.

Comments

Greg-Z wrote on 4/22/2021, 4:32 PM

+1

Just noticed today that VMS17P build 204 crashes every time I try to add/open m2ts video to project (m2ts files are from my SONY camera). This started happening on both my PCs. Even with VMS16P. I already tried to uninstall/install, disable antivirus with no luck - still crashes. It also crashes when I open old projects with m2ts files.

Adding mpg files is fine.

I can't say exactly when it started to crash. But as far as I remember, it worked fine two weeks ago.

John-Sarick wrote on 4/22/2021, 6:52 PM

I am getting an error message after selecting Add Media, I click on a video to add and I immediately get an the error message that Movie Studio Platinum Stop has Stopped working. Once I sent the error log, the application shuts down. I have version 16.0 Platinum.

I have the application installed on my Surface.

Anyone else encounter this issue and/or has any thoughts on how to fix.

I've been having the same issue since I recently upgraded to 17.0 Platinum. Cannot load and Sony MTS files. MP4 files are fine. I'm not a frequent user, but last month version 16 worked fine with the Sony MTS files.

 

EricLNZ wrote on 4/22/2021, 8:23 PM

@John-Sarick If you follow through on the link I gave above you will find a recent Windows update is behind the problem. Search the forum and you will find several threads on the problem, which hopefully will be fixed either by Microsoft or Magix Vegas.

John-Sarick wrote on 4/23/2021, 6:28 AM

Hello EricKNZ - yup, after posting then I read a little further and found the fix you mentioned. Worked fine after uninstalling that specific windows update. Thank you!