KB4598242 CU Windows 10 v2004 build 19041.746 and v20H2 19042.746 Win Update

One laptop and one desktop both completed no issues.
Both no running Version 20H2 (OS Build 19042.746) .

pietcorus2 said:

" What version number of Windows 10 are you on? ".........its on 10942.685 .
Used old MR backup ( 29-11-2020 ) with Off.2016 , update went ok !
After updating to Off.2019 , not possible to get this latest CU..............

That's a new one. For what it's worth I upgraded to 746 from 685 with Office 2019 installed and it went fine. I'm sure you may have already tried resetting Windows Update but if not that would be my next step.

Downloaded this on one SSD and all went well. But lost my video and sound capabilities. Then booted to my other SSD with Preview installed . Then all hell broke loose AGAIN. Wiped my Production SSD causing me to reload everything. This sucks. I've now reinstalled all my software and cloned that SSD. I'm done with this 20H2.

Yes , thanks to MR , used old backup , with Off.2016 still installed ..........updated perfect !
Have to update the other software from 15 Dec. untill now again..........

jamis said:

Thanks for the tip. The key is already set as you described. Guess I'll remove the CU as this is causing me not to be able to use my USB drives for system images.

Update: Removed CU KB4598242 and have the two front USB ports back. I just love technology. Thanks MS.

I had a helluva problem last night/early hours of this morning with this CU - I was on build 685 prior to this, so everything was as up to date as it could be.

I was having constant 'Generic Superspeed USB HUB' error:43 issues after updating, and wasted way too many hours trying to troubleshoot this. It appears related to my Startech PCIe USB 3.0 extension card and the driver available from Startech are so old (2012) that it's not smart to install them. But I tried, and same issues.

Went back to a MR image from last week and all good.

I even installed the SSU that I got from this thread before applying the update.
Now I am scared to update this CU from yesterday, and might have to use the WAU Manager to just not waste a full day with this crap:
Enable or Disable Windows Update Automatic Updates in Windows 10

This is a current high-end gaming rig, always kept up to date, but I have a lot of USB device requirements (hence the need for the powered Startech USB card with 4 USB 3.0 ports, each with their own separate USB Controller to overcome motherboard USB bandwidth limitations).
Does this older app still work to control the entire WAU process, or is it still limited to only delaying for 7 days?

Thanks as always for the great info on this site.

I see a few people reporting earlier in the thread that the update seemed to hang at 74% completed.
This happened to me too, and has happened before with some other CUs in the past as well.
This time it must have stopped on 74% for a good 30 minutes!
No apparent disk activity. I was just on the point of giving up and manually rebooting when it suddenly came back to life again, and then completed successfully, but why does this happen?
As I said, I've had it happen with other updates in the past, but not by any means all of them.
Half an hour with apparently no activity is ridiculous!

DaveH1 said:

I see a few people reporting earlier in the thread that the update seemed to hang at 74% completed.
This happened to me too, and has happened before with some other CUs in the past as well.
This time it must have stopped on 74% for a good 30 minutes!
No apparent disk activity. I was just on the point of giving up and manually rebooting when it suddenly came back to life again, and then completed successfully, but why does this happen?
As I said, I've had it happen with other updates in the past, but not by any means all of them.
Half an hour with apparently no activity is ridiculous!

First off, I very seriously doubt that anyone on the planet knows why this happens from time to time - seems to happen to everyone sooner or later.

Second, Microsoft's stated paradigm at the launch of Windows 10 was that these updates should be in the background, and ideally, not even noticed. If it takes half an hour, or two hours, so what? In the online part of it, it's background. You're supposed to be doing your work, not babysitting an update But I know we all like to feel like we're doing something! Just forget about it and let it go.

My partner here works on her Windows 10 computers (she needs two for her research and data crunching and GIS work) for hours a day, and never checks for updates, nor even cares about whatever build or whatever CU. I just checked her computers - they're on .746. It just sort of happens for her, without any annoyance to her.

I wonder how many update problems are due to people closely watching the update process, freaking out when it pauses at some percentage (as is always does, sooner or later), and forcing a reboot, becuase... why?

WU is not a snappy, determinate process, never has been. It's done according to some mysterious algorithm that does what it does, and if you worry about the timing of various stages of it and whatnot, and comparing it to other reports, you'll probably drive yourself crazy.

sgage said:

First off, I very seriously doubt that anyone on the planet knows why this happens from time to time - seems to happen to everyone sooner or later.
Second, Microsoft's stated paradigm at the launch of Windows 10 was that these updates should be in the background, and ideally, not even noticed. If it takes half an hour, or two hours, so what? In the online part of it, it's background. You're supposed to be doing your work, not babysitting an update But I know we all like to feel like we're doing something! Just forget about it and let it go.
My partner here works on her Windows 10 computers (she needs two for her research and data crunching and GIS work) for hours a day, and never checks for updates, nor even cares about whatever build or whatever CU. I just checked her computers - they're on .746. It just sort of happens for her, without any annoyance to her.
I wonder how many update problems are due to people closely watching the update process, freaking out when it pauses at some percentage (as is always does, sooner or later), and forcing a reboot, becuase... why?
WU is not a snappy, determinate process, never has been. It's done according to some mysterious algorithm that does what it does, and if you worry about the timing of various stages of it and whatnot, and comparing it to other reports, you'll probably drive yourself crazy.

I certainly do agree with the principle of what you say, but as a computer enthusiast (I won't use the n word!) I like to be aware of what my machine is doing, and I suspect that most of the others on this forum are the same, or they wouldn't be here!
I'm not going to lose any sleep over it, but I'm just puzzled as to why anything should take that long to install. It makes me worry that something is wrong with my setup, especially as others are reporting that it installed comparatively very quickly.