It remains beyond me that such a serious bug was missed and then ignored.
I don't think we should assume it was ignored. As I noted, it was first reported back in February and Microsoft released an update to fix it. And apparently it did fix it. But it resurfaced - or more likely was "reintroduced" when another update or modification came out.
But an update or mod to what? Who knows? It could have been an update to Windows, or some driver update by NVIDIA, the motherboard chipset maker or another HW maker, or a mod to the widget or to the code that runs the widget. IDK!
Again, we have to remember that essentially each and every one of the 1.6+ billion Windows machines out there are unique machines as we configure our own unique hardware combinations (from 100s of different makers), install our security and 3rd party apps, and well as our own Windows "Personalizations", changes to the defaults (a biggie!) and "tweaks".
Point being, it is unrealistic to expect that Microsoft, even with unlimited resources, could think of and prepare for every scenario possible, let alone test every possible scenario before releasing updates. And again, this apparently is only affecting a tiny percentage of people. AFAIK, this is the only thread at TPU on this topic.
Personally, with 50 million lines of code, I'm amazed more people don't encounter more bugs all the time!!! The Microsoft developers deserve some credit there, despite our personal feelings about the company itself.
"Serious bug", in this case, is a very relative term. Does this issue affect computer or user security? Apparently not! So is it really a "serious" bug? It certainly is not "critical" - at least not IMO because it is not a security issue. Nor is it (as far as we know) affecting [100s of, 10s of, or just] millions of users.
Now for sure, even if 0.1% of those 1.6 billion users are affected, that is 1.6 million users! And that would be a lot of upset users - users who deserve to be heard and NOT ignored.
So again, since you are one of those few impacted, then indeed, it "IS
" serious for you! So in no way am I trying to downplay the problem. This is especially true if it causes your system to lock up, or worse, you lose data. That would be totally unacceptable. But I just don't think "serious" for a relatively few users (when security is not an issue) can, or even should constitute a top priority for Microsoft - not when there are armies (some state sanctioned!
) bad guys out there actively intent on conducting "serious" malicious harm.
Also, and I know you already are fully aware of this Andy (so speaking to the crowd), fixing problems is easy and usually quick too! It is the actual troubleshooting required to pinpoint the problem where the expert knowledge, training, experience and invested time consumes the vast majority of resources. And when troubleshooting unseen, obscure problems, if you cannot duplicate the problem at will
, then pinpointing the defect/bug becomes a nearly impossible challenge. My point there is I believe if this was a simple-to-duplicate issue, Microsoft would have fixed it once and for all the first time around.
Of course, I could be wrong.