Windows 10 Feature Update 2004 taking too long to install

Thanks for the big team for every update! I have lasted version Win 10.0.19041.450 .  I have a ThinkPad Pro CPU 7e generation with more than 32Go RAM. Since few weeks, when I boot my laptop and I signin with standard account, the process Windows Update took around 15-20% of my CPU for 1 or 2 minutes. The fans are always quiet except if the CPU work more. Microsoft have new method to check how update the OS !? If I can find the good method (clue) to say to the service Win Update please keep quiet! I found an easy solution, I disabled the service Windows Update !! 

That is three or four updates ago. It's the one that's on my laptop, 2004 19041.508, but I am holding it here for a reason. In fact, I may do a clean install to get rid of 600+ GB of OneDrive files. As far as the best method, it depends on whether you have trouble with the standard update process. Otherwise....

Here I am, on my birthday, just wanted to play some games before going out.

But no, Windows automatically started this update, even though I set it up to ask me before installing updates.

It started at 1AM.. Now it's 10:30. Ridiculous.

I am an independent PC support specialist and my clients are getting it rolled out to them.  One of my machines was asking me to install it or set a date and time.  The average time from saying yes to ready to use again is around 6 hours.  That time is not any faster on a brand new computer with 9th generation Core I-7 4ghz, with 1TB PCIE NvME SSD and 32gb of RAM.

For a giggle, I asked Google how long it takes to install the May 2004 Update which is now being called "Feature update to Windows 10, version 20H2" and Google's pleasant voice read off part of an article saying it takes about twenty minutes.  I giggled all right and that is how I wound up here.  I just wanted to toss in my experience with it on the 15 or so computers I have actually witnessed hands-on do it.  A few of those I was called in after it failed  It seems to install more successfully on custom-built machines than the name brand store-bought machines from the big manufacturers.  That is just my observation so far.  My laptop took it fine and it is one of those brand names we all know.  But it did take about 6 hours.

I am an independent PC support specialist and my clients are getting it rolled out to them.  One of my machines was asking me to install it or set a date and time.  The average time from saying yes to ready to use again is around 6 hours.  That time is not any faster on a brand new computer with 9th generation Core I-7 4ghz, with 1TB PCIE NvME SSD and 32gb of RAM.

For a giggle, I asked Google how long it takes to install the May 2004 Update which is now being called "Feature update to Windows 10, version 20H2" and Google's pleasant voice read off part of an article saying it takes about twenty minutes.  I giggled all right and that is how I wound up here.  I just wanted to toss in my experience with it on the 15 or so computers I have actually witnessed hands-on do it.  A few of those I was called in after it failed  It seems to install more successfully on custom-built machines than the name brand store-bought machines from the big manufacturers.  That is just my observation so far.  My laptop took it fine and it is one of those brand names we all know.  But it did take about 6 hours.

As an "Insider" I get these updates before the public, or so I'm told. The GOOGLE time you mentioned, is longer than any of the 20H2 updates have taken. There has been 4 or more, and the longest time it took for the update was 13 minutes. I'm at 20211.1000 release. I did build my rig. I have an AMD Ryzen 5 CPU, that boosts up to 4.2Ghz. I have a 2TB NAND WD M.2 SSD, with 32GB RAM. An MSI Radeon RX 570 DirectX 12 RX 570 ARMOR 8G OCGPU.

I'm not sure why this thing is so buggy, and my "Insider" tag has gotten me no closer to a solution as anybody else. But 6 hours! Man!....

I'm having the same issue, only a few months later.

I was informed that an update was available (which routinely happens mid month) and without too much concern began the update process.

The machine presumably had to reboot to complete the install, and after about 20 min I was at a blue screen with the notice that it was updating. 4+ hours later, the screen hadn't changed. It would be nice if MS had bothered to put some sort of percent update status, but nothing except an endlessly spiraling circle.

I assumed that the install had stalled, which has happened in the past (gee, thanks Microsoft), so I did a hard reboot. That resulted in a black screen with the line "undoing changes." 3+ hours later, it finally came up to the desktop, but everything was glacially slow. I clicked on settings (waited 10+ min), clicked on updates (waited 10+ min) and saw an update status of "installing - 23%."

I though this a bit reassuring, so I went to bed, certain that by morning all would be well.

Morning.

Things are kinda working -- my off-line backup apparently worked without issue -- but that 23% had only crept up to 52% in 6 hours. Now, close to 20 hours in, and it's only at 75%.

Over the decades, I've fought through myriad updates. I was there in the DOS days and when Windows 3 (3.1) became Windows 95. But this latest has been the worst. 

Who needs a computer virus when you have Windows?