KB3105208 update for Windows 10 Build 10565 pulled as it caused BSOD for some users
Windows 10 has been drawing a lot of flak for the way it handles Windows Updates.
Microsoft does not allow users to disable updates, except for those being served by the Long Term Servicing Branch, who just get security updates, and skip all feature updates for a year.
The Current Branch for Business, also offers users the option to skip updates temporarily, but they will still need to install all prior updates before installing a new one. So any and every Windows update that Microsoft releases is automatically installed on Windows 10 devices. This is supposedly to reduce the fragmentation of the Operating System, as Joe Belfiore recently defended the update system, claiming that “Cumulative updates are essential“.
Now, what happens when a botched update hits users? That would be a horrible scenario, right? And that is exactly what happened when Microsoft rolled out the KB3105208 update to users. Fortunately the update was not released to the general Windows 10 RTM Build 10240.
The update was instead only rolled out to the Insider Preview Program, and so the unfortunate ones who got the update were those on the latest Build 10565. Once the update was installed, some users reported that they began to experiencing the infamous BSODs (Blue Screen of Death).
Apparently the issue was so critical, that Microsoft had to pull the update from its servers, so it does not impact PCs yet to be updated to it. This was officially confirmed by Microsoft’s Gabe Aul, on Twitter.
@thurrott KB was throttled to zero last night (no longer automatic) and now fully pulled.
— Gabriel Aul (@GabeAul) October 23, 2015
Aul also replied to the forum thread (linked above), asking users not to try a system restore as a resolution for the issue. The reason behind this, is that system restore makes the system unbootable. So much for providing a resolution Microsoft.
But in fact there is one workaround which Aul has suggested.
As many have mentioned, the temporary workaround is to disable Secure Boot so that your machine can boot correctly. Once we have a fix for the issue we definitely want you to be sure to re-enable Secure Boot for your protection. I’ll share more info on that when we have a fix in hand.
It is not clear how many users were impacted by this issue, as of yet.
I think its about time that Microsoft wakes up and realise what a serious impact its Automatic Updates are having on users, and mayb ejust maybe allow users to skip updates. But we know that’s not going to happen.