Windows 10: Cannot install any builds AFTER 10130/ not 10158 up to 10240

I've posted this before, but I need to know if anyone know exactly what has changed on builds after 10130, which install and runs completely fine on my AsRock h97m Pro4 board. The bios settings are the same throughout all previous builds on and before 9978 to 10130.
0xC1900101 - 0x20017
Something MS changed after 10130 that has made it totally impossible for me to do a update install or a iso clean install (restart death loop from hell after a brief showing of the Windows Logo).


:)

 

windows 10 build 10158

is the build 10158 for the home edition and/or pro edition. I had to download the iso file for build 10130,because of the know issue and went from home to pro edition.

 

Can't open anything with a left click, aloso many other issues on Build 10122

Right now it is stuck on trying to download 10130

• fbl_impressive Professional 10130 - Error 0x80246017

Any help on getting around this and going straight to 10158

Skilly

 

I just gave up and went back to Windows 7 until RTM. It's been confirmed by multiple people now that it doesn't work with the G3258.

Cant install Windows 10 build 10162 on Gigabyte H81 motherboard - Microsoft Community

 

Wow ... wow... omg, wow, I had no idea - - - thank you for that link, (I think) - starting to make a lot of sense now...

 

Sign in with Microsoft Account, install the updates, then you can switch back to Local account (Settings->Accounts).

 

Failed and fresh .iso installs happened the same way, and installing from within 10130 happens fine until the computer reboots - thats when the trouble starts, at the boot process. Thanks anyway.

 

Just got a fix for this, go here here if you have this problem:

10162 update and iso install total fail 0xC1900101 - 0x20017 - Microsoft Community

Worked for me, but can run only (1) core while running 10166, better than nothing, and at least the issue is known...*Mad/*Biggrin

 

Sorry Guys, I just hate not knowing and don't give up until I do - anyway, here's my most recent update on this issue.

*** KB3064209 ***
JUNE 2015 Intel CPU
microcode update for Windows

Appears to be the real villain here. This broke many g3258 users, even Win7-8.1 users immediately after updating giving them the same startup 'death loop'. I sense it was combined into builds after 10130, so up to 10240 is going to already g3258 nuke ready.

If I find a fix for this that needs to be put on blast I will, but I suspect the fix itself will need to had come from the Top (MS) enough for us to know right away... I hope

 

I get a similar error code 0x101-0x20017 when I try to upgrade from Windows 8 to Windows 8.1 and even Windows 10 (earlier builds not 10240) and I suspect the Intel Core Duo T2250. I will wait for the RTM and try an upgrade or clean install once more.

 

Since MS hasn't even acknowledged the problem, I wonder if it would be possible to edit the install image with DISM to replace the files introduced by KB3064209 with ones from 10130.

 

I almost tried that - but it became complicated really quick, thinking even if inserted something from 10130 successfully, the main problem is REMOVING KB3064209 integrated from any .iso (etc 10240), but if i'm not mistaken we're not allow to do any of that anyway.

A fix HAS to come at some point, though it may take a thousand years as I like to say. I am looking out for something daily...*Sick

 

Some people are saying that if you disable a core in BIOS, install Windows 10, then delete or rename mcupdate_genuineintel.dll in System32, you can re-enable the second core. I tried deleting that DLL from the install image and it still crashed, but I've yet to try this method.

 

Just tried it, and it works, overclock and all! *Biggrin