I’m not sure about that. There isn’t any evidence, that I know of, of a surge in complaints. Just a surge in reporting because one person blamed the update. storage fails all the time, so complaints are naturally constant.
Sorry for the double reply. Check this video, around 8:45 - someone managed to reproduce the issue, under different conditions, with the update in question. There’s also a second problematic update.
Here’s my hypothesis: from a quick websearch, a lot of people are getting error messages from this update (regardless of disk failure), it’s around 3GiB large, and classified as a security update. It’s possible that the system is trying to install it over and over and over, and this is unnecessarily stressing storage devices that would eventually fail anyway.
If my guess is correct there is a higher amount of complains, not just reports, but Microsoft won’t find the cause.
Of course, it’s just a guess - I don’t know if it’s correct.
I’m not sure about that. There isn’t any evidence, that I know of, of a surge in complaints. Just a surge in reporting because one person blamed the update. storage fails all the time, so complaints are naturally constant.
Sorry for the double reply. Check this video, around 8:45 - someone managed to reproduce the issue, under different conditions, with the update in question. There’s also a second problematic update.
Here’s my hypothesis: from a quick websearch, a lot of people are getting error messages from this update (regardless of disk failure), it’s around 3GiB large, and classified as a security update. It’s possible that the system is trying to install it over and over and over, and this is unnecessarily stressing storage devices that would eventually fail anyway.
If my guess is correct there is a higher amount of complains, not just reports, but Microsoft won’t find the cause.
Of course, it’s just a guess - I don’t know if it’s correct.