Last Friday I actually wrote about troubles reported with this month’ s Win10 1903/1909 Total Update, KB 4549951. Besides a recurring bug that creates temporary profiles  — the bug we’ ve talked about for months that leads to wonky desktops and misplaced documents — I couldn’ big t identify any patterns within the hue and cry.

A few hours later, Ms officially acknowledged the issues in a rather odd quilt statement, posted on both the particular Windows Launch Information Status page and the Information Base article :

Social media reports related to difficulties with KB4549951

We now have seen social media reports associated with KB4549951 that mention Bluetooth, prevent error with blue display screen and other related issues.

Affected platforms:

• Customer: Windows 10, version 1909; Windows 10, version 1903
• Server: None

Next actions: To date, we have not observed these issues reflected in telemetry, support data or customer opinions channels. We continuously check out all customer feedback and are carefully monitoring this situation. Note In case you experience any issues we would like to know. Please provide suggestions using the keyboard shortcut Home windows + F or navigate to the Start menu and select Opinions Hub so that we can check out.

Upon first glance, that’ t great: Microsoft’ s positively asking for help nailing lower these odd, seemingly unique, problems. We rarely observe that kind of proactive effort. Yet on second glance … wuh?

There have been dozens of headline-grabbing articles on the problems with this particular month’ s Cumulative Update  — not just in social media marketing, but in Home windows Latest , BleepingComputer , MSPoweruser , WinCentral , TechRadar , OnMSFT , and in several blogs in many languages, all over the world. The reports pull on voluminous reports associated with bugs that I’ ve seen, largely in social media marketing, including those in Microsoft’ s regular Windows 10 thread upon Reddit , all over Microsoft’ s Answers forum , and in the particular Microsoft Feedback Hub (search on KB4549951).

Odd that Ms doesn’ t consider those people “ customer feedback channels. ”

We utilized to see Microsoft engineers follow-up on specific complaints, straight contacting and working with clients who report buggy indications. I rarely see that take place now. Most of the one-on-one I realize about occurs with having to pay enterprise customers filing occurrence reports.

We don’ t know how a lot of those bug reports are legally attributed to the Cumulative Up-date, how many are simple coincidences, and exactly how many emanate from the feces of the massive Windows replicate chamber. I’ ve appeared for patterns and, aside from the temporary profile pester, haven’ t found any kind of. That isn’ t exactly what concerns me about Friday’ s post.

Here’ s what captured my eye: “ we now have not seen these issues shown in telemetry. ”

That’ s the phenomenal statement. And a frightening one.

Investigating many of the problems in the Windows-provided telemetry should be trivial. Once the Windows Update installer places in a new patch, a list gets sent back to Ms. When the system reboots, an additional record goes back. When Home windows triggers a blue display screen there’ s another. Once the installer doesn’ t function and rolls back, there’ s another one. And so on.

How hard can it be to find out if a specific Stop mistake (blue screen) immediately comes after an update reboot?

How hard could it be to see if a completely new user profile appears immediately after an up-date reboot?

Exactly how on earth could they not really see “ these issues” in the telemetry?

Microsoft has spent a massive amount of money on telemetry. Heading all the way back to the time associated with Dr . Watson, we’ ve been sending Microsoft huge quantities of data. And today they can’ t link these straightforward dots?

Meh.

We’ re subsequent intently on the AskWoody blog .