As of last Thursday, MS added recently — and widely — reported issues with Windows Search to its Known Issues list for 1903. The language of the item appears in the screencap below, and makes reference both to high CPU usage and lack of search results. Given that such reports stated surfacing from Insiders on August 26, and regular users on August 30 (release dates for this CU to those respective populations), this gives us a sense of how long the process takes. What process? The process of receiving, checking, verifying and publishing a bona fide Windows 10 1903 issue to the Known Issues list, of course. Here’s what that item looks like, which is dated — and made its initial appearance — on September 4 as shown.
Reports about search (CPU and lack of results) started appearing almost immediately after the August 26 Release Preview release, and picked up markedly after the General 1903 release August 30. Those reports hit the issues list on Wednesday, September 4.
[Click image for full-sized view.]
How Quickly Should Issues Percolate Onto the List?
That’s actually a pretty good question. Looking at the list itself, it seems like something on the order of 4-7 days is typical. But that timing seems to apply to release dates for general 1903 availability, not to Release Preview. I guess that makes sense. We’ve seen evidence that MS will delay transitioning from Release Preview to general release when Insiders report sufficiently severe errors. I’m thinking of the 1809 issue that popped up when those who upgraded lost OneDrive files (which mostly proved recoverable) as a consequence of its application. If memory serves they fixed this issue before making the upgrade generally available.
Thus, it’s interesting to get a sense of how Microsoft reports on and reacts to problems that, while vexing for those who fall subject to them, are less serious than posing the possibility of data loss. While it might be nice to see the issues on the list show up and turn over a little faster, I have no trouble understanding why it takes 4-7 days to go from “general report in the wild” to “appearance on the issues list.” I just hope MS remains as transparent and quick to react (and fix , work around, or mitigate) open issues sooner rather than later. To me, this shows not just that the process is working. It also gives some inkling of how it works, and how long it takes to make its way from intake through official channels to the Known Issues list itself. Good stuff!
Author: Ed Tittel
Ed Tittel is a 30-plus-year computer industry veteran. He’s a Princeton and multiple University of Texas graduate who’s worked in IT since 1981 when he started his first programming job. Over the past three decades he’s also worked as a manager, technical evangelist, consultant, trainer, and an expert witness. See his professional bio for all the details.