Bork Tuesday, Any Problems Yet?

Windows 10 Storage Spaces bug fixed, safeguard hold remains
August 4, 2020
https://windowsreport.com/windows-10-parity-storage-spaces-bug/

 

No borks today! KB4566782 (cumulative) and KB4569745, (,NET Framework) installed after a servicing stack process (2x d/l and install). Now winver is 19041.450. 271 MB of Windows Update cleanup via Disk Cleanup.

 

Error 0x800f081f with KB4566782. Nice going Microsoft...

 

Have a disk image ready and go for it. If something is broken restore the image. 3 PCs updated here so far, no issues that are immediate. If something does come up, I'll roll it back. Usually there is nothing worth that much effort.

 

Updated Win10 v. 2004 to build 19041.450 with no issues. Cleanup of Win update with Disk Cleanup is just over 300 MB (I guess similar @plat1098 ). Unfortunately the memory bug associated with the Win optimize tool still persists, looks like it is not a priority for MS.

 

No problems here on my two Win10 x64 2004 machines.

 

I have only updated my home PC so far. No issues as of yet on 1909.

 

I just noticed a red icon on WD tray icon. I opened WD to find it had turned itself off somehow.

 

Yikes! Went to Check for Updates, and I see it had updated automatically to Win10 Home v. 2004 to build 19041.450 overnight ... KB4566782 (cumulative) and KB4569745, (.NET Framework) + Office updates.

Don't think I've experienced that before. No issues though.

 

No problems here with KB4571703 and KB4570508 on my Win 8.1 x64.

 

...running 'Win10 Pro' on one of my laptops. Yesterday i installed all available updates for build 1909. No problems so far...
Build 2004 is being offered for my machine... ...but i guess i will stay with build 1909 for a while. Build 2004 might still contain too many bugs.

My second laptop (win 8.1) is also running fine after installing all important updates yesterday.

 

Since 3 updates back, or more, my Pc has sounded like a steam engine. No driver update has helped.


Now since tuesdays update, silence - again.
At last!

 

Not really, the only thing that hasn't been fixed yet is MS Defragmenter and Optimizer tool, when one performs either of these operations it does not record the date of the operation. Of course upgrading is optional, I'm saying this for the sake of the argument.

 

Initially, 2004 was pretty unstable: lots of ESENT warnings, spams of them, along with some unfamiliar errors and warnings in the System logs. I allowed Full telemetry for like 2 days, and it worked well, the Event Viewer is quite clean now. Residual items that don't really affect day-to-day use: around 10-15 ESENT id 642 warnings in Application logs/day, and of course the Disk Optimizer "never run" bug.

It took a relatively long time to get 2004 stable and solid, like 3 weeks or so. By comparison, 1909 was a snap. If it wasn't such a hassle, I'd go back, it's prob. the best Windows 10 build Microsoft put out to date.

 

Agreed but to me 2004 is still not stable enough. I am running 1909 at home and at work with no intention of upgrading any time soon. It is a real mess imho.

 

Macrium to the rescue Microsoft should offer an immediate solution and not only that an error (0x800f081f) occured.

 

Unfortunately Macrium has had to come to the rescue a couple of times recently. If Microsoft had a solution maybe there would not have been a problem...

 

No problems or errors in updating in Win 10 2004.

 

Same here. Also no problems with Office 2019 updates noticed.

 

no issues here either.

 

Has anyone noticed that lsass.exe is no longer running as a PPL process on Win 10 Home 2004 ?

 

Have finally received 2004 update, it was a trouble free installation. No issues running on 2004.