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? 

I've attempted many scenarios...Windows Update, Update Assistant (both active and via ISO download), Microsoft Catalog, direct ISO download from my VLSC (both 2004.1 and this newer 2004.2). All of them step me through the process accordingly, but none ever complete. When attempting Windows Update, I get an error code and have searched the Internet far and wide for the cause...tried everything from the result of said search and get the same error code, if it completes at all (some attempts spin for days and days and days...64% and 93% are the most common numbers). I've tried various tools to scan the back-end (I.e., Process Monitor/Explorer for one) just to see if I might discover something hung up or stuck - nope. When attempting to complete the update via ISO, it's a bit of a different process, it's essentially conducting an upgrade (blue screen) and the result is, if it ends, the good ole vanilla "Update Failed" dialog box...no error code, no nothing. Much like the update process, this upgrade process can spin for days...I've seen it end in the 50s and 90s (%). Since I virtualized the environment, I've removed all non-essential apps, drivers, etc. I've even attempted to complete the "Keep Nothing" and same result.

It's beyond comical how the system runs tight (ZERO stability issues, NO system crashes and NADA event log entry concerns, etc.) and yet I can't get 2004 to install on a Dell Precision 7520, XEON E3-1505M v6, 32GB DDR4 2400MHz RAM and 512GB NVMe (with tons of space).

Known issues

• We’re looking into reports of the update process hanging for extended periods of time when attempting to install a new build.

Not sure if this will fix existing systems, or not. There was no elaboration. They were discussing the upcoming 20215 update coming out to developers. I dunno..., hopefully, it'll help the existing users too.

I just found out why I'm not being responded to about this, and some other issues. I saw this headline from the "Insider" website. "

As of September 22, 2020, customers will no longer be able to ask questions in the Microsoft Edge and Internet Explorer on Insider Preview forum

Why? What good is the program if it's members are not allowed to post questions? What?

You should return the PC this could mean it doesn't have an authentic Windows version. 

Have you read the comments in this thread? Is that what you got out of them? OK.

Please see my comment to Lance above this one regarding the unorthodoxy of my procedure. :)

Yeah, I saw that, and I think, well, you should have just let that one slide. You are trying to help, and you believe that we should just buy this, lock, stock, and barrel, and just sell ourselves out. Yeah, there are as many configurations, as there are users, but isn't that what MS is supposed to address? As an "Insider" both Windows and Office 365 (Microsoft), I can attest to many, many, MANY, issues with updates, installs, 3rd party software, drivers, et al. But I do what I do so that maybe something I learned can help someone on this forum, or others. MS pays big money to people who are supposed to address our concerns. To tell someone to just stick it isn't an amicable solution. You sound like Donald Trump, Jr! 

This update issue is not unique, but it certainly isn't the norm. My system updated Sunday morning, in about 1.5 hours. It restarted several times, but I have the latest build. I have a friend, whose system I maintain, that started this morning at 6, and he called me at 12:30 saying it was stuck on 84%. I told him to just let it run, and if it is still running in an hour, I'll come to him to see what I can do. But I wouldn't tell him that this is normal, because it's not.

Ok, I don't get your hostility. I'm writing as a former IT guy, and I'm neither telling people to selling themselves out, nor am I telling anyone to stick it. I don't know where you got that from, but you have clearly misinferred something I wrote. I figured out a way to get 2004 to install, I shared that info in the hopes that it would help others, and I explained - especially for those who are NOT IT skilled - why there's no way MS can produce a solution that will work for every computer. As an IT professional, you know that what I wrote is correct. That you're trying to help others is wonderful and I applaud that effort - I'm trying to do the same thing.

But, please, reread what I wrote and tell me where it was that I told people "sell out", "stick it" or that I behaved like Donnie Jr, because I cannot fathom where such a vitriolic series of claims came from.

OK, let's back this train up. There's no hostility, first. Second, YOU said "However, it's not the responsibility of computer and OS manufacturers to train each user - its their own responsibility and, with all the free and paid resources online and offline, there really aren't a lot of excuses that can be leveraged once someone has been online long enough aside from low IQ, a lack of confidence to explore and learn, fear of tech, having been mollycoddled to the point that they always rely on others to do things for them, etc. Of them all, only low IQ can form a permanent barrier to proper computer use, and millions, if not billions, have malware secretly installed on their computers because they don't know that the Internet is full of hidden nasties, especially on websites that provide gray and black market items." 

That, to me, is throwing in the towel and telling everybody to sink, or swim. Fact is, it IS MS responsibility to assure that every customer's experience is a memorable one, not a nightmare. And we are still talking about "updates". As an IT person, you have, no doubt, seen the lion's share of issues caused BY updates. But this is a problem WITH the update. Do you remember why Windows 8 was such a short-lived experience? Or go back to Win 2000, Win Millennium. Total nightmares! After Vista, no one thought the experience could be so cumbersome, and then along came '98. All of these were busts, and MS knew it. They took note of the customers dismay, and they fixed the problem. They did not send everybody a "This is the only way you can use this OS", notification. And you know that. I'm not trying to drag you down, but don't make excuses for a system that is clearly failing. Tell the respondents to install this update with the MCT tool. Something other than "it ain't MS fault". It IS MS fault! You know this, and THEY know this. I have confidence that they will address this issue, but no one should feel that they are dumba$$es because of a screwed up update stream from MS. That's all I am saying. This isn't against you, but don't make it about you. I've been in telecommunications/IT for 51 years, and I've seen many iterations of buck passing, and MS doesn't get a pass. Like I said, I'm an Insider and my feedback is not gonna blame anyone's computer!