Big problems with M4A after updating to Windows 11 22H2

But no :-) KB5034765 was released, but the fix for a more than two-year-old bug was not included in this update. Bravo Microsoft, we love you :-)

Once again, the attitude is unnecessary and counterproductive.

Today's update was not the one that comes "sometime in the middle to second half of the month" as I had previously said. Really. That's exactly what I had said. Today is Feb 13.

Wait until end of month.

"Patch Tuesday" is not one Tuesday every month. It's every week. Each week is reserved for a different type of patch.

Pete

I checked with the team today and they told me they will let me know when it's out but to expect sometime in the middle to second half of the month.

Pete

Colleague, what you are saying is not entirely true. This problem has been known for a long time, even if you watch the videos in the first message, you will see in the comments that the problem was reported on the forums, on social networks and in the support center from various sources. I have signaled it myself many times. It's great that the new build has finally fixed this issue, but millions of people aren't using pre-release builds. It would be reasonable to release a separate small patch this coming Tuesday. Thank you, although of course my patience has already run out.

I'll reiterate what I said in an earlier post: posting videos and posting on forums doesn't actually let Microsoft engineering teams know about the problem. And forum posts typically contain no actionable data we can work with. Unless someone on that engineering team happens to stumble across that content, it's not getting to the teams, and even then, without the data, there's not much they can do. You may have known about the problem, as well as many others in the community. But again, no reports, and no data we could use to investigate.

Engineering teams typically aren't on these peer-to-peer forums, or manufacturer forums, etc. and aren't scouring YouTube for videos. Feedback Hub is available in all Windows 10 and Windows 11 editions on all channels (not just Insider). That's how engineering teams are made aware of bugs. When there are many upvotes or entries in a relatively short amount of time, or when a Microsoft employee promotes an entry, the entry goes into our bug system for evaluation. The more entries with recordings/repro steps, the easier it becomes to investigate and fix.

There are only two feedback hub entries on this topic and both are quite new. The first reply in this thread, back in May, links to how to post the issue to Feedback Hub, but that wasn't done. You even replied that the problem was already known. The problem on the Pioneer Dj rekordbox forum was also never reported to Microsoft by any companies or users there. Again, it wasn't actually known to Microsoft.

So, this problem was not actually *reported* to Microsoft until recently. Relying on others to report a problem that is important to you does not help get the problem fixed as you can see from this thread which is an example of everyone thinking other people had already reported the problem. Instead of linking to another forum, you could have filed a Feedback Hub report, with a repro/recording. It's quite easy to do. If the problem was important to you, it would be worth it to take a few minutes to do it -- less time than replying here :)

Then, if you feel a feedback hub report isn't getting appropriate attention, you can share a link to it in forums, videos, etc. If the Feedback Hub report is within approximately 1 month, or there is one within a month that contains the recording (the data expires for privacy and other reasons) they can take a look at it right then.

As for release: there's a defined path to get a change from internal testing to a production release in retail Windows. It will almost certainly take longer than next Tuesday. I will post here when I know when it will make it out.

Pete

As i wrote it day's ago as one of the first guy's.

We know about this bug since the start of win 11 but I never reported that bug because i thought, that one day it will be fixed. But now with 23h2 my patience had an end.

The songs in m4a have a very strange wave form. They get louder an quieter. They do not have a connstant volume. Thats the problem. You play the song and the volume jumps up and down the hole time ...

Only on Windows 11

I went back to win 10. There is no porblem there ether on Mac or Linux. Only Win 11 an m4a.

Yes, we know about the issue now. But because no one had actually reported it, we're only hearing about it now.

The main ways we find out about bugs:

1. Our testing before we release. If we don't catch a bug then, and the product releases with it, then it's a scenario we're not testing for.
2. Telemetry in the case of crashes (this is not a crash so that wouldn't happen)
3. Partner reports in partner center (there's one recent report on this topic from a month ago. Nothing older than that)
4. Feedback hub reports.

Because none of those things were present, we didn't know we had a bug, and so we wouldn't know to fix it. I appreciate that you ran out of patience and reverted to an older version, but you all were waiting for us to fix something we didn't know needed fixing.

That's why the first reply in this thread says to use Feedback Hub to report the bug.

Pete