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
{count} votes
Answer accepted by question author
  1. 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.

    79 people found this answer helpful.
    0 comments No comments

331 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-05-09T03:20:17+00:00

    I have the same problem on two PCs! --->an HP HPE 190t Desktop W10 Pro, version 1803, 64-bit and an HP Envy dv7 Notebook/Laptop W10 Pro, version 1803, 64-bit. I had trouble installing version 1803 on the Laptop- had to go back to reinstall version 1709 to do an eventual successful update to version 1803, which finally worked. But updates KB4103721 along with KB890830 put both PCs into a permanent black screen reboot loop with the circling white dots!

    Using the F11 key while rebooting the Laptop 3 times allowed me to get into the sub-menu to restore the Laptop back to the previous W10 version 1709, and then delay automatically installing updates on it until June 12, 2018. But, no luck in using the same process to revert the Desktop back to version 1709. In the meantime, the Desktop shows nothing but infinitely circling white dots upon rebooting. I may have to PAY a professional IT/IS person to fix this problem. Thanks for the screw up MS!

    13 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-05-09T03:27:36+00:00

    Trying to fix a system for someone that is constantly installing the 1803 update to 59% then going back to 0% repeat in a stuck loop :(

    They seriously need to STOP this forced update crap especially with such low quality of updates coming out with so many problems.

    It is way past a sad joke now that they've not put back proper manual control over updates - someone at MS has to be doing it just to be obnoxious there is no way they'd leave it like this if they cared about the consumer experience a single bit.

    20 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-05-09T03:51:00+00:00

    Yup same issue here. Update won't fully install and prevents windows from booting. Have to go into safe mode to fix it.

    10 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-05-09T04:12:34+00:00

    yes experiencing the same issues, there is a twitter hashtag going out as well. I also raised a SRX case but I can't get the twits at MS Support to understand this is not a Adm Policy block issue & that it is installing then failing. The support I have on this case is astounding, the level of total incompetence rivals what I have ever seen before. Usually by the time you create a SRX case you actually get "support". They cleared by System update history even though this update had been applied & was awaiting and then rebooted me into the " ether " again. Then never called me back.

      Now did anyone notice post build 1803 if the reg key " Microsoft\Windows\CurrentVersion\QualityCompat   "   is removed ?

     I think it may have been removed & I have Windows Defneder + a manual run of Malwarebytes & I am curious if that reg setting maybe got whacked in 1803 update and this kb is looking for it. A real guess I have no clue but clearly neither does MS.

    2 people found this answer helpful.
    0 comments No comments