The windows 10 fall upgrade 1709 fails after about 45% mark.. Then gives an error message and returns system to 1703

This worked for me.

I deactivated the Broadcom WFI in Device Manager and Uninstalled the Broadcom Software and Driver from App and a restart then Ran Check For Updates . Now up and running 1709.

Thanks

You were lucky... I ended up having to perform a complete reinstall of Windows and the applications..  (I also had to repurchase some licences... - costing $400)

But.. I am up on 1709.. with a clean install...

This worked for me.

I deactivated the Broadcom WFI in Device Manager and Uninstalled the Broadcom Software and Driver from App and a restart then Ran Check For Updates . Now up and running 1709.

Thanks

2018-02-07 12:24:58, Error      [0x018007] CSI    00000020 (F) Failed execution of queue item Installer: Generic Command ({81a34a10-4256-436a-89d6-794b97ca407c}) with HRESULT HRESULT_FROM_WIN32(14109).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]

Try looking at  setupact.log  for this one's context.  Also, the last messages show CBS.log (or archived pieces, since the CBS.log will probably be showing a rollback once you get to see it) might have some clues.

Did you try using my PowerShell script?  It could change our ideas of what would be worth looking at.  So far what we have seems inconclusive.

I really appreciate all your help....  but.. I have come to the end.....  I give up... I am going to back the system up... and then do a clean Windows 10 install....  I say ..  Microsoft - I say shame on you!!

Thanks for the help

I just spent 4 days installing a fresh Windows 10 pro and all my apps... and $400 (re-purchasing licences)...  and doing all the configurations again......

I have a bit of tweaking to do still...  but the lion's share is done.... 

Doing a complete reinstall would have been easier if I had selected this option back in November.. but who would have thought that Microsoft would have released such a challenging update...

Sigh

Hi Andrew,

Thanks. I finally found the solution to my problem here: https://forums.iis.net/t/1229869.aspx. The Wireless broadcom driver, even after uninstalling leave some registry entries that caused the problem. I de-activated the Wireless device in BIOS, removed the driver completely, did not allowed Windows Update to update the driver and finally went thorugh the registry and deleted every reference to Broadcom I could find. "After a bunch of digging, I found my problem was that my Broadcom Wireless driver had added some registry keys to HKLM\SYSTEM\CurrentControlSet\Control\Cryptography\Providers and iissetup.exe was just picking the first provider from the list, which was the Broadcom one, and failing."

After i did that, I also proceed with the USB-ISO created installation(Setup) without any connection to Internet (unplug Ethernet cable) and I also clicked to not make updates before installing(which is the recommended option during setup).

Then I am now with 1709 with latest January updates. Wireless Broadcom driver is back enabled up and running as well. 

this fixed mine. iv been using ethernet for quite some time but i checked those registry entries and it had broadcom so i simply deleted the entries for it. there were 2. i ran a full search for broadcom as well, found a few other entries for it regarding SHA256. the prior entry had a microsoft entry in the key so i copied that over the broadcom entry as it referred to the earlier keys i removed.

to note: i dont have any wireless adapters installed as id already removed them. had an old netgear, dlink and tplink over the years. most recent being the tplink. all software had already been removed.

downloaded the update and it went perfectly. though asus aisuite had an issue after the restart. i'll just reinstall it. i was only using it to monitor temps anyway and i fixed that issue a while back.

This helped me - finally after a couple of months!!! THANKS!!!!

Thanks for the tip....  but I gave up trying to find the problem and I started with a fresh Windows 10 pro install...   I now have 1709 installed and a bare bones windows 10 pro/Norton internet/Windows Office.. and am working through all the application installs and set up...  I expect it will take another week to be up.. but it is straight forward process.... (but costly as I have had to repurchase some licences)

I reached the point after trying so many different fixes...  I no longer had confidence in the system... and even if the 1709 update had finished.. the system would have been suspect... so the clean Windows 10 option was the only way.

I say shame on Microsoft for putting many people through such an ordeal.....  I have lost way too much time to this problem.....

Andy