Share via

Windows 10 1809 update problem(Windows could not configure one or more system components. to install windows restart the computer with error code 0xc1900101-0x30018)

Anonymous
2018-10-11T06:51:19+00:00

When the update was downloaded and prepared , it called me to restart the computer to install 1809 update . However, until 52%, it said that "Windows could not configure one or more system components. to install windows restart the computer." After it restore the system, i check out the update record and find that the error code is 0xc1900101-0x30018. What should i do?

P.S. I have fix windows update errors by using the dism and system update readiness before.

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
  1. Anonymous
    2018-12-02T17:30:37+00:00

    Ischte - I could kiss you. Your suggestion worked for me!

    Rather than booting into Linux, I was able to rename the inetsrv folder to inetsrv.old in Windows by:

    1. Taking ownership of the folder
    2. Stopping the Application Host Helper Service

    I then took ownership of the WinSxS folder in order to move the *windows-iis*.* folders to a backup folder on another drive.

    With these out of the way, I then used the Windows 10 Update Assistant(rather than the ISO I had created), and updated successfully.

    When the updater reached 52% - where it would normally create the error message - it instead went back to 46% for a moment, then jumped back to 54% and continued progressing from there. I'm guessing this is where it needed to rebuild the files I had removed.

    Once the update was complete, I deleted the C:\Windows\System32\inetsrv.old folder.

    All is well, and I am successfully updated to 1809. Thanks again for your help!

    90+ people found this answer helpful.
    0 comments No comments
Answer accepted by question author
  1. Anonymous
    2018-12-02T11:50:06+00:00

    My solution:

    I also had the problem with updating Windows 10 1803 (last version) to 1809 and the standstill at 52%, then rebooting and restoring the old version. I noticed in the logfile which I analyzed the part with "iissetup.exe" in connection with the abort. shift+f10 for a console and possible repair with regedit during setup didn't work for me.

    Therefore I proceeded like this:

    In the software deinstallation (control panel) and with msicleaner (msicuu) i removed all old .net and visual studio parts. And then i reinstalled them with offline installer versions. there were still remains of old installations, but in the end they didn't solve the problem.

    Even with feature removal (control panel) and uncheck the box "internet information services" i couldn't get any further, because there were errors during deinstallation.

    ***

    The crunch point was the following:

    I booted with ubuntu linux and renamed the folder "c:\windows\system32\inetsrv" (which also contains the "iissetup.exe") e.g. to "inetsrv.old". Additionally, under "c:\windows\winsxs" I moved all folders with the name mask "*windows-iis*.*" to another location.

    Then i booted windows 10 again and restarted the update via the windows 10 update assistant.

    Now it ran error free through the installation and the files/folders under "inetsrv" and "winsxs" were rebuilt with the current version.

    ***

    Now my system is update correctly to the latest Windows 18 1809 build patch level. No further problems.

    Hope this help, Ischte

    70+ people found this answer helpful.
    0 comments No comments

51 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-12-02T17:59:25+00:00

    Great to see this solution worked for others too.

    yes, 52%, 46%, 54%... it was the same behavior here. 

    Funny what some beers and a saturday evening can do... it took me some nights to get the final hint with the "isssetup.exe". 

    Greetz Ischte

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-12-12T17:46:28+00:00

    The method I used for taking folder ownership is outlined here. The article is long and tedious, so I will save you some time - toward the bottom, they have one-click Registry files that will add "Take Ownership" to your right-click menu. I then simply right-clicked the WinSxS folder, and clicked Take Ownerhsip.

    There is another manual method described here.

    I moved all results with the *windows-iis*.* mask, though I do not remember if there were any items other than folders. I have not put them back in place after successfully upgrading, and have had no issues so far. However, I haven't deleted them from their archive location either. Yet.

    3 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-11-23T21:46:45+00:00

    Greg these are fantastic tips - thank you!

    I still find myself in the same boat as Lok32123; unable to update from 1803 to 1809, resulting in the same error above. Now that the update has been deemed safe to resume (except in a few cases), I'm hoping you will join me on a journey of troubleshooting.

    Caveat: while I could do a clean install to resolve the issue - I've used the Media Creation Tool to create a bootable USB with 1809 on it, just in case - I'd rather not go that route. Besides, I'm really curious to find the root cause here.

    My system:

    • Windows 10 Pro version 1803, build 17134.407.
    • All updates installed (even KB4467702) - Windows Update is squeezed dry for now.
    • Intel Core i7-8700K, 16GB RAM, 100+GB free space on the system drive (Intel SSD).
    • Discreet Nvidia graphics, wired ethernet connection, and a patridge in a pear tree.
    • No third party firewall, malware, or virus scanning software installed

    My Method:

    Since I have not been "pushed" 1809 via Windows Update, I went to get it myself from the update assistant at:

    https://www.microsoft.com/en-us/software-download/windows10

    I used the "Update Now" button, which gets you a copy of Windows10Upgrade9252.exe to download and install.

    After rebooting, this update proceeded to 52% before resulting in this screen, followed by a full rollback:

    At 52%, "Windows could not configure one or more system components. To install Windows, restart the computer and then restart the installation."

    Clicking "OK" results in a reboot and full rollback. No error code is presented once the rollback is complete, so I didn't have much to go on here.

    Before a second attempt, I did the following:

    • SFC /Scannow (in admin command prompt) - clean bill of health.
    • DISM /Online /Cleanup-image /RestoreHealth (in admin command prompt) - no issues found.
    • Ran Windows Update Troubleshooter - no evidence of corruption.
    • Disabled all non-Microsoft startup services and programs (aka clean boot).
    • Downloaded the Media Creation Tool for Windows 10 v1809.

    This time I ran the update through the Media Creation Tool (using the "Update Now" option rather than creating media). Same failed result - 52%, could not configure one or more system components, full rollback. However, this time I got an error message from the utility after the rollback:

    Error 0xC1900101 - 0x30018. "The installation failed in the FIRST_BOOT phase with an error during SYSPREP operation."

    This time I did some digging:

    • Device Manager - no drivers experiencing issues.
    • Right-Click -> Update on several drivers including network and display adapters, just to be sure.
    • Unplugged all external devices except keyboard, mouse, and a single monitor.
    • Uninstalled several unnecessary programs.
    • Discovered the C:$Windows.~BT\Sources\Panther and C:$Windows.~BT\Sources\Rollback folders, and the setupact.log files there.

    Here is an edited excerpt from my setupact.log file that would seem to be relevant to the update failure:

    2018-11-20 22:43:52, Info                  CSI    00000015 Begin executing advanced installer phase 38 index 1 (sequence 40)

        Old component: [l:0]''

        New component: [l:162 ml:163]'Microsoft-Windows-IIS-SharedLibraries-GC, Culture=neutral, Version=10.0.17763.1, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS'

        Install mode: install

        Smart installer: false

        Installer ID: {81a34a10-4256-436a-89d6-794b97ca407c}

        Installer name: 'Generic Command'

    2018-11-20 22:43:52, Info                  CSI    00000016 Performing 1 operations as follows:

      (0)  LockComponentPath: flags: 0 comp: {l:16 b:2035f6906581d401070000002c047c04} pathid: {l:16 b:2035f6906581d401080000002c047c04} path: [l:117]'\SystemRoot\WinSxS\amd64_microsoft-windows-iis-sharedlibraries-gc_31bf3856ad364e35_10.0.17763.1_none_3e1953fa9e8e8ea5' pid: 42c starttime: 131872557117969207

    2018-11-20 22:43:52, Info                  CSI    00000017 Calling generic command executable (sequence 1): 'C:\WINDOWS\System32\inetsrv\iissetup.exe'

        CmdLine: '"C:\WINDOWS\System32\inetsrv\iissetup.exe" /launch C:\WINDOWS\System32\inetsrv\appcmd.exe reset config -section:system.applicationHost/applicationPools'

    2018-11-20 22:43:52, Info                  CSI    00000018 Performing 1 operations as follows:

      (0)  LockComponentPath: flags: 0 comp: {l:16 b:20e606916581d401090000002c047c04} pathid: {l:16 b:20e606916581d4010a0000002c047c04} path: [l:115]'\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_10.0.17763.1_none_cd390dcd62eabc5a' pid: 42c starttime: 131872557117969207

    .

    .

    2018-11-20 22:43:52, Error CSI    00000021 (F) Done with generic command 1; CreateProcess returned 0, CPAW returned S_OK

        Process exit code 13 resulted in success? false

        Process output: [l:22 [22'[gle=0x80004005]

    .

    .

        CmdLine: '"C:\WINDOWS\System32\inetsrv\iissetup.exe" /launch C:\WINDOWS\System32\inetsrv\appcmd.exe reset config -section:system.applicationHost/listenerAdapters'

    .

    .

    2018-11-20 22:43:52, Error CSI    0000002b (F) Done with generic command 2; CreateProcess returned 0, CPAW returned S_OK

        Process exit code 13 resulted in success? false

    Process output: [l:22 [22'[gle=0x80004005]

    .

    .

        CmdLine: '"C:\WINDOWS\System32\inetsrv\iissetup.exe" /launch C:\WINDOWS\System32\inetsrv\appcmd.exe reset config -section:system.applicationHost/listenerAdapters'

    .

    .

    2018-11-20 22:43:52, Error CSI    00000035 (F) Done with generic command 3; CreateProcess returned 0, CPAW returned S_OK

    Process exit code 13 resulted in success? false

    Process output: [l:22 [22'[gle=0x80004005]

    .

    .

        CmdLine: '"C:\WINDOWS\System32\inetsrv\iissetup.exe" /launch C:\WINDOWS\System32\inetsrv\appcmd.exe reset config -section:system.applicationHost/sites'

    .

    .

    2018-11-20 22:43:52, Error CSI    0000003f (F) Done with generic command 4; CreateProcess returned 0, CPAW returned S_OK

    Process exit code 13 resulted in success? false

    Process output: [l:22 [22'[gle=0x80004005]

    .

    .

        CmdLine: '"C:\WINDOWS\System32\inetsrv\iissetup.exe" /launch C:\WINDOWS\System32\inetsrv\appcmd.exe reset config -section:system.applicationHost/webLimits'

    .

    .

    2018-11-20 22:43:52, Error CSI    00000049 (F) Done with generic command 5; CreateProcess returned 0, CPAW returned S_OK

    Process exit code 13 resulted in success? false

    Process output: [l:22 [22'[gle=0x80004005]

    .

    .

        CmdLine: '"C:\WINDOWS\System32\inetsrv\iissetup.exe" /install SharedLibraries'

    .

    .

    2018-11-20 22:43:53, Error CSI    00000053 (F) Done with generic command 6; CreateProcess returned 0, CPAW returned S_OK

    Process exit code 13 resulted in success? false

    Process output: [l:22 [22'[gle=0x80004005]

    2018-11-20 22:43:53, Error [0x018007] CSI    00000054 (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]

    2018-11-20 22:43:53, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]

    2018-11-20 22:43:53, Info                  CBS    Could not get file name for current session file logging [HRESULT = 0x80004003 - E_POINTER]

    2018-11-20 22:43:53, Info                  CBS    Failed to retrieve CBS log environment variable size for offline WER report. [HRESULT = 0x800700cb - ERROR_ENVVAR_NOT_FOUND]

    2018-11-20 22:43:53, Info                  CBS    Not able to add CBS log files to Windows Error Report. [HRESULT = 0x800700cb - ERROR_ENVVAR_NOT_FOUND]

    2018-11-20 22:43:53, Info                  CSI    00000055@2018/11/21:06:43:53.150 CSI Advanced installer perf trace:

    CSIPERF:AIDONE;{81a34a10-4256-436a-89d6-794b97ca407c};Microsoft-Windows-IIS-SharedLibraries-GC, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35};725233us

    2018-11-20 22:43:53, Info                  CSI    00000056 End executing advanced installer (sequence 40)

        Completion status: HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED)

    Several commands involved "iissetup.exe" failed, but the line "iissetup.exe /install SharedLibraries" resulted in the message "Failure will not be ignored: A rollback will be initiated (etc.)" A further 7 lines in the log resulted in "Failure will not be ignored," all involving iissetup.exe with various different parameters specified.

    Finally, I created a bootable USB stick from the Media Creation Tool for Windows 10 v1809, disconnected the network cable, rebooted, and tried to upgrade directly from the media.

    Same exact result (full rollback to 1803), same exact errors in setupact.log.

    I did another clean boot, opened an elevated PowerShell, and directly ran some of the iissetup.exe commands (even though they are not meant to be called directly by a user), just to see if it would give me any more error information. All of them failed with code 0x8007000d, with one exception:

    "iissetup.exe /install SharedLibraries" returned 0x8009000f.

    This is where I ran into a dead end. The only reference I could find to this error was in a 10 year old threadspecific to IIS reinstallation and machine encryption keys. I tried following the recommended procedures there and re-running the update, but to no avail.

    I have a programming background, so I'm trying to "step through" the problem, but I can't seem to find any answers to what would cause the "un-ignorable" 0x8009000f. Any leads would be greatly appreciated!

    3 people found this answer helpful.
    0 comments No comments