Last week it came to light that Microsoft had pulled the Spring Creators Update to Windows 10 at the last possible minute due to some sort of show stopper bug. But nobody knew what the bug was.
Well, thanks to this post from Dona Sarkar who runs the Windows 10 Insiders program, we do now:
As Build 17133 progressed through the rings, we discovered some reliability issues we wanted to fix. In certain cases, these reliability issues could have led to a higher percentage of (BSOD) on PCs for example. Instead of creating a Cumulative Update package to service these issues, we decided to create a new build with the fixes included.
I’ll give points to Microsoft for not shipping dodgy code. But it does highlight one thing. Windows insiders (which is Microsoft speak for public beta testers) found this issue. It was not found by Microsoft’s QA department. The fact that it slipped through Microsoft’s internal QA and almost made it out to the planet is kind of bad. Maybe they need to step up their game on that front. Otherwise, they’ll have a QA department as bad as the Apple QA department is at the moment. Just a thought.
Like this:
Like Loading...
Related
This entry was posted on April 17, 2018 at 7:53 am and is filed under Commentary with tags Microsoft. You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
Microsoft Says That Windows 10 Spring Creators Update Delay Due To Blue Screen Of Death Issues
Last week it came to light that Microsoft had pulled the Spring Creators Update to Windows 10 at the last possible minute due to some sort of show stopper bug. But nobody knew what the bug was.
Well, thanks to this post from Dona Sarkar who runs the Windows 10 Insiders program, we do now:
As Build 17133 progressed through the rings, we discovered some reliability issues we wanted to fix. In certain cases, these reliability issues could have led to a higher percentage of (BSOD) on PCs for example. Instead of creating a Cumulative Update package to service these issues, we decided to create a new build with the fixes included.
I’ll give points to Microsoft for not shipping dodgy code. But it does highlight one thing. Windows insiders (which is Microsoft speak for public beta testers) found this issue. It was not found by Microsoft’s QA department. The fact that it slipped through Microsoft’s internal QA and almost made it out to the planet is kind of bad. Maybe they need to step up their game on that front. Otherwise, they’ll have a QA department as bad as the Apple QA department is at the moment. Just a thought.
Share this:
Like this:
Related
This entry was posted on April 17, 2018 at 7:53 am and is filed under Commentary with tags Microsoft. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.