{"id":477,"date":"2015-10-23T10:20:41","date_gmt":"2015-10-23T10:20:41","guid":{"rendered":"http:\/\/borncity.com\/win\/?p=477"},"modified":"2020-12-12T23:49:25","modified_gmt":"2020-12-12T22:49:25","slug":"windows-10-kb3105208-causes-process_initialization_failed-bsod","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2015\/10\/23\/windows-10-kb3105208-causes-process_initialization_failed-bsod\/","title":{"rendered":"Windows 10: October Update KB3105208 causing BSOD PROCESS_INITIALIZATION_FAILED"},"content":{"rendered":"

[German<\/a>]Windows 10 Insider Preview-Testers are facing a blue screen PROCESS_INITIALIZATION_FAILED after Security update KB3105208 (issued yesterday) has been installed.<\/p>\n

<\/p>\n

\"\"This morning I was notified about a new update for Build 10565 of Windows 10 Insider Preview (sorry, it's a German Insider Preview, so all screen shots are in German).<\/p>\n

<\/p>\n

A restart has been scheduled \u2013 and I decided to reboot the machine (because I intended to use the machine for some Win 10 related work). During reboot I was facing a blue screen, reporting PROCESS_INITIALIZATION_FAILED. <\/p>\n

<\/a><\/p>\n

The blue screen of dead (BSOD) occurs directly after installing Windows 10 October Update KB3105208 during the first reboot. Having a short look into the mini dump file (after the machine was fixed), showed me this.  <\/p>\n

<\/a><\/p>\n

Obviously a NTOS kernel error prevents the system from boot (I haven't analyzed it further, because I haven't installed WinDebug anymore).<\/p>\n

<\/p>\n

Gladly the automatic repair failed and Windows RE<\/a> came up with the message shown above, so I was able to select Advanced options<\/em> to gain access to the following Windows Repair Environment (Windows RE) menu. Using the Advanced <\/em>options <\/em>enables me to select the Troubleshoot <\/em>entry.<\/p>\n

<\/p>\n

And then the following Windows RE Advanced options <\/em>menu with extended repair options was offered.<\/p>\n

<\/p>\n

System Restore<\/em> was not possible, because this feature reported, that no restore point was found \u2013 installing a Preview build disabled this feature (as I experienced in the past). But I was not alone \u2013 in MS-Answers forum is a discussion<\/a> about this issue. And I came across two reddit.com posts here<\/a> and here<\/a>. In both posts someone mentioned, that disabling Secure Boot in UEFI settings should cure the BSOD. <\/p>\n

I selected UEFI Firmware Settings<\/em> in Windows RE menu (shown above). And after a reboot I was able, to navigate to UEFI branch Security <\/em>and disable Secure Boot<\/em>. Saving this using F10 key solved the problem. My Windows 10 Insider Preview was able to boot. <\/p>\n

I haven't tested, whether uninstalling KB3105208 and blocking it, using wushowhide.diagcab <\/em>(KB3073930<\/a>), will solve this issue with Secure Boot enabled. OK, to be fair, we are discussing about an update for Inside Preview builds \u2013 but the automatic update can ruin also productive Windows 10 machines. This new episode of a Windows 10 update failure rembers me to mention the change.org petition What Computer users want changed in Windows 10<\/a>, my MVP collegue Susan Bradley set up. I can't believe it \u2013 according to Microsoft, there are 110 million Windows 10 users \u2013 and less than 5,000 users actually has already signed this petition. So, please sign this petition \u2013 we need a feature (also in Windows 10 Home) to disable automatic update install – otherwise I can't see, that Windows 10 will be a stable foundation for productive work environments. Or do you have other thoughts?<\/p>\n","protected":false},"excerpt":{"rendered":"

[German]Windows 10 Insider Preview-Testers are facing a blue screen PROCESS_INITIALIZATION_FAILED after Security update KB3105208 (issued yesterday) has been installed.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[153,152,154,76],"class_list":["post-477","post","type-post","status-publish","format-standard","hentry","category-windows","tag-bluescreen","tag-kb3105208","tag-process_initialization_failed","tag-windows-10"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/477","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=477"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/477\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=477"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=477"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=477"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}