Failure to install Windows 10 April Update(version 1803)

I see a title page there. But no substance or way to get to a blog from there;

I did finally get my system to update successfully. It took a mixture of time, persistence, diagnostic effort, and luck. I'll skip the red herrings and false starts and get right to what worked.

The essential information about my system is that it uses an ASUS X99-E motherboard with a RAID1 disk array (two mirrored drives).

1. I used the media creation tool to burn a DVD of Windows 10 1803.
2. I wiped my disk array clean.
3. I booted from the DVD and tried to install Windows onto my empty disk array.
4. When that failed, it was pretty clear that there was some fundamental conflict. Having previously stripped the system down to mouse, keyboard, and internal drives, there wasn't much left.
5. I deleted the RAID and left it as two separate drives.
6. I booted from the DVD and successfully installed Windows 10 1803 onto one of the two empty drives. That worked!
7. I rebuilt the disk array.
8. I booted from the DVD and successfully installed Windows 10 1803 onto the empty array. That worked!
9. That proved Windows 10 1803 is not fundamentally incompatible with my (Intel IRST) RAID controller chipset, but was for some reason incompatible with the array I'd started with.
10. I restored my working system onto the array that was now working with Windows 10 1803. That wiped out the update, of course, but I had a running system with all of my apps, files, and settings.
11. I ran the 1803 update again.
12. The update worked.
13. I now had a working 1803 installed on a RAID1 array.
14. I did have to fetch and install a new version of the IRST management software, but that was it.

I don't know how useful this is for you. I have no clue what was different about my disk array after I destroyed and rebuilt it. And I'm sure most of you don't have a similar setup. If you do, then give this a try.

Clearly, this entire update is sensitive in the extreme. I have another, much simpler, system that is also giving me fits. Nothing I described here will help with that. There must be something entirely different going on.

Strange. Well there is only one post at the moment so maybe this works

You have to realize one thing. I am total computer illiterate. I do not understand a whole lot on that page, just that that that provided error code never appears when the installation fails on my computer, which it always did then tried to start over. My computer must have rebooted more than 50 times with me being able to do nothing to stop it from trying again. I took 4 HP techs to finally decide it was never going to install itself on my desktop and I got the last HP tech (second level) to get my computer to even quit seeing the update. So that's why I am still mad a Microsoft. Putting in an update that does NOT work on all computers out there, and forcing me to let the Microsoft techs grab remote control of my computer 4 times before they decided it was NOT going to install itself.....EVER!

Should you have some other error (It's shown when old version starts for the first time after rolling back), then solution is not for you. I feel your pain, My computer was doing rebooting dozens of times too so I'm not too happy with MS either, and I'm afraid this problem may exist in the future updates as there seems to be no good channel to get that information to MS developers. "Windows 1803 fail" returns 5,9 million hits in google so there's obviously a **** of problems with MS updates at the moment and they should fix the update process instead of blaming drivers, external devices etc.