Have tried the solutions for the other C1900101 errors reported in this forum and have tried to install Windows 10 8 times to no avail. Have uninstalled Nortons and turned off the Windows Firewall and Windows Defender.  Have a couple of hundred Gig spare in C:.

My last install failed at 70% complete.

Any solutions??

regards

Flash

Hi FlashGP,

What is your current situation, after it fails, did it revert back to the previous Windows?

C1900101-40017 means

SP_EXECUTION_SECOND_BOOT 4  SP_EXECUTION_OP_INSTALL_RECOVERY_ENVIRONMENT<o:p></o:p>

Which indicates that the setup fails at the installing Recovery Environment part of the installation.

If available, please find us the setupact.log and the setuperr.log file under the following path:

$windows.~bt\Sources\Rollback (this is assume you have rollbacked to the previous Windows)

Reference: https://technet.microsoft.com/en-us/library/Hh824819.aspx?f=255&MSPPError=-2147217396

Also please share us your current disk configuration, use Diskpart: list volume (reference) and then share us the screenshots here.

Regards

It did not fail at that point according to the update process itself.  The update was in the process of installing drivers, failed, and "We are re-installing your former version of Windows", provides that code (C1900101-40017) and "get help for this error" which is a MS link and leads nowhere.  My machine is an Acer and according to various Acer notes the tablets, AIOs and laptops are all tending to experience this problem (similar, oddly enough, to the HP Pavilion laptops, although the HP Pavilion AIOs seemed to update/upgrade nicely.  The reversion to 8.1 was smooth; the initial upgrade to 8.1 from 8.1 was rocky and involved 800240 and removal of the anti-virus and similar software (like rootkit-sniffers).  My Dell AIO and Acer laptop in fact did update smoothly--but another Dell laptop struggled to do the 8.1 and is still choking on 10...with no codes at all.

I'm sure you feel you know the meaning of the codes, but this isn't smooth and they aren't meaning the same thing for all machines.  I'll be happy to provide whatever data you need.  oregonnerd would be the one at gmail preferably.

I had this error twice trying to upgrade from 7 on my netbook. I disconnected all peripheral connections, made sure that W7 was updated with all available updates until only W10 was left, did a disk clean and then started the upgrade again. It appeared to hang up again at the same point but this time when I restarted it continued the upgrade (from 75%) and completed successfully. Not sure if this helps but I must have done something right. MSI U135DX netbook 2G ram

Nymmers,

Yes I agree with that the information may be vary, the error code just shows the process part, for the related stuffs about what the setup is doing, we need to take a look at the rollback log.

$windows.~bt\Sources\Rollback

Reference: https://technet.microsoft.com/en-us/library/Hh824819.aspx

Please understand that any personal information sharing is not officially allowed here.

If you would like us to take a look at your situation, then please find the log under the path I wrote above, then upload it into OneDrive, and post the shared link here.

To d35mond,

Thanks for the update.

Which I suppose the right thing should be the disk cleanup and the peripheral connections, which allow the system not keep searching the related drivers.

Regards