Windows 10 Cumulative Update KB4103721 Version 1803

Anonymous
2018-05-08T20:10:41+00:00

This update has some serious issues, specifically. Do NOT install this update after updating to Windows 10 version 1803. It will prevent your computer from booting up. I am stuck on the spinning circle for a long time. I have to use a Windows 10 USB to boot into the Troubleshooting and use Command Prompt to boot into safe mode. Please fix this update!

UPDATE: I have a tutorial on how to fix that:

https://www.youtube.com/watch?v=7Qiy4yxYHXc

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-05-11T20:33:05+00:00

I discovered that if you installed a program from Iobit (like Driver Booster, for example) it creates a service called "LiveUpdate" with full name, as I remember, "LiveUpdateSvc".

Even if you remove the program the service will remain and this cause the KB4103721 update to fail to boot Windows after the update.

Uninstall all Iobit programs and remove the service from the administrator command prompt typing "sc delete LiveUpdateSvc" (check it is the correct service name) and then you will be updating Windows without any problem.

I experienced this issue on two computers and this has been the solution.

Was this answer helpful?

70+ people found this answer helpful.
0 comments

331 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2018-05-09T05:56:47+00:00

    I'm runing:

    Asus Strix X370-F Gaming mobo.

    16GB Trident Z 3200 RAM.

    Ryzen 1700

    Evga 1080 video card. 

    Samsung 960 Evo m.2

    2tb Western Digital hdd. 

    My Intel i7 4770k machine has the same problem with the update as well. Even tried to install it manually to no avail.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-05-09T05:43:51+00:00

    You can also change to Manual and check when you want so it does not disturb what you are doing.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  3. Anonymous
    2018-05-09T05:40:24+00:00

    After using safe mode to force windows to discard the failed update and boot normally, I went in and disabled automatic updates. This prevents windows from trying to reinstall it again next power down cycle. On win10 you can do this by clicking start menu, Run and type services.msc. Then go down to Windows Update, open it and set value to disabled. You will have to reverse the process and set it back to automatic once this glitchy update gets fixed or replaced.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  4. Anonymous
    2018-05-09T04:12:34+00:00

    yes experiencing the same issues, there is a twitter hashtag going out as well. I also raised a SRX case but I can't get the twits at MS Support to understand this is not a Adm Policy block issue & that it is installing then failing. The support I have on this case is astounding, the level of total incompetence rivals what I have ever seen before. Usually by the time you create a SRX case you actually get "support". They cleared by System update history even though this update had been applied & was awaiting and then rebooted me into the " ether " again. Then never called me back.

      Now did anyone notice post build 1803 if the reg key " Microsoft\Windows\CurrentVersion\QualityCompat   "   is removed ?

     I think it may have been removed & I have Windows Defneder + a manual run of Malwarebytes & I am curious if that reg setting maybe got whacked in 1803 update and this kb is looking for it. A real guess I have no clue but clearly neither does MS.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments