Big problems with M4A after updating to Windows 11 22H2

Thanks a lot, IT RINPHARM. We had finally gotten somewhere. And now we're back to nowhere.

Let me tell YOU something, my friend. Microsoft owes you and us NOTHING here. You chose to buy within another company's ecosystem, and take the results outside of that company's ecosystem. Shame on you, and shame on all of us for doing that. Caveat emptor. MP3 was the open standard, other vendors offered it, it STILL works, and we instead bought from a company with a closed-door reputation and took their licensed product outside of their fiefdom, which they explicitly advised against.

And we wonder why it now doesn't work.

M4A still works within Apple's closed-door ecosystem.

It was never guaranteed to work in Traktor or Rekordbox or anywhere else.

We gambled...we lost. Microsoft owes you NOTHING.

You want something else, something better, YOU build it. YOU pay for it.

from the ground up. I am a DJ but I am also a software developer and I am tired of hearing this kind of $#!t.

Go F off and find another solution.

Pete, I do appreciate your responsiveness. It's nice to be able to have some actual conversation. Thank you!

I actually did post about this in the Feedback hub about 6 months ago. https://aka.ms/AAns8g9 That's recent? I know you said to add videos and reproduction elements, and recheck the post in a month, and if there's no activity to go and post it more places, but I have no way of knowing if that will get more attention. Even if it did, there no way to know if any changes would occur. I may still do it next time (I appreciate the advice) but, in all honesty, I'm not getting paid for any of that work and I am a busy person.

I'd like to reiterate, I appreciate you and how you're actually being helpful here. I just think that the policies and methods used by microsoft are clunky and inefficient. It seems that's largely due to volume... So, in light of all this, I'd like to promote a suggestion that might help us all a whole lot: "Updates" are only mandatory if they are directly related to essential security updates. No more forcing an "update" that takes away a feature (like moving the taskbar). He's the feedback hub link https://aka.ms/AAnt63c
Considering the post for moving the taskbar (https://aka.ms/AAd2jme) has 27,000+ upvotes and no action has been taken, I don't think this will do it, but it's worth a shot.

Drew

Thanks. I didn't see your feedback hub entry because it doesn't have M4A in it anywhere (that's what I searched on previously). Good to know it's there.

FWIW, we don't need videos or similar, but we do need repro recordings. If you pick the Devices & Drivers -> Audio category when reporting something through feedback hub, you are able to record, right through the tool, what happens. Nothing else needed.

In this case, it was filed under Windows Security, so the audio team would never have seen it, and any recording would not have the correct data. I do wish the FB Hub tool had more guidance for picking categories.

On the taskbar docking: not sure where the shell team sits with that one, and why it hasn't been implemented in the new version (the taskbar was completely rewritten for Windows 11, which is why some catch-up was needed). They did take the feedback for not combining icons and showing icon labels and added that to a recent Windows 11 release, however, so they do listen, even if it takes a while.

Updates: I know that goes against the direction Windows has taken, so I wouldn't expect to see anything there. However, if you are running Pro or better, and know the risks, here's the supported way to disable updates:

https://devblogs.microsoft.com/windows-music-dev/take-control-of-windows-updates-on-your-windows-11-daw-pc/

Pete

Good afternoon. Since the problem has been confirmed and already fixed in the new build, can we hope that the fixes will be made to build 23h2?

Like I said yesterday, once I know when it will go out into retail builds, I will update this thread here.

We can always use more confirmations, and more importantly: confirmation from folks that the fix doesn't break anything else related to M4A that they rely on.

Thanks.

Pete

Thank you for your advice. I understand perfectly well that you can remove a specific update and even roll back a release to a previous version. Only the current list does not have the problem that I described. This is definitely a problem with the Microsoft codec(in 22H2) and I hope this little fix will be released soon.