KB4601319 CU Windows 10 v2004 build 19041.804 and v20H2 19042.804 Win Update

FrankW · 09 Feb 2021

Same here all 3 installed on Feb 10 (Philippines) in 30 minutes, now on 20h2 19042.804. WU asked/paused each time for a manual Restart with a note that automatic restart is scheduled outside working hours (in my case 10 pm - 6 am).
I probably would rate this build as one of the most stable W10 versions to date: Backed up (W7 BU) incl. an image file, that took less than 1 hour and when I ejected my external USB HDD it went flawless, no errors, no problem reports, no VSS or other issues.
Frank

DJG · 09 Feb 2021

DaveH1 said:

Installed fine on both my machines, with another .NET update.
It's really good to finally see the back of those endless ESENT 642 warnings!

Now all they need to fix is the also huge number of DistributedCOM 10016 warnings, which have been there far longer.
At least they are now warnings, not errors as they were for ages so the whole event log was a sea of red blobs!
I know they say they're nothing to worry about and to just ignore them, and they only happen when something doesn't happen as it should do, but when they happen all the time on everyone's systems you do wonder just how useful they are!

I only get occasional DistributedCOM errors, but the long list of ESENTs is happily gone.

curlysir · 09 Feb 2021

Updated 2 desktop and 2 laptops successfully. Having to do a repair install on another desktop, getting an 0xe0000100 error. this particular computer has never had problem updating until now. The other desktops have required the repair installation on recent updates. Not at the same time, one was on the last update and the other was on the update before that. Once they were repaired the later updates installed without problems like the 804 did tonight.

Update - just finished the repair install now at 20H2 804 on all machines.

Jen1 · 10 Feb 2021

I updated and didn't restart cause I was working, I left my PC on to finish the rendering of my video, for the first time Windows restart automatically without even asking and my without my consent, I lost 3 days work, I had an open TXT file, it opened upon restart with same changes I did before restarting,

I hate you Microsoft, don't do anything without asking, it literally felt like I was being raped.

secondsight · 10 Feb 2021

Task Manager seems fixed. Did I miss when that was or did this update fix it just now?

ugatme · 10 Feb 2021

Went without a hitch in less than 5 minutes. Be careful Microsoft, you might start getting a good reputation.

eLPuSHeR · 10 Feb 2021

Updated three PCs from WU without issues so far.

KCR · 10 Feb 2021

Berton said:

This is what I just got with that PS command after the Build update to 19042.804, the first listed is for .NET:

Attachment 318264

I got that too...

KB4601319 CU Windows 10 v2004 build 19041.804 and v20H2 19042.804-image.png

Lol... the time stamps seem a bit odd, though. .

~~I got that too...~~

Actually, they aren't the same. . .

jimbo45 · 10 Feb 2021

Hi there

This update broke Office 2019 for me !!! on a physical (real machine)

KB4601319 CU Windows 10 v2004 build 19041.804 and v20H2 19042.804-upd.png

Not just outlook but the whole thing

Excel for example gives same error

KB4601319 CU Windows 10 v2004 build 19041.804 and v20H2 19042.804-excel.png

Can't work without EXCEL etc !!!

Have to "bin" this update --reverting it.

Cheers
jimbo

secondsight · 10 Feb 2021

jimbo45 said:

Hi there

This update broke Office 2019 for me !!! on a physical (real machine)

Not just outlook but the whole thing

Excel for example gives same error

Can't work without EXCEL etc !!!

Have to "bin" this update --reverting it.

Cheers
jimbo

Is it not possible to repair Office from Control Panel-> Programs and Features?

Right click on it and choose Change

Then pick the kind of Repair you want.

KB4601319 CU Windows 10 v2004 build 19041.804 and v20H2 19042.804-2021-02-10_102633.jpg

0xc0000142 has been around for years and to the best of my knowledge can be cured by doing this.