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-11T16:13:53+00:00

    I do not have an IoBit on my laptop !!! Should we now only install programs from Microsoft? The price development can then anyone imagine (see Office)! You can not solve problems if you simply negate them and shift responsibility to others.

    Frank

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-05-11T16:09:15+00:00

    I disagree with that statement. I'm seeing PC's that are now getting offered the update & not being offered the KB patch but upon completion their ver/winver is 17134.48 so as many PC's do work with the patch some are getting upgraded straight to it (download updates). The unusual thing is first couple updates post patch Tuesday this wasn't being offered it seemed you needed to go to build 1803 then update to this now it is embedded so it may be those experiencing issues now with going to 1803 perhaps have this embedded update in the upgrade process.

     Let's not forget one critical point, this 1803 was PULLED in early April due to issues, then rolled out later, now we have this. I would suggest that this has been sub par all around.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-05-11T16:08:36+00:00

    Totally bricked One PC with every recovery menu option failed. Got home from work and my laptop was BSOD. Afraid to turn on my 2 PC's downstairs for the same mess.

    Cust svc got angry with me when I laughed at his explanation that my custom built PC was "incompatible" with W10. Told hime I had the most recent image for a clean install and after I got it up and running he could explain to me again how it was "incompatible" Well it's up and running just fine after a lot of inconvenience and more still left to repopulate.

    The laptop I'm on now just went through a system restore point and I'm trying to figure out what to do next before this update is forced on it again.

    This is unacceptable and customer service needs to stop lying to W10 users about their computers or manufacturers being the issue. Your update is bricking our machines. Own up and solve the problems you've created or at least do some more testing and make the update OPTIONAL if you know this might happen. It's a terrible business model to dig in your heels over this.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-05-11T15:54:35+00:00

    Hello R.Gold,

    as I already mentioned in my first summary and then also to Pascal (in my reply to him a few minutes ago), the problem very likely is there already in 17134.1 and not caused specifically by KB4103721.

    In regard to "Syncovery", fortunately the contained & installed VSS helper service (triggering the "black screen") is nothing someone really needs (as copying locked/open files very often leads to corrupt data anyway), so you should move on by either manually disabling this service (in "msconfig" or "autoruns") or deinstall & reinstall "Syncovery" (without selecting the VSS helper service).

    Was this answer helpful?

    0 comments