Fall Creator update fails to install at 81%

YES!  After 2 months of endless update failures, I found this article.  I was getting the following error every time it tried to upgrade:

0xC1900101 - 0x40017

The installation failed in the SECOND_BOOT phase with an error during BOOT operation

I removed my Asus wireless card and my system was finally able to update.   I was ready to give up soon but thank you!  And Microsoft really messed up with this update, give the number of people who have been unable to update to 1709.

All,

As a quick update, I had a Microsoft tech support person connect to my system and disable the updates.  The tech support person lost their temper with me and deliberately corrupted my system.

I connected with Microsoft, dwscribwd the problem I was having, and asked that someone assist me in disabling the automatic updates that werw crippling my system.  The tech support agent took control of my system, went into my Services and Reg and made a series of changes to prevent my system from updating any more.

When he was done, he told me that my system wasnt on the list of compatible systems with the new Update.  

When I disagreed with him and said I thought my system was on the Windows10 update compatibility list (btw he was right... it had been for the original Windows10 update... but not this one), he got very angry and proceeded to attack my system config.  Before I could kill the remote session, he had modified several settings in my Services and Reg file.  Even though I was frantically typing that he stop and kept trying to steal mouse control back.

When my system restarted, it failed in the middle of running the update.  The install was completely corrupted and I had to do a clean install after (an extremely difficult) backing up my hard drive in an attempt to preserve/protect my files.

Windows agents helped me with this, but it took 4 sessions of more than 6 hours each over a long weekend to do everything.

Now, all my apps and settings are gone.  My HD partitions are not what they originally were - and my drive is really struggling to cache properly. 

What's worse, the changes they made to limit my connection type artificially has compromised Symantec's ability to update and scan properly as well.  

I am beyond disappointed with Microsoft on the handling of this update.  This was a criminal act on the part of their tex   support agent as far as I am concerned.  I CANNOT in good conscience ever recommend a PC/Microsoft system again.  I will (and I can't believe I' saying this after siding with MS since the '80s) be switching to a Mac at my first opportunity.   This was a horrific experience and there is precious little MS can do to make it right, as far as I'm concerned.

It should be noted that Anatel private brands wireless boards for other companies. In my case, the card was labelled Asus, with an Asus part number. Flipping it over revealed the Anatel identification. This is why you may not notice Anatel appearing in Device Manager.

Bottom line: If you're not sure of the make of the wireless card, pull it out and investigate.

I was having a similar problem, and after multiple attempts (over 7 times) trying different solutions like disabling virus protection, disabling startup programs, running update database corruption repair, etc. My computer never got past 81% before freezing and not updating.

I stumbled across a forum talking about problems with  Anatel  PCI-E Wlan cards (wi-fi) and old drivers that would hang up their computers and after removing the card (not just disabling) their machines would update and run fine. Since I was running my machine through an Ethernet connection, connected to an access point, I could remove the Anatel card in my computer and still have an internet connection. I tried it, and my computer a Gateway FX6860 updated to Windows 10 Fall Creators version without any problems. 

Check to see if you have an Anatel wifi card and remove it and replace it with something newer or an Ethernet or usb connection to the internet and try the update. this worked for me.

I've been having the same problem with Creators Update (continuous crashes and blank screens between 75-81%.)  I tried every solution shown here (especially now that MS is force-feeding this update down my throat and is now constantly trying to update from 1607 to 1709) then I stumbled across your post.  I never paid any attention to the fact this PC did in fact have a PCI-e Wifi card plugged into it, as I never used it (This PC is hardwired with an Ethernet cable.)  So after my 5th crashed update since yesterday, I stumble across this post, pop the lid off my PC, pull that Wifi card out and lo and behold find out it's an Anatel (device manager never identified the card as such--it called it something from Ralink Technology and could not find anything that co-related the two companies.)

Windows is trying (again) to shove this update down my throat.  But this time without that wifi card.  If this works, I shall give you internet hugs * infinity.

UPDATE:  SUCCESS!!  A billion thank yous for sharing your solution.  I now am running 1709 and would never have connected the update failures to this WLAN card and its failed drivers.

Same here when trying to upgrade an old laptop from 1607 to 1703 or 1709.  Upgrading was failing both from Windows Update (gets stuck on a black screen during the upgrade) and Media Creation Tool (Upgrade freezes at 81%).  Removed the Ralink wi-fi card and it worked.