KB5005565 Windows 10 2004 19041.1237, 20H2 19042.1237, 21H1 19043.1237 Win Update

WXC · 14 Sep 2021

Ghot said:

Iirc, SFC started doing that around Feb. 2021. After a monthly update I would run DISM store cleanup, then I would reboot and run sfc /scannow. Since February, if I didn't reboot... sfc would take some serious time to run.
That's on my system with a 2.5" 500 GB SSD with 38 GB on C:\

But If I run sfc first, OR run DISM store cleanup, then reboot, and then run sfc... it only takes me about 1 min 15 seconds to run sfc.

/edit

When I say DISM store cleanup, I mean this... Dism.exe /online /Cleanup-Image /StartComponentCleanup

Clean Up Component Store (WinSxS folder) in Windows 10

Got you, buddy. All noted, for future endeavors.

I appreciate you, and, of course, your knowledge and willingness to share.

- - - Updated - - -

steve108 said:

I've personally not updated my PCs to 21H2.

2004 works just fine for me here and Microsoft is still providing updates for it

Thank you Steve.

I certainly, appreciate the reply.

Wishing you, the best.

fg2001gf10F · 14 Sep 2021

steve108 said:

In case anyone missed it

:
KB5005565 Windows 10 2004 19041.1237, 20H2 19042.1237, 21H1 19043.1237

KB5005565 Windows 10 2004 19041.1237, 20H2 19042.1237, 21H1 19043.1237
Cumulative Update - September 14, 2021

All done, 6 machines.

CountMike · 14 Sep 2021

RingTailCoon · 15 Sep 2021

Welllll....... I think that update fixed the overly-LOOOOOOOOOONG chugging of my HD, whatever it was doing right after booting into Windows. It now stays quiet (after yesterday!)

eLPuSHeR · 15 Sep 2021

ThompsoniusIV said:

I got this:
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Make sure YOU ARE CONNECTED TO THE INTERNET

Then do (in this order)

dism /online /cleanup-image /restorehealth
sfc /scannow

The order is important because sfc relies on dism.

eLPuSHeR · 15 Sep 2021

RingTailCoon said:

Welllll....... I think that update fixed the overly-LOOOOOOOOOONG chugging of my HD, whatever it was doing right after booting into Windows. It now stays quiet (after yesterday!)

Probably latest MSRT. It took a while on my i7-7700k while it took fewer time on my ancient i7-5960x.

PanosG · 15 Sep 2021

KB5005565 Windows 10 2004 19041.1237, 20H2 19042.1237, 21H1 19043.1237-1237.jpg

No problems here!

ThompsoniusIV · 15 Sep 2021

eLPuSHeR said:

Make sure YOU ARE CONNECTED TO THE INTERNET

Then do (in this order)

dism /online /cleanup-image /restorehealth
sfc /scannow

The order is important because sfc relies on dism.

The problem is, is that it does not finnish the restorehealth command. It freezes at 62.3% and then I got the error I mentioned above.

RingTailCoon · 15 Sep 2021

eLPuSHeR said:

Probably latest MSRT. It took a while on my i7-7700k while it took fewer time on my ancient i7-5960x.

Thanks, it drove me quite gaga after each boot in windows. Thankfully after the new version/update it stayed quiet! :) Prob a bug in the last version! :)

eLPuSHeR · 15 Sep 2021

ThompsoniusIV said:

The problem is, is that it does not finnish the restorehealth command. It freezes at 62.3% and then I got the error I mentioned above.

Then you will have to use an offline source someway.