Windows 10 Feature Update 2004 taking too long to install

I'm still here...still not able to complete the update (now on attempt 27, maybe more). I successfully ported my physical system over to a virtual machine, removed all non-Microsoft tools and drivers that are no longer relevant in its virtual state and still, same failures in that environment. This confirms it's not hardware! My physical system still runs/operates without problems as does the identical virtual system. The only good news is the failure results are much quicker now in the virtual world. Still the same ole boring Update Failed (nothing but a dialog box indicating such), but now it only takes 45 minutes. I've reviewed the setuperr.log (among the many, many others), cleaning it out prior to every attempt, and still get nothing out of the process that provides even a hint of where the problem is or what caused the "failure".

Such a shame this product, as much as it sucks, isn't a vacuum (new business opportunity for Microsoft?).

On to attempt 28!

This may be a stupid question, but do you start the update from "Update & Security">Windows Update? I've done it from there, this one was from there, and I'll do my laptop from there too. I need to correct something I said earlier. I'm not sure what the "dated" update is you're trying to install, but my suggestion for the MCT route is only the May 2020 update. My update was released today to Insiders. Do you know the release date of the update you're trying to install?

Just finished the 20215.1000 update. It took 40 minutes, and that's the longest time it has taken. I tried to post that I was about to commence the update, but kept getting an Oops! message, Sheesh!!!

I'm still here...still not able to complete the update (now on attempt 27, maybe more). I successfully ported my physical system over to a virtual machine, removed all non-Microsoft tools and drivers that are no longer relevant in its virtual state and still, same failures in that environment. This confirms it's not hardware! My physical system still runs/operates without problems as does the identical virtual system. The only good news is the failure results are much quicker now in the virtual world. Still the same ole boring Update Failed (nothing but a dialog box indicating such), but now it only takes 45 minutes. I've reviewed the setuperr.log (among the many, many others), cleaning it out prior to every attempt, and still get nothing out of the process that provides even a hint of where the problem is or what caused the "failure".

Such a shame this product, as much as it sucks, isn't a vacuum (new business opportunity for Microsoft?).

On to attempt 28!

"The only good news is the failure results are much quicker now..., but now it only takes 45 minutes."

That is unbelievable!  And it makes is scary that in my beta environment, I may get caught up in a web of unexplainable craziness. I know that if it does, I'll just download the OS-Update from Media Creation Tool download, format my SSD and start over. That isn't a solution, that isn't a workaround. That's a a cop out perpetrated by the "gold standard" in the PC world that so many of us live in. That's tragic. It makes me wonder, "Why am I doing the "Insider" beta thing, if it doesn't help anybody?" It's crazy!!! When a failure result is "good news" because it only took 45 minutes to get there, something is gravely wrong with this picture.

I'm still here...still not able to complete the update (now on attempt 27, maybe more). I successfully ported my physical system over to a virtual machine, removed all non-Microsoft tools and drivers that are no longer relevant in its virtual state and still, same failures in that environment. This confirms it's not hardware! My physical system still runs/operates without problems as does the identical virtual system. The only good news is the failure results are much quicker now in the virtual world. Still the same ole boring Update Failed (nothing but a dialog box indicating such), but now it only takes 45 minutes. I've reviewed the setuperr.log (among the many, many others), cleaning it out prior to every attempt, and still get nothing out of the process that provides even a hint of where the problem is or what caused the "failure".

Such a shame this product, as much as it sucks, isn't a vacuum (new business opportunity for Microsoft?).

On to attempt 28!

Intel i5, 3.8GHz; 16GB RAM; 1 TB SSD, about half used.

Yea, not buying that it's the fault of "the system."

Admittedly, it's hard to design something that works smoothly on as many different systems and on as many different software setups, but after 3.5 months, one would like to think that the update process would be a bit less rocky. 

Good news: I'm at 82%. 

Bad news: it has been at 82% for about an hour.

Thank God for day drinking.