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-11T16:28:14+00:00

    Current Windows 10 Pro OS v 1803 build is 17134.48

    I don't know the original build that was installed earlier this month.

      Yeah 17134.1 was 1803 straight up, this has that update in it which may have gotten embedded when you re-did it back up.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-05-11T16:35:04+00:00

    I'm calling it good for now and not changing anything else until the dust settles on these issues.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-05-11T16:51:44+00:00

    Hello Poomba_1,

    I don't believe I understood your reply, as you also did not specifiy in which part of my conclusion you disagree.

    Let me again try to clarify :

    In 16299.xxxx (Windows 10 1709) every next boot after having done an AMD driver update or having run "CCleaner" was fine.

    Starting with 17134.1 (Windows 10 1803), every next boot after having done an AMD driver update or having run "CCleaner", and now after

    attempting to install KB4103721, was resulting in a "black screen" (before logon) and the only way to solve/bypass was to boot to "safe mode" (necessary once after having done the AMD driver update or having run "CCleaner", necessary twice after KB4103721, which furtheron was leading to a rollback of KB4103721).

    For MY particular situation I was able to find out, that disabling the "Syncovery VSS helper service" allowed any further boot (after above mentioned "maintenance tasks") to complete without any issue (as in 16299.xxxx).

    So again, KB4103721 (the update from 17134.x to 17134.48) is NOT causing the problem, but at the end of the day suffering from an issue already introduced with 17134.1 (Windows 10 1803 final).

    Of course I did never state, that every Windows 10 user will run in that problem, as obviously not every Windows 10 user is using "IoBit Advanced System Care" or "Syncovery" (known at the moment to cause the "black screen" situation) ... it is now up to Microsoft to find out, why those (or maybe other) products are causing (kind-of) compatibility issues in the Windows 1803 boot process.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-05-11T17:03:13+00:00

    It does not help people solve the problems. I agree with you! But it may motivate the world company "MICROSOFT" in the future to work more carefully, the Windows users are not facing almost unsolvable problems. Microsoft should rather offer solutions and not rely on the few capable people in a community.

    A public apology would be appropriate!

    But then Microsoft would have to admit yes mistakes and that is definitely not!

    Frank

    Was this answer helpful?

    0 comments