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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-05-12T08:20:09+00:00

    I´m playing around with this Update since 4 Days. First it started with a black Screen. Cant go back. So I made a clean install which causes Network Disfunction. Now I´m through. This morning I have an Update: 

    Windows 10 Cumulative Update KB4103721 Version 1803

    Again, and again, and again, and again…

    There is a way to pause the update for at least 35 days in the Security and Update section. Hopefully Microsoft will pull this update by then.

    I believe you can also go back to a previous build.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-05-12T08:21:32+00:00

    Yeah, that´s what I did already

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-05-12T08:23:00+00:00

    If You know anything about root cause analysis, You would know that its enough with ONE having the problem without having any Iobit products, to disqualify it as the root cause.

    Add the fact that the problem didnt show up after a change in ASC but after two updates from MS.

    Again Iobit might or might not contribute (among other products) to the effect of the problem, but never being the root cause.

    You could take my word for it. I have been a root cause analyst in the industry for the past 25 years.

    I understand your point of view.

    What I can say is that I updated succesfully many clients experiencing the problem only with clients having Iobits software and "LiveUpdateSvc" service.

    I also made an image of the disc of one pc experiencing this problem and after trying many solutions the only working was to remove Iobit software and service. Everytime I started from the original disc image and trying a different solution. After removing Iobit software and LiveUpdateSvc service (doing nothing else) everything updated fine.

    In any case, you may try to install an older Windows 10 version, install Iobit software and LiveUpdateSvc service and then try to update.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-05-12T08:23:32+00:00

    Not true either - I now know at least three of my friends using Iobit ASC and Win10 that did NOT experience this problem when being pushed to update with the "bug fix" from MS last tuesday.

    So not all Win10 users have the problem, but the problem is common enough.

    The only thing that ALL users with the problem has in common, is that they use Win10 and it presented itself  when installing that Win10 "bux fix". Some Win10 users did not have the problem when updating, so the update by it self is not enough to make it emerge.

    The april edition + the bug fix + something more (still unknown) is the most proable cause. You can bank on it.

    Was this answer helpful?

    0 comments