How is this a Windows problem as apposed to magix vp17/18?

Reason for asking: When testing the file it caused a major problem with vp18. When I tested the same file with Edius (nle) it loaded, played on the timeline and could be rendered. Only steps missed was to apply fx.

It just seems strange to blame Microsoft; to my mind it is a magix problem. Thanks.

If a Windows Update breaks functionality of software, who is to blame? Hopefully Magix and/or Microsoft can fix it in a timely way.

The team is aware of the problem and maybe they have a fix in a next VPro 18 update.

Seems to only affect V17 & 18 other versions seem fine.

Seems to only affect V17 & 18 other versions seem fine.

With me it affects VPro 17,18 and VMS Pl 17

Not sure who is to blame, but since Vegas 18 has problem and Vegas 16 does not, hopefully Magix can figure it out. I had to put Microsoft updates on pause, but that gives me just 7 days and no way I can finish editing all my surround sound video files by then. So if Microsoft update pushes through and there is no fix, then I'm dead in the water with those older projects.

@Matthew-Comstock Just uninstall KB5001330, as suggested elsewhere, until either Microsoft or Magix fixes it.

Thank you so much!! This was the solution for me too!!!😀

@virginia-m 👍

@JN-  I think you missed my earlier posts where I did just that. However, Microsoft wants to reinstall and I had to put it on pause, but it told me I can only do it for 7 days.

@Matthew-Comstock Yes, by elsewhere, I meant that I saw that tip in another thread, john dennis gave it, here, so I posted it here. Not everyone reads everything, the important thing is if my input was of use to anyone, I believe that was so.

@Matthew-Comstock Yes, by elsewhere, I meant that I saw that tip in another thread, john dennis gave it, here, so I posted it here. Not everyone reads everything, the important thing is if my input was of use to anyone, I believe that was so.

That's how it is in life: You can't do anything without being criticised by someone.
Some people look for problems 😠 - others for solutions 😀.

@Matthew-Comstock Yes, by elsewhere, I meant that I saw that tip in another thread, john dennis gave it, here, so I posted it here. Not everyone reads everything, the important thing is if my input was of use to anyone, I believe that was so.

That's how it is in life: You can't do anything without being criticised by someone.
Some people look for problems 😠 - others for solutions 😀.

I am definitely looking for solutions. It is hard to follow with the various threads, but I added an edit 3 with what I think is the original problem mention and good news is that Magix has a fix in beta testing.

@Matthew-Comstock I saw this of you:

 No problem with Vegas 16 or earlier.

Afaik there comes a solution in the next update for Pro 18 as stated by MagixDerek.
To be able to work with the files in VPro 17 for me the problem was gone after I did following:
1, Copy file "C:\Program Files\VEGAS\VEGAS Pro 16.0\FileIO Plug-Ins\compoundplug\compoundplug.dll"
2 Goto the same file of VPro 17 and rename to "old..........."
3. Paste the file of 1 at the same location.

@Matthew-Comstock I saw this of you:

 No problem with Vegas 16 or earlier.

Afaik there comes a solution in the next update for Pro 18 as stated by MagixDerek.
To be able to work with the files in VPro 17 for me the problem was gone after I did following:
1, Copy file "C:\Program Files\VEGAS\VEGAS Pro 16.0\FileIO Plug-Ins\compoundplug\compoundplug.dll"
2 Goto the same file of VPro 17 and rename to "old..........."
3. Paste the file of 1 at the same location.

I changed name of compoundplug.dll in Vegas Pro 18 folder, then copied in the version from Vegas Pro 16, but Vegas Pro 18 crashed when using the V16 version. I went back to the original and it was fine. Maybe it would work with the new Windows update, but I had already rolled it back for the second time today. Also not sure Windows would need to be rebooted after changing version, I had only quit Vegas when applying the swap. Let me know if there is something I may have missed in this process.

You must read my comment well. Changing 18 comes with a new update. I was talking about 16 and 17

Understood now. The files import fine into Vegas Pro 16,which I have. I skipped 17 and went directly to 18 in my upgrade path as the promise of improved stabilization lured me in. And I would say that the Vegas Pro 18 stabilization has been good enough to allow me to finally edit my old video which I thought was too shaky. I had attempted some of the 3rd party stabilizations in the past, but the workflow was too tedious and time consuming to make it practical for thousands of clips.

Hello,

I tested the described method (copying the compoundplug.dll from VP16 to VP17) a few days ago. It works for me to import files with AC3 5.1 tracks into VP17. However, when calling the render dialog, the program crashes. Only the deinstallation of the updates KB5000842 and KB5001330 has brought success so far. Unfortunately, this cannot be a permanent solution.

Holgy

Windows 10 Pro 2004 will not let me uninstall the KB5001330 update. Does anyone have any information on the Beta fix Magix is working? ETA? The dll-swap technique (both in Vegas 17 and 18) did not work for me at all on some project files, and did not play the audio tracks on the few it did open.

Windows 10 Pro 2004 will not let me uninstall the KB5001330 update.

@Doug-Buseck
Do you perhaps not have administrator rights on the PC because you cannot uninstall the Windows Update?

@walter-i.

I have a similar issue in that I have Admin rights and I cannot uninstall KB5001330. However, I switched the .dll mentioned above and Vegas17 seems to be functional right now. It would be nice if Magix decides to help ALL of its customers-both current and previous. I am sure that a patch could be written that would help us all.

This is bigger than Vegas. Not only M2TS and MTS, but VOB and MPG, even MP4 stopped working in Windows yesterday -- won't play, can't open, rename, delete, or move. Windows HARD LOCKS and must use POWER BUTTON RESTART!

So I went back to Control Panel, and the damned update had been installed--again! Everything went back to normal after second uninstall.

• This is a Microsoft problem. Vegas is just our local poster child.
• Paused updates for a month. Microsoft owes us a fix; we owe them nothing for this abomination.
• Leave the files on my computer alone! If there's a problem with malformed downoads, fix that!
• If I wasn't too old to learn a new OS, I would be dumping Windows today. Just damn them.
• But with billions of all-important gamers screaming at Microsoft as well, I think the bottom line is going to force a fix soon.

EOR

WOW! I was only concerned with .mts/5.1 sound files, had no idea this was so widespread.

This is bigger than Vegas. Not only M2TS and MTS, but VOB and MPG, even MP4 stopped working in Windows yesterday -- won't play, can't open, rename, delete, or move. Windows HARD LOCKS and must use POWER BUTTON RESTART!

@Musicvid - THANK YOU! This was exactly the issue I got with my recently returned MONSTA! - Windows HARD LOCKS and must use POWER BUTTON RESTART! - I couldn't believe it. I also did a CacheCleaner which remove a mass of RegKeys looking for the Door.