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

steve108 said:

Download/install the Enablement KB mentioned at top of OP to update to 21H2

Thank you, Steve.

Is this something, you would personally recommend? (Essential/necessary). Or, should I wait until next 'Patch Tuesday', in Oct., as I was thinking.


Sorry buddy, not meaning to put you on the spot.

~~~~

Edited, I appreciate your prompt response.

I think I'll wait. As it seems everything is functioning okay, at present.


Thank you, again.

WXC said:

Thank you, Steve.

Is this something, you would personally recommend? (Essential/necessary). Or, should I wait until next 'Patch Tuesday', in Oct., as I was thinking.


Sorry buddy, not meaning to put you on the spot.

I updated to 21H2 last month... haven't had any problems.
The upgrade took like 3 seconds... seriously.

Ghot said:

I updated to 21H2 last month... haven't had any problems.
The upgrade took like 3 seconds... seriously.

Thank you, Ghot.

I was editing my post to Steve, when you replied.

I'll wait a bit, for now.

WXC said:

Thank you, Ghot.

I was editing my post to Steve, when you replied.

I'll wait a bit, for now.

When I did the enablement package to get 21H2, I remember thinking... "the only thing that could of changed was the feature update number. It was too fast to change anything else".







I know it sounds like an exaggeration, but the enablement package ran, then 3 seconds later it said... time to reboot.

Ghot said:

When I did the enablement package to get 21H2, I remember thinking... "the only thing that could of changed was the feature update number. It was too fast to change anything else".

Thank you, buddy.

That is all I needed to read.


My very best, to you.

~~~~

Not to stray too far off topic, but do you have any idea why it took over an hour, to run SFC, the final (2nd) time? That has never happened to me before. Just curious. I run a tight ship, (so to speak). 20 GB on a 1 TB 7200 spinner. lol

Nothing on my PC, but music files.

WXC said:

Thank you, buddy.

That is all I needed to read.


My very best, to you.

~~~~

Not to stray too far off topic, but do you have any idea why it took over an hour, to run SFC, the final (2nd) time? That has never happened to me before. Just curious. I run a tight ship, (so to speak). 20 GB on a 1 TB 7500 spinner. lol

Nothing on my PC, but music files.

Sometimes SFC runs slow like that. If you reboot before you run it... it only takes like 3-4 minutes, on a spinner.
Under 2 minutes on an SSD.

Especially if you just ran DISM component store cleanup. Always reboot after that, before running SFC.

Ghot said:

Sometimes SFC runs slow like that. If you reboot before you run it... it only takes like 3-4 minutes.

Ahhh, thank you, very much.

- - - Updated - - -

Ghot said:

Sometimes SFC runs slow like that. If you reboot before you run it... it only takes like 3-4 minutes, on a spinner.
Under 2 minutes on an SSD.

Especially if you just ran DISM component store cleanup. Always reboot after that, before running SFC.

Noted.

Thank you.

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