• Feature update to Windows 10, version 1607. Problems

From the error log, it looks like something had already gone wrong by 12:47:36, as it says

2017-02-17 12:47:36, Error [0x018007] CSI 00000028 (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]

What does the main setupact.log say from around that time? (Maybe just before as well.)

[CODE]2017-02-17 12:47:35, Info CSI 00000021 Calling generic command executable (sequence 6): 'C:\WINDOWS\System32\inetsrv\iissetup.exe' CmdLine: '"C:\WINDOWS\System32\inetsrv\iissetup.exe" /install SharedLibraries'2017-02-17 12:47:35, Info CSI 00000022 Performing 1 operations as follows: (0) LockComponentPath: flags: 0 comp: {l:16 b:1db116ec4589d2010a000000dc04e004} pathid: {l:16 b:1db116ec4589d2010b000000dc04e004} path: [l:115]'\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_10.0.14393.0_none_ 09e78f632173f4c5' pid: 4dc starttime: 1313182700539287612017-02-17 12:47:35, Info CSI 00000023 Creating NT transaction (seq 2), objectname '(null)'2017-02-17 12:47:35, Info CSI 00000024 Created NT transaction (seq 2) result 0x00000000, handle @0x7302017-02-17 12:47:35, Info CSI 00000025@2017/2/17:17:47:35.444 Beginning NT transaction commit...2017-02-17 12:47:36, Info CSI 00000026@2017/2/17:17:47:36.429 CSI perf trace:CSIPERF:TXCOMMIT;12108862017-02-17 12:47:36, Error CSI 00000027 (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]2017-02-17 12:47:36, Error [0x018007] CSI 00000028 (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]2017-02-17 12:47:36, Info CBS Failed to retrieve CBS log environment variable size for offline WER report. [HRESULT = 0x800700cb - ERROR_ENVVAR_NOT_FOUND]2017-02-17 12:47:36, Info CBS Not able to add CBS log files to Windows Error Report. [HRESULT = 0x800700cb - ERROR_ENVVAR_NOT_FOUND]2017-02-17 12:47:39, Info CSI 00000029@2017/2/17:17:47:39.804 CSI Advanced installer perf trace:CSIPERF:AIDONE;{81a34a10-4256-436a-89d6-794b97ca407c};Microsoft-Windows-IIS-SharedLibraries-GC, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35};7105700us2017-02-17 12:47:39, Info CSI 0000002a End executing advanced installer (sequence 40) Completion status: HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED) 2017-02-17 12:47:39, Info CSI 0000002b Begin executing advanced installer phase 38 index 2 (sequence 41) Old component: [l:0]'' New component: [l:164 ml:165]'Microsoft-Windows-ProcessModelLibraries-GC, Culture=neutral, Version=10.0.14393.0, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS' Install mode: install Smart installer: FALSE Installer ID: {81a34a10-4256-436a-89d6-794b97ca407c} Installer name: 'Generic Command'2017-02-17 12:47:39, Info CSI 0000002c Performing 1 operations as follows: (0) LockComponentPath: flags: 0 comp: {l:16 b:62dbbbee4589d2010d000000dc04e004} pathid: {l:16 b:62dbbbee4589d2010e000000dc04e004} path: [l:117]'\SystemRoot\WinSxS\amd64_microsoft-windows-p..ssmodellibraries-gc_31bf3856ad364e35_10.0.14393.0_none_ddc4cba1ddf61d91' pid: 4dc starttime: 1313182700539287612017-02-17 12:47:39, Info CSI 0000002d Calling generic command executable (sequence 7): 'C:\WINDOWS\System32\inetsrv\iissetup.exe' CmdLine: '"C:\WINDOWS\System32\inetsrv\iissetup.exe" /install ProcessModelLibraries'2017-02-17 12:47:39, Info CSI 0000002e Done with generic command 7; CreateProcess returned 0, CPAW returned S_OK Process exit code 0 resulted in success? TRUE Process output is throttled for successful Generic Commands2017-02-17 12:47:39, Info CSI 0000002f@2017/2/17:17:47:39.882 CSI Advanced installer perf trace:CSIPERF:AIDONE;{81a34a10-4256-436a-89d6-794b97ca407c};Microsoft-Windows-ProcessModelLibraries-GC, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35};101294us2017-02-17 12:47:39, Info CSI 00000030 End executing advanced installer (sequence 41) Completion status: S_OK 2017-02-17 12:47:39, Info CSI 00000031 Begin executing advanced installer phase 38 index 3 (sequence 42) Old component: [l:0]'' New component: [l:159 ml:160]'Microsoft-Windows-ProcessModel-Cpt-GC, Culture=neutral, Version=10.0.14393.0, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS' Install mode: install Smart installer: FALSE Installer ID: {81a34a10-4256-436a-89d6-794b97ca407c} Installer name: 'Generic Command'2017-02-17 12:47:39, Info CSI 00000032 Performing 1 operations as follows: (0) LockComponentPath: flags: 0 comp: {l:16 b:b364c5ee4589d2010f000000dc04e004} pathid: {l:16 b:b364c5ee4589d20110000000dc04e004} path: [l:114]'\SystemRoot\WinSxS\amd64_microsoft-windows-processmodel-cpt-gc_31bf3856ad364e35_10.0.14393.0_none_ce9dd1cee24d526a' pid: 4dc starttime: 1313182700539287612017-02-17 12:47:39, Info CSI 00000033 Calling generic command executable (sequence 8): 'C:\WINDOWS\System32\inetsrv\iissetup.exe' CmdLine: '"C:\WINDOWS\System32\inetsrv\iissetup.exe" /install ProcessModel'2017-02-17 12:47:39, Info CSI 00000034 Done with generic command 8; CreateProcess returned 0, CPAW returned S_OK Process exit code 0 resulted in success? TRUE Process output is throttled for successful Generic Commands2017-02-17 12:47:39, Info CSI 00000035@2017/2/17:17:47:39.945 CSI Advanced installer perf trace:CSIPERF:AIDONE;{81a34a10-4256-436a-89d6-794b97ca407c};Microsoft-Windows-ProcessModel-Cpt-GC, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35};70060us2017-02-17 12:47:39, Info CSI 00000036 End executing advanced installer (sequence 42) Completion status: S_OK[CODE]

Curiously I think it may be the same as that Windows 8.1 problem I found on the first page of the thread.

Me said:

This is about someone getting the same error (I assume) in Windows 8.1, but the first step of looking at setupact.log (and I guess setuperr.log) to see which component generates the error looks like a valid suggestion in this case:
https://blogs.msdn.microsoft.com/fri...-to-windows-8/

From that blog:

Towards the end of this log, I was able to find, towards the end of the log, information that the installer was trying to install IIS 8. Searching for system32\inetserv\iissetup.exe from the bottom of the file upwards should do the trick to help you find the line. If you inspect the log file around these lines, you will see the setup tries to perform several operations for the install of IIS, all of which fail, and then the installer decides to roll back the installation all together. Hence the ‘system component’ that could not be configured is IIS.

The next thing to try is to install IIS on the machine and see if this fails. And indeed after going through the IIS setup via the Windows Package Manager (Control Panel – Turn Windows Components on and off interface) I was able to see that IIS installation was indeed failing, even when I tried to install under Windows 7.

Basically, an IIS installation just asks CBS to deploy certain installation packages to the OS. The installer also keeps a detailed install log, which can be found here:
C:\Windows\IIS7.log

Contrary to the Windows 8 upgrade log, this log gets appended to, and will contain all installation and uninstallation attempts you perform in chronological order.
Looking through the log for the keyword <!!FAIL!!>, I was quickly able to spot information ...

And for your machine we have.

David49 said:

2017-02-17 12:47:35, Info CSI 00000021 Calling generic command executable (sequence 6): 'C:\WINDOWS\System32\inetsrv\iissetup.exe' CmdLine: '"C:\WINDOWS\System32\inetsrv\iissetup.exe" /install SharedLibraries'
2017-02-17 12:47:35, Info CSI 00000022 Performing 1 operations as follows: (0) LockComponentPath: flags: 0 comp: {l:16 b:1db116ec4589d2010a000000dc04e004} pathid: {l:16 b:1db116ec4589d2010b000000dc04e004} path: [l:115]'\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_10.0.14393.0_none_ 09e78f632173f4c5' pid: 4dc starttime: 131318270053928761
2017-02-17 12:47:35, Info CSI 00000023 Creating NT transaction (seq 2), objectname '(null)'
2017-02-17 12:47:35, Info CSI 00000024 Created NT transaction (seq 2) result 0x00000000, handle @0x730
2017-02-17 12:47:35, Info CSI 00000025@2017/2/17:17:47:35.444 Beginning NT transaction commit...
2017-02-17 12:47:36, Info CSI 00000026@2017/2/17:17:47:36.429 CSI perf trace:CSIPERF:TXCOMMIT;1210886
2017-02-17 12:47:36, Error CSI 00000027 (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]
2017-02-17 12:47:36, Error [0x018007] CSI 00000028 (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]

What I would do at this point is:

• Have a read of that blog post - it looks as if it could be relevant to your scenario.
• Make sure I had a good backup image of the system (especially the system drives) before proceeding further, just in case this doesn't work. (I would use the Free version of Macrium Reflect but other backup tools would do the job too).
• Try to switch on the Windows feature for Internet Information Services, and see if it works. If it doesn't work that might be a good thing as it may mean we've found the issue.
• If it doesn't work, have a look for a file with a name like C:\Windows\IIS.log and see what it says. You will probably need to copy it to another folder, and look at the copy.

Does this help? Not sure what I should do at this point.

David49 said:

Does this help? Not sure what I should do at this point.

Push OK. It should try to install the feature. (I'm assuming it wasn't already like that before you opened the option.) It may need a Restart afterwards. Then I think have a look for the C:\Windows\iis.log file.

David49 said:

My computer keeps telling me I have an update which requires a restart. It is listed as • Feature update to Windows 10, version 1607. (Is this what they are calling the "anniversary update"?) I don't know which build/version I currently have. The problem is, I have tried to let it update quite a few times, but it fails due to one or more components not able to be configured. This has been going on for many months now. Currently I have the "delay updates" checked so I do not have to let it try again. I keep hoping Microsoft would eventually have a fix for this, but so far I don't see one.

Any idea what I can to get the feature update to install?

my PC smooth update btw.. maybe your OS illegal

DavidY said:

Push OK. It should try to install the feature. (I'm assuming it wasn't already like that before you opened the option.) It may need a Restart afterwards. Then I think have a look for the C:\Windows\iis.log file. C:\Windows\iis text file denies me access to open this file.

How does this look?

David49 said:

How does this look?

I'd try switching it on/off and seeing what appears in that log file. Note you may need to Restart.

DavidY said:

I'd try switching it on/off and seeing what appears in that log file. Note you may need to Restart.

I try to open the iis .txt file and "Access is denied". Do you think I could try to run the update again?

David49 said:

I try to open the iis .txt file and "Access is denied".

Yes - you'll need to copy it to another folder and look at it there. You'll need to provide admin permission, but it should allow you to copy the file.

Me said:

• If it doesn't work, have a look for a file with a name like C:\Windows\IIS.log and see what it says. You will probably need to copy it to another folder, and look at the copy.