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-09T13:50:42+00:00

    What should we do now? I had to reinstall my Window 10 (repair, restore etc all didn't workd) and reinstall all my programs (650 GB!!!). Now Windows wants to install the same bad update again. What can I do? I do not dare to reboot my system!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-05-09T13:48:32+00:00

    Also the same problem on one machine (but not others). It fails at the second stage of the update process immediately after the reboot after something like the 30% progress mark.

    The two differences are that the one failing was on 17134.1 and all the others (which worked fine) on 17134.7, and that the one that fails has WMR installed (taken device out to make sure that was not the problem).

    This is a really really bad bug - had to go back to a backup as System Restore failed for me. Tried again and the same issue occurs (hoping that the System Restore that I manually did before it this time works, otherwise another 18 hours of restoring 1.5TB).

    At the very least you need to pull the update until this can be fixed.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-05-09T13:45:05+00:00

    Yes, I have the same problem too!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-05-09T13:23:04+00:00

    yes, I have the same problem....

    Was this answer helpful?

    0 comments