New
#1
It seems that for some disabling the secure boot does fix the problem. I had it disabled from the start so this wasn't an issue when I got the update yesterday.
Read more: https://t.co/BrJBTrKDF5Users claim Microsoft has just shipped a botched update
Botched updates are not something new for Microsoft, but it seems that almost every single update that the company releases for Windows 10 is actually causing problems. Not for too many users, but still.
This time, it's the Windows 10 Insider Preview October Update for x64-based systems, or KB3105208, as it's being called in Microsoft's documentation.
As you can easily figure out by reading its name, this is an update specifically released for users running a preview build of Windows 10, so if you're still on RTM, then you're safe.
On the other hand, if you're running build 10565, prepare for the worst.
A number of users are reporting that KB3105208 is causing BSODs on their computers, and for the moment, there doesn't seem to be a fully working solution that does the job for everyone affected.
It seems that for some disabling the secure boot does fix the problem. I had it disabled from the start so this wasn't an issue when I got the update yesterday.
I had this problem and after BunnyJ suggesting to turn off Secure Boot it fixed the problem for me.
Shipinomore
As of this morning I went back and tried to change the secure boot to enable after the update and it caused the BSOD again and so I then went in and Deleted the update and then I was able to change the Secure Boot to Enable.
I feel now that all is as it was and now waiting for either 10585 or Nov. 2nd when the so called Fall Update is to be released?
Shipinomore
Last edited by shipinomore10; 24 Oct 2015 at 13:50.
The only problem is that if you enable secure boot after you had successfully installed KB3105208 and restarted the PC to Windows, you will get the BSOD again.
KB3105208 PROCESS1_INITIALIZATION_FAILED Bluescreen - Microsoft Community
I don't seem to have this update installed. I'm currently running build 10568, which it's been working even better than 10565 for me :)
Read more:https://t.co/GRZPBWc8IxRedmond confirms the only solution is to disable Secure Boot
One of the updates that Microsoft recently shipped to computers running Windows 10 Insider Preview build 10565 was causing BSODs all of a sudden and in some cases, made it impossible to boot to the desktop and access files.
We first reported on this issue yesterday morning when the first reports on the issues caused by KB3105208 started reaching the web, but it turns out that this was actually a widespread problem that was eventually acknowledged by Microsoft too.
Gabriel Aul, head of the Windows Insider program, confirmed the botched update a few hours ago and also revealed that Microsoft has decided to pull KB3105208 completely to prevent more PCs from getting it.
What's more, Aul confirmed that the solution we provided you yesterday to disable Secure Boot is the only workaround for this problem in case you've already received the update.
I went back and uninstalled KB3105208 then went back in and set the secured boot back to Enabled and all is fine.
shipinomore
Because I experienced the BSOD recently, I went back to 10240. Oh well.
Is there any kind of analysis of what computers (brand or whatever) seem to have these types of problems? I have two Dell computers and have never had a problem with an upgrade or update. I did turn off the whole upgrade notice "app" on 2 older Dell computers and 2 Dell tablets because of all the reported problems.
My ASUS P8H77-M-PRO based system has also never had any real problems since Oct 2014, including Secure boot with the 5208 update. Would be interesting to know why a few systems escaped the 5208 one. Perhaps MS tested it on my mobo!!