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-07-09T15:02:19+00:00

    I too would like to think you Ischte. I followed the approach used by Discrepancy.

    In my case I'd had windows update fail a couple of times and DsmSvc (Device Setup Manager) was left in an agitated state where it would fire up and start using 55% cpu. Killing the process and disabling the service would work for about 5 minutes. Then the service would get reset to manual, startetd, and back to DsmSvc 55% cpu.

    After the *windows-iis*.* fix, the windows 10 update assistant worked.

    Now, onto a full backup and seeing what surprises await in my "more secure environment."

    Many thanks to you both.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-08-11T08:58:07+00:00

    This worked for me too, although I must say, I spent a great deal of time previously trying various other options and those hours and hours gone to waste simply got on my nerves. This one took like three hours to complete. Never before has it been so difficult to run a Windows update, I never had to spend so much time reading on forums, trying stuff out, playing with the command prompt, tampering folders from C etc. What''s going on???

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-08-13T01:47:10+00:00

    This solution given by Ischte works on the latest update 1903 as of August 12, 2019

    Would think Microsoft would have fixed the problem by now.  Spent better than twenty hours doing ten different attempts using different tools built-in Windows.  Did each separately to see if it would be the one which solved the problem.  Did not think they would since each reported no errors found

    Thanks Ischte

    Was this answer helpful?

    0 comments