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 No 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 No comments

331 additional answers

Sort by: Oldest
  1. Anonymous
    2018-05-11T11:35:55+00:00

    Dear all,

    after having spent several hours I was able to find the root cause (for MY installation(s) !), the solution, no logical explanation, and some additional, but important, conclusion :

    The observed behaviour (black screen, only been able to be resolved by booting to "safe mode") does not seem to be caused specifically by the recent Windows 10 update KB4103721 ... it seems to be a general "incompatibility" problem (during a reboot following some "service") of 1803.

    Let me explain:

    • I also had to observe the "black screen" after having attempted to install KB4103721. Only solution was to boot in "safe mode" twice leading to the rollback of the failed installation
    • Interestingly, I then had to observe the identical bad behaviour after installing the recent AMD drivers 18.4.1 ... "black screen" after the next reboot, only solved by booting into "safe mode" (once)
    • And further on, after I decided to run a check/clean with CCleaner, again the same symptom ... "black screen" after the next reboot, only solved by booting into "safe mode" (once).
    • I decided to follow the recent suggestions and, with "msconfig" I disabled all "non-Microsoft" services ... and ALL above mentioned situations were able to start fine with the next reboot.
    • Enabling all those services again was leading again to the "black screen" situation.
    • I then step by step was disabling service by service and after all, in my case, I was able to identify "SyncoveryVSSService" to be the root cause for ALL above mentioned "black screen" situations.
    • "SyncoveryVSSService" is part of "Syncovery", which is obviously aimed to allow to copy locked files (which is selected by default to be installed)

    As your situation very likely will differ from mine (as you likely will not have installed "Syncovery" at all), the most important part is, that the problem seemingly is not caused specifically by the mentioned update KB4103721, but seems to be a general 1803 compatibility issue.

    As already stated several times, if you are not able to identify the root cause (which is very time-consuming), the best and easiest solution for the moment to bypass this problem is to run "msconfig", and deselect every "non-Microsoft" service for the next reboot following some "system change" (Windows 10 update, driver update, or as in my case CCleaner), and enabling those again afterwards.

    I personally decided to not allow such an disaster again, and installed "WUMT", which not only blocks automatic updates but gives you (similar to Windows 7) again the ability to selectively install or to hide specific updates

    (see http://forums.mydigitallife.info/threads/64939-Windows-Update-MiniTool)

    Good luck !

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-05-11T12:21:53+00:00

    I uninstalled Advanced System Care, rebooted, installed the update no problem, re-installed ASC. Sorted. There may be more subtle ways (disable asc services then reboot?) but it worked for me

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-05-11T12:30:50+00:00

    I'm still trying.

    Frank

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-05-11T12:32:56+00:00

    Is it possible, that the service LiveUpdate from IOBit is the reason? I´m not using ASC but sometimes used the Uninstaller from IOBit. I´ve uninstalled it, but the service is still running.

    Was this answer helpful?

    0 comments No comments