Share via

Big problems with M4A after updating to Windows 11 22H2

Anonymous
2023-05-16T09:52:13+00:00

Dear colleagues, after updating Windows 11 to 22H2, there were significant problems with playing files purchased from iTunes in .m4a (AAC, ALAC) format. This problem has been fixed by a lot of people all over the world and is especially evident on the DJ forums. Problems are observed with the quality of playback, and with the volume and with a number of other parameters. This problem is detected on software that uses the built-in Windows 11 22H2 codecs (on earlier versions, the problem is not observed), Windows Media Player, RekordBox, Serato DJ Pro, etc. On players that use their own codecs (VLC, iTunes, JetAudio HD, etc.) there is no problem. When converting m4a to mp3, there are no problems. What it looks like: https://youtu.be/WqAA12pfWjg and https://youtu.be/um3QSTuLg6s Software vendors fix this issue after the 22H2 update as well, label it as a Microsoft issue and offer a workaround, such as converting the entire m4a database to other formats, which of course is completely unacceptable advice with a database of several thousand files. https://forums.pioneerdj.com/hc/en-us/community/posts/12212808237337-RekordBox-5-8-7-m4a-problems Does Microsoft acknowledge the existence of this problem and when is it planned to release an urgent fix, since. the problem has been observed for a very long time and prevents normal operation?

Thanks in advance!

Windows for home | Windows 11 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

  1. Anonymous
    2024-03-27T00:42:35+00:00

    I installed KB5035942 and unless I'm severely mistaken, the issue seems to be resolved.

    Can anyone else confirm?

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments

115 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-03-01T22:44:39+00:00

    Update:

    The team has figured out what happened. It really was working in the test builds, and in the Insider builds. However, there was a configuration mistake when this was moved to the retail release. That resulted in the corruption effect because it wasn't a complete release. The code works, and is still in the Canary Insider builds.

    The team is doing two things:

    1. Disabling the current codec fix in the releases that are going out so more folks don't run into this, and we don't make it any worse. I'm not sure when this updates on the download servers but it will be at least a few days.
    2. Getting the configuration into, we hope, the end of month's fixes. Yes, this will mean at least one more month of waiting. The fix date is not yet confirmed because this is fresh from the team today. Once I know an actual planned date, which is not guaranteed to be this month, I'll update here. The feature team gets the urgency of the situation, as do I, and this is a shorter period than it usually takes to roll out a non-security update.

    Please also note that "Patch Tuesday" is a public interpretation of what we do, but they aren't always on Tuesdays -- we go by weeks of the month, and the day that rolls out for you also depends on your configuration, update settings, geo location, and more. We never refer to patch Tuesdays internally, so end of month really does mean up to the last day of the month. Your continued patience is appreciated.

    We have all the data we need on this, and no longer need any more feedback hub entries or reports. Thank you to all who have provided them.

    If you've already downloaded and installed the current update, I recommend uninstalling it while you are within the time window to do so.

    Once again, sorry for the impact and bad experience here.

    Pete

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments
  2. Anonymous
    2023-10-26T19:00:42+00:00

    When is this getting fixed FFS!?!?!?!

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments
  3. Anonymous
    2023-11-08T13:11:30+00:00

    It´s still not fixed! Update 23h2 08.11. F. Microsoft for that! You had over 2 years time! Whats going on! Money is running from us with that realy BIG PROBLEM!

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments
  4. Anonymous
    2023-11-14T09:25:55+00:00

    So we are talking two years! It took me countless hours to even figure out, that the issue was Windows 11 and not something else. Seeing this and sweatting through various DJ Sets that it wont be too noticable I am contemplating of abandoning Window alltogether I might move over to Mac since it will also run all my producer tools. Beeing a "Hobby DJ" I can only wonder what it must be like for people who make a living out of DJaying and with Rekordbox beeing affected probably a few thousand Dollars worth of equipment, that cant be used with their Windows 11 Computer for several years now.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments