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
Answer accepted by question author
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!

Was this answer helpful?

90+ people found this answer helpful.
0 comments
Answer accepted by question author
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

Was this answer helpful?

70+ people found this answer helpful.
0 comments

51 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2019-03-30T00:47:24+00:00

    Thanks to Ischte, Discrepancy, and others who have pioneered, streamlined, and documented this fix.

    The fix worked for me.  I just stopped the service and renamed inetsrv to inetsrv.old in an administrative command prompt, then Windows Update worked successfully next time, passing the same milestones detailed by JoeTS.

    I will contribute my small bit by documenting further the problem that this fix fixes.

    What is the problem that this fix fixes?

    During Windows Update to version 1809, while showing "Working on updates 52%" on a blue background, a popup shows error message "Windows Setup"  "Windows could not configure one or more system components.  To install Windows, restart the computer and then restart the installation"  

    After a restart, Windows Update | View update historywill show an error code of 0xC1900101 for the failed update.  Retrying as suggested will eventually fail again the same way.

    Restarting after this failure, the file C:$WINDOWS.~BT\Sources\Panther\setuperr.log will contain, near its end, a summary something like 

    the following.  To read this, you need administrative privilege.  If you want to see this, and if your account has admin privilege, you can:

    • Click the Windows "Start" button in lower left of screen
    • Type Notepad
    • Right-click on Notepad and "Run as administrator"
    • Open the filename above.

    2019-03-28 18:53:04, Info                  CSI    000001cd The queue has completed running, and AI failures have occured.

    2019-03-28 18:53:04, Info                  CSI    000001ce ==Error Summary Start==

    2019-03-28 18:53:04, Error                 CSI    000001cf (F) Installer: ServiceModelReg Installer Binary Name: servicemodelregai.dll ErrorCode: 8007000d Phase: 39 Mode: Delta Component: NONE[gle=0x80004005]

    2019-03-28 18:53:04, Error                 CSI    000001d0 (F) Generic Command ErrorCode: 80004005 Executable: iissetup.exe ExitCode: 13 Phase: 38 Mode: Install (first install) Component: Microsoft-Windows-IIS-W3SVC-GC, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS[gle=0x80004005]

    2019-03-28 18:53:04, Error                 CSI    000001d1 (F) Generic Command ErrorCode: 80004005 Executable: iissetup.exe ExitCode: 13 Phase: 38 Mode: Install (first install) Component: Microsoft-Windows-IIS-HttpCache, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS[gle=0x80004005]

    2019-03-28 18:53:04, Error                 CSI    000001d2 (F) Generic Command ErrorCode: 80004005 Executable: iissetup.exe ExitCode: 13 Phase: 38 Mode: Install (first install) Component: Microsoft-Windows-IIS-CachingBase, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS[gle=0x80004005]

    2019-03-28 18:53:04, Error                 CSI    000001d3 (F) Generic Command ErrorCode: 80004005 Executable: iissetup.exe ExitCode: 13 Phase: 38 Mode: Install (first install) Component: Microsoft-Windows-IIS-HttpProtocol, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS[gle=0x80004005]

    2019-03-28 18:53:04, Error                 CSI    000001d4 (F) Generic Command ErrorCode: 80004005 Executable: iissetup.exe ExitCode: 13 Phase: 38 Mode: Install (first install) Component: Microsoft-Windows-IIS-RequestFiltering, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS[gle=0x80004005]

    2019-03-28 18:53:04, Error                 CSI    000001d5 (F) Generic Command ErrorCode: 80004005 Executable: iissetup.exe ExitCode: 13 Phase: 38 Mode: Install (first install) Component: Microsoft-Windows-IIS-AnonymousAuthentication, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS[gle=0x80004005]

    2019-03-28 18:53:04, Error                 CSI    000001d6 (F) Generic Command ErrorCode: 80004005 Executable: iissetup.exe ExitCode: 13 Phase: 38 Mode: Install (first install) Component: Microsoft-Windows-IIS-SharedLibraries-GC, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS[gle=0x80004005]

    2019-03-28 18:53:04, Error                 CSI    000001d7 (F) Generic Command ErrorCode: 80004005 Executable: iissetup.exe ExitCode: 13 Phase: 38 Mode: Install (first install) Component: Microsoft-Windows-IIS-NetFxExtensibilityCommon-GC, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS[gle=0x80004005]

    2019-03-28 18:53:04, Info                  CSI    000001d8 ==Error Summary End==

    2019-03-28 18:53:04, Error                 CSI    000001d9@2019/3/28:22:53:04.712 (F) onecore\base\wcp\componentstore\com\advancedinstallerstore.cpp(580): Error HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED) originated in function Windows::COM::CComponentStore::IAdvancedInstallerAwareStore_ResolvePendingTransactions expression: HRESULT_FROM_WIN32(14099L)

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2019-04-02T16:19:11+00:00

    Thx for ischte and discrepancy，this problem continues from winter to summer, now new 19h1 is coming. finnally i upgrade to 1809

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-04-24T17:32:30+00:00

    Hi,

    I didn't understand about Windows iis folders. Can I move these folders in an other folder? Or do I have to remove them definitely? Thanks

    Was this answer helpful?

    0 comments