I installed KB5035942 and unless I'm severely mistaken, the issue seems to be resolved.
Can anyone else confirm?
Big problems with M4A after updating to Windows 11 22H2
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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.
Answer accepted by question author
Anonymous
115 additional answers
Sort by: Oldest
-
Anonymous
2024-03-27T09:49:40+00:00 I confirm that KB5035942 solves the problem. At least a few tracks with which there were problems are now displayed and played normally. I hope that it will be the same with the others, although there is no more trust in Microsoft, but I hope that the two-year saga is successfully completed. True, as usual, Microsoft “completely accidentally forgot” to indicate in the list of fixable problems KB5035942 that our problem was also fixed, as if it had not been observed for two years. Honest guys.
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Anonymous
2024-03-30T20:44:24+00:00 I installed KB5035942 and unless I'm severely mistaken, the issue seems to be resolved.
Can anyone else confirm?
The volume and waveform fluctuations seem to have been fixed! I did notice a small thing (on Rekordbox at least) where the volume of purchased AAC/M4A tracks are noticably louder than the MP3 and manually encoded AAC/M4A versions. This should hopefully be a non-issue since we can manually dial down the gain very easily on our controllers, but I just thought that I'd point that out.
Big thanks to everyone here who reported the bug and to Pete Brown and his team for working on it!
-
Anonymous
2024-03-30T21:44:06+00:00 Another data point: installing the "2024-03 Cumulative Update Preview for Windows 11 Version 23H2 for x64-based Systems (KB5035942)" update has fixed the problem. I use the built-in Groove Music/Media Player app to listen to music, and having my audio volume suddenly start fluctuating from song to song had been pissing me off for so many months. I am very glad to finally see the resolution. Thank you to everyone who worked on reporting and fixing this issue--it was one heck of a journey with plenty of ups and downs, but we got there in the end.