![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I finally resolved this issue on my laptop. I believe that update 4103727 simply broke the upgrade process. My laptop was stuck in a perpetual upgrade fail, reboot cycle. Worse, it was very aggressive in rebooting my machine. This is a disaster for me, as the laptop is my main development platform. I need to be able to leave it on for a week or more, maybe I'm in the middle of coding something over the weekend.
Anyway, I tried deleting the download folder, no joy. After reading many articles about the issues, I decided to just skip the last two updates and go straight to the latest. Came across this link with a number of suggestions: https://www.wintips.org/fix-windows-10-update-1803-fails-to-install/.
I elected to try fixing the Windows Update facility then force the download of the 1803 package. Ran the Windows Update Troubleshooter (you need admin rights), and it corrected a number of issues. Link Windows Update Troubleshooter
Next, I elected to go with Method 2, Download and Install the Windows 10 April 2018 v1803 Update manually.
The process went right through, installed and I am no longer am at the mercy of the previously botched update.
NOTE: Folks, I really don't trust Microsoft to protect your system. Before you do any of this, please create a System Restore point manually. Name it something special like "Safe Sex with Microsoft" or something. This will give you a known retreat path if something terribly goes wrong. I would also recommend getting a decent sized USB drive and create a Windows Installation Media USB drive. See: https://www.microsoft.com/en-us/software-download/windows10
Should things get very ugly, you can boot from the USB drive and select your system restore point you created earlier. This has saved my butt a number of times after Microsoft "helped me."
Hope this helps someone...
Oh one other comment - my machine is a core i7 2.8 GHz, 32GB ram, all solid state drives. Even so, the process took a little over 2 hours. Plan accordingly.
And one more: one thing that Microsoft decided to do is at drivers to their update list. This can be fatal for laptop users, as laptop drivers really, really need to come from the OEM of the laptop, not the latest drivers from device manufacturers. I had many BSODs until I realized what was happening (another wtf Microsoft moment). Now, its up to you to decide if you want to allow Microsoft to update the drivers, but be aware that when you install major updates like 1803, inexplicably Microsoft resets this setting to update. Simply stuck on stupid if you ask me.