Windows 10: Windows 10 Feature update 1709 keeps failing to install

Two things I have notice. System Reserve still might be dynamic. I can't tell by the last picture in post #12

With that systems hardware, I would think UEFI would be used instead of MBR.

Take a read here. A Tutorial by Brink.

Convert MBR Disk to GPT Disk in Windows 10 Hardware Drivers Tutorials

Your choice.

Posting another of Windows 10 complete Disk Management picture would helpful.

This tutorial by gregrocker will guide you.

Disk Management - How to Post a Screenshot of General Tips Tutorials

Jack

 

I used the show non present devices trick and deleted anything no longer on the computer. When it asked about removing drivers I indicated yes.

 

I'm already doing the update. If it fails again I'll make sure to update. I do know all partitons are basic at this point. I didn't see the option of converting to GPT. I'll look at that as well.

 

There were/are additional troubleshooting steps to make for upgrade failure.
How come you are eager to upgrade now and not wait for the new drive......14 days?
What was done with the gigabyte driver?
The LG drivers were the main problems found.
Hope it works.
If it does not be sure to look for an error message and error codes.

 

Well, it didn't work. Same generic error message at the end but the log files show it's having trouble with a WinPE file.
I've converted the boot drive to GPT from MBR.





The zip file attached contains the Panther and Rollback setup*.log files as well as a diagerr.xml file from the rollback directory.

 

Well, nothing seems to have helped much. I just finishing scanning the setupact.log file for clues and found this section:
Info CSI 00000021 Calling generic command executable (sequence 6): 'C:\WINDOWS\System32\inetsrv\iissetup.exe'
CmdLine: '"C:\WINDOWS\System32\inetsrv\iissetup.exe" /install SharedLibraries'
Error CSI 0000002b (F) Done with generic command 6; CreateProcess returned 0, CPAW returned S_OK
Process exit code 9 resulted in success? false
Process output: [l:22 [22'[gle=0x80004005]
Error [0x018007] CSI 0000002c (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]
Completion status: HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED)

So, it looks like it is trying to do something with IIS. I've found others with similar issues with IIS. I've un-installed and re-installed IIS to no avail. Finally I found this IIS install fails after the Windows 10 November update : The Official Microsoft IIS Forums where the user descibes a broadcom driver interfering with IIS. But, this can't be my issued because I never installed a broadcom driver (I wouldn't know what it was for). But I checked and it was there...
I've removed the driver and will have to try the update again to see how it goes. I will update after my next try.

 

1) Download and install Everything
voidtools
2) Look for the 4 problematic drivers
Were they uninstalled?
Were they uninstalled and reinstalled?
3) Turn off Windows updates of non-Microsoft drivers
Enable or Disable Driver Updates in Windows Update in Windows 10 Windows Update Activation Tutorials
And/or completely disconnect from the internet: mechanical off wireless, disconnect ethernet or cat5e cable
4) Unistall the 4 drivers again
5) Place the computer in clean boot:
https://support.microsoft.com/en-us/...oot-in-windows


How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki

6) Uninstall all AV products/firewall software (always on and manual) and use only windows defender
7) Attempt upgrade with Windows 10 iso

 

The solution provided in IIS install fails after the Windows 10 November update : The Official Microsoft IIS Forums worked to resolve the issue for my computer.

Some how a broadcom driver was installed onto my computer. Perhaps when it was a previous version of windows - I don't know where it came from or why it was installed. But the driver adds a couple of keys into the cryptographic providers in the registry and that is what ultimately crippled the upgrade on my computer. I removed the two keys and the dll from my computer and tried the upgrade.

It worked. I'm upgraded.

 

What was the driver?
Did you find it in the logs?

 

That rings a bell. The rollout of 1703 had to be delayed on some machines with particular Broadcom hardware until Microsoft developed a fix....

Windows 10 Creators Update rollout: First phase update

 

No I did not. I found by examining the registry entry posted in IIS install fails after the Windows 10 November update : The Official Microsoft IIS Forums I really didn't expect to find it there. No idea where it came from.