Here is how to fix Patch KB 3105208 endless BSOD's
As of last night, Windows insiders who have updated their systems with the latest Windows Preview Build build 10565, have reported an endless loop of BSODs, caused by patch KB 31052008, which was released yesterday.
While there isn’t much information on what the patch actually does, the issue seems to be somehow linked to Secure Boot, a feature found on many new laptops. Secure Boot provides protection to the boot loader on many new devices through encryption.
By this token, we can only assume that the latest patch is designed to somehow interact with Secure Boot, however, given the experimental nature of all preview builds, one has to prepare for these types of scenario.
Disable Secure Boot
Disabling Secure Boot involves entering a laptop’s BIOS settings, but that alone won’t solve the problem, if the patch has already been installed.
The “easy” solution is to plug a USB flash drive into a different computer, and create a Windows 10 installation media using the tools provided by Microsoft.
Once the USB drive is ready, we’ll simply insert it into the affected laptop, boot into the Windows 10 setup program, and choose the repair option at the bottom of the installation window, and navigate to the recovery screen, where we’ll be given a chance to choose the last working restore point.
While the recovery procedure will likely give you an error and quit, strangely enough, Windows seems to be restored anyway upon restarting. With that in mind, do not go into Windows Update just yet. First, reboot your device, and disable Secure Boot.
Once that’s done, it should be relatively safe to let Windows Update do its job.
Be a “common folk” for a little while
This might be a little tough to digest for a lot of techies out there, like us, but the “easier” solution, and yet the most painful if you really want to be a Windows Insider, is to roll back to an earlier restore point, and simply stop receiving preview builds, which means “sticking it with the common folks” until Microsoft fixes the problem, which is fine. Boring, but fine.
One thing to remember is this, once again: this problem affects only Windows Insiders. This seems to be a fact that too many pundits conveniently forget, when trying to build hype.
Once a user joins the Windows Insider program, such user accepts the responsibility of introducing unsafe, partially untested software into their machines, whether they elect to receive slow ring updates, or fast.