KB4557957 Cumulative Update Windows 10 v2004 build 19041.329 - June 9 Win Update

Upgraded to 2004 and 19041.329 in one go.

• DISM and sfc reported no issues.
• DISM /online /Cleanup-Image /StartComponentCleanup cleaned up around 3 GB.
• Settings > System > Storage > Temporary files > Windows Update Clean-up took care of Windows.old

The only apparent thing noticed, was that while sfc /scannow was taking around 01:40 to complete in 1909, this time it took more than 12 minutes, but found no issues.

So far, so good.

pietcorus2 said:

" So far, so good " ..........I tought so too , untill I discovered several bugs , I could live with most of them .
Now today , I noticed my Windows startmenu does not work well , when opening ; it shows a totally blue screen and have to sign in again ! I upgraded with the "Open Shell" startmenu ( startsup with windows ) , which works fine , but when choosing for Windows startmenu , blue screen ( explorer off ?) .
This is way too much ........rolled back to 1909 , all fine now ! Will wait untill its been offered by WU and will not startup with Open Shell , during the upgrade......
Anyone in this forum who experienced the same problem.......??

Open Shell didn't give me any problems with the upgrade, both it and the Windows start menu are the same as 1909.

ddelo said:

• DISM /online /Cleanup-Image /StartComponentCleanup cleaned up around 3 GB.
• Settings > System > Storage > Temporary files > Windows Update Clean-up took care of Windows.old

The only apparent thing noticed, was that while sfc /scannow was taking around 01:40 to complete in 1909, this time it took more than 12 minutes, but found no issues.

I have been seeing this exact same chronic behavior with sfc /scannow and well before 1909, where for me it goes from an easy 4-5 to well over 30 minutes immediately AFTER either of these types of cleanups - DISM or Settings > System > Storage > Temporary files.

Doing these sfc scans regularly before every MR image, I've seen this predictable time pattern for a while now.

Worth noting, it will stay at this longer 5-6X expansion for some time or until I do my next Cumulative Update where I'll find it's back to just a few minutes again. Then after the cleanups it's 25-35 minutes again. ;o|

I've always assumed something about these cleanups just makes sfc's job more laborious.

pietcorus2 said:

Will wait untill its been offered by WU

It looks that you have forced the 2004 upgrade and maybe it's the reason of the problem. That's not the case with me. I was offered the upgrade by WU, but I still keep my fingers crossed (for a day or two)

Farvatten said:

I have been seeing this exact same chronic behavior with sfc /scannow and well before 1909, where for me it goes from an easy 4-5 to well over 30 minutes immediately AFTER either of these types of cleanups - DISM or Settings > System > Storage > Temporary files.

Doing these sfc scans regularly before every MR image, I've seen this predictable time pattern for a while now.

Worth noting, it will stay at this longer 5-6X time for some time or until I do my next Cumulative Update where I'll find it's back to just a few minutes again. Then after the cleanups it's 25-35 minutes again. ;o|

I've always assumed something about these cleanups just makes sfc's job more laborious.

Thanks a lot for the info. I'll keep an eye on it.
I usually run dism and sfc whenever I restore a Macrium image or after an update/upgrade.