We've been informed that Updates for the products affected by the Windows Update problem are in development and will be released as quickly as possible. The products include VP 17, VP 18 and VMS(P) 17.
It refers to the recent Windows Update problems discussed currently in several forum threads.
Thank you for the 'heads-up'. I will be very happy to have my #17 back up and running. Thank you Magix!
Has this update affected Hard Drive access?
If you mean with "update" the Windows update, that changed the way which AAC files could be opened in those Vegas versions
It affected my video file handling system-wide. Lost another day yesterday when the damned thing reinstalled itself. KB5001330
@vkmast Some progress from the Microsoft end ... https://www.windowslatest.com/2021/04/24/microsoft-issues-emergency-windows-10-april-fix-for-performance-issues/
Check for Windows updates ...
“Once you’ve checked for updates and your device has communicated with the Windows Update server, you’ll need to restart the device.”
This included link in above article gives directions on removing updates, using command prompt also. https://www.windowslatest.com/2021/04/23/how-to-uninstall-windows-10-updates-manually/
And theres this also ...
“The immediate solution to this problem involves checking for updates in the Settings app and restarting the device. If the fix has been applied, you will no longer face performance and gaming issues.
The problem with the “Known Issue Rollback” approach is that users cannot easily verify if the server-side fix has been applied to their device. Fortunately, using a simple PowerShell script, you can scan Windows Registry and verify the hotfix manually.
To verify fix for KB5001330 issues, use these steps:
Open Windows PowerShell from Search.
Enter the following command, should be all on one line.
Get-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\4\1837593227
When you enter the above command, you should see the information of a registry key in the PowerShell window. If you get the message “Path not found”, then the fix is not applied.”
Re the question as to whether this is a Windows problem or a Vegas Pro/VMS problem, I take a broader view that MS regularly makes updates to its OS - mandatory or optional. But I really doubt that MS sends beta versions of those updates to all 3rd party program and app software companies like MAGIX that use Windows 10 to ensure that those W10 updates work without a problem. Surely that would be in the 100,000s or even millions of 3rd party programs and apps. At least both MS and Vegas recognise that there is a serious problem and are both working on a solution.
Disable Windows 10 Automatic Updates 
Has anyone had an update from either Magix or MS about a fix for the .mts issue on VP17/18?
Hello BobMoyer - I have not seen anything official from Magix. They can push advertising when you start up their programs, but after 2 weeks of this problem: not a word. It would be nice if they pushed a message with an ETA for the fix, or maybe even sent a robo-email out to all the registered users. I've seen nothing but posts from users in this forum with no updates or ETA. It would do them well to squash the rumors going around that it is a licensing thing with the audio tracks...
Hello BobMoyer - I have not seen anything official from Magix. They can push advertising when you start up their programs, but after 2 weeks of this problem: not a word. It would be nice if they pushed a message with an ETA for the fix, or maybe even sent a robo-email out to all the registered users. I've seen nothing but posts from users in this forum with no updates or ETA. It would do them well to squash the rumors going around that it is a licensing thing with the audio tracks...
@Doug-Buseck
Magix staff here (hint, the username has Magix in it) have told us on the forum a fix is in the works for VP 18 at least, and also explained the cause of the issue. They never post ETA to updates as I assume quality assurance or other testing means its ready when its ready.
Here's one source (VegasDerek) for MTS with surround sound: https://www.vegascreativesoftware.info/us/forum/vegas-movie-studio-17-0-204-crashes-just-looking-at-m2ts-files--128621/#ca800053
There aren't rumors about AC-3 licensing either, the engineers clearly stated facts about no longer having Dolby support here
This is why it became an issue re: AC-3
"AC-3 support has not been dropped. We are now using the Windows OS codec for any AC-3 encoding and decoding in VEGAS. A bug does exist with mpeg files using AC-3 and we are working to get that support back in place."
For further info just search a bit- this is what I found in a couple minutes of searching for MTS and AC-3.
@RogerS wrote
Magix staff here (hint, the username has Magix in it)...
Actually, as you later quote (VegasDerek), (most of) the VEGAS team members have VEGAS in their username, not MAGIX.
The team members also have "MAGIX employee" mentioned in their profile.
Oops, that's what I meant.
VegasDerek had a response in this other related thread: https://www.vegascreativesoftware.info/us/forum/vegas-17-and-windows-update-20h2--128913/
Blaine-Witherow - Thanks soooooo much for sharing that link to VEGASDerek's 5/3/21 message. My original point of poor communication from Magix still stands: Why is that critical message buried in one thread with a title to one specific versions of Windows 10? I would not have read that thread based on the title. When there is a program-critical fail as with this Windows update issue, Magix should email all registered users with such information. RogerS - I read your suggestion about "...just search(ing) a bit...". I guess the near-daily checking in the forums between my original post on 4/19/21 and VEGASDerek's message of 5/3/21 wasn't enough effort on my part.
The search feature is quite handy for finding info you may have missed. There were many threads about this issue over the past few weeks. I was able to use it to compile some info on it here in one place.
Most of us aren't using MTS files with surround sound so it's a non-issue, but I can see for some it is critical.
Magix has never sent blast emails to date, though the news update within Vegas could be a way to provide info like this (and not just sale info).
@Doug-Buseck I am glad the message was posted anywhere, but I was surprised that it wasn't posted here, given the moderator vkmast started this thread specific to this issue
It's not every day of the week that a moderator starts a thread, and when they do its usually significant.
I doubt very much that this is a non-issue.
I agree with @Doug-Buseck, the thread should come from Magix, be pinned, made urgent somehow and have proper title (current thread name "Windows Update Problem" looks for me as someone have an issue that Windows Update does not work).
I have not used VP for a while (was busy with other stuff) and when I faced the issue I did not realize that it is caused by specific windows update or mts sources (that is m2ts in my case).
Tried to roll out GPU/CPU drivers (that I updated recently), tried to made some other changes on PC until found one related thread about mts by pure incident.