Last week, Microsoft began the relaunch of the Windows 10 October 2018 Update after pulling it more than a month ago due to a file deletion bug that somehow crept into the shipping build. While Microsoft has since gone into extensive detail as to how it’s making sure something like this doesn’t happen again, it’s still unclear how such an issue made its way into the final release. So I did some digging.
Short version: Microsoft conflated two different bugs.
> Microsoft has introduced a new severity rating system in the Feedback Hub, for example, to help combat this. Insiders can now rate the severity of an issue on a scale of one to 10.
This isn’t going to fix a cultural problem like dismissing user’s bug reports. If this had been in place a year ago both bugs would have been rated 10/10 by users and they still would have been conflated by the engineers.
Well throwing out 50% of your testers does not help quality either, does it?
I don’t think there is a solution when there are errors that occur without error codes, stack traces or other relevant logs that can be reviewed.
Maybe there were logs here that were missed? Not sure specifically.
In this case, there was a non bug and a bug that had similar descriptions. They added a visual cue to people to prevent the confusion in the non bug, they should have also added a log somewhere when that known condition happened that would allow them to eliminate any confusion between this and any future bugs.
Easier said than done, and I understand you can’t anticipate future bugs that everyone thinks should never happen. But I still like the idea of logging when a confusing situation happens to a user to prevent future confusion from other people looking at an issue.
If you are tried to find that how you can play this game https://heartsgameonline.net you must be play this game with created the name when you ask to reboot the game then again you have to create the account.