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
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 No 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 No comments

51 additional answers

Sort by: Newest
  1. Anonymous
    2019-01-05T20:37:57+00:00

    I would also like to thank Ischte and the follow on reply. I also had the fallback at the 52% mark using the Windows 10

    Update assistant. In my case, renaming the inetserv folder to inetserv.old was enough for success; I did not need to

    deal with the WinSxs folder. Also, I had other machines at 1809 so I could do a before and after look at both the 1803 and

    1809 file versions. I also fell back from 52% to 46% as noted here, but then went to 47,50,etc back to 52 then on from

    there with long stops at certain points, notably 75% (with a restart here) and 84%. 

    For me, this update first failed in windows update with a 0xC1900101 code. Then, windows update tried again and showed

    the upgrade was successful and awaiting a restart in the features tab of view update history. Alas, no restarts made any

    difference and the machine was still at 1803 which continued to update. Then I turned to Windows 10 Update Assistant

    and followed the pathway noted above.   Thanks again for the posted info which allowed this to work..

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2019-01-04T10:10:13+00:00

    Hi Discrepancy.

    Thank you for getting back to me. I used the solution posted by blueadept1, a few days ago(booted into "Safe Mode") and finally got the update to install. I now have two****inetsrv folders in Windows: "inetsrv" and "inetsrv.old"...but everything appears to functioning correctly. Not sure if I should remove the "old" or leave it? Also should I remove the 'take ownership' application?

    Regards

    Stu

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-01-04T04:25:29+00:00

    The Application Host Helper Service is in the services control panel (type services.msc into a Run dialogue box). Alternatively, go to Task Manager -> Servicestab and look for AppHostSvc. Stop the service when you find it - the fact that it is still running is probably what is causing your inetsrv folder to show an item "in use."

    Hope that helps!

    Was this answer helpful?

    0 comments No comments