KB4586853 CU Windows 10 v2004 build 19041.662 and v20H2 19042.662 Win Update

Bree · 01 Dec 2020

f14tomcat said:

...I just hope the "Stuckees" don't hit the wall again next Tuesday, regardless of the .6xx level. I hole in the files, if that's what it is, is still a hole, as far as the current .661 users are concerned.

In the absence of any .630 image to restore, those stuck on .661 have just one option available as far as I can see. The .661 update did include the fix that allows an in-place repair install that keeps files and installed apps.

secondsight · 01 Dec 2020

f14tomcat said:

Your probably right. I just hope the "Stuckees" don't hit the wall again next Tuesday, regardless of the .6xx level. I hole in the files, if that's what it is, is still a hole, as far as the current .661 users are concerned.

If we do hit a wall, there is always the in place downgrade to 630 using iso/usb. One interesting thing you raise here is the difference in files between 661 and 662. Dunno if anyone has looked inside them to see which files have changed or are missing. I was going to look....but then I saw this spider climbing a wall and so I'm watching that

Regardless of all that, I do wish that each change of version number no matter how small would get a different KB number. It can't be that difficult to do and may avoid a lot of confusion. He's made it! (the spider that is)

f14tomcat · 01 Dec 2020

secondsight said:

If we do hit a wall, there is always the in place downgrade to 630 using iso/usb. One interesting thing you raise here is the difference in files between 661 and 662. Dunno if anyone has looked inside them to see which files have changed or are missing. I was going to look....but then I saw this spider climbing a wall and so I'm watching that

Regardless of all that, I do wish that each change of version number no matter how small would get a different KB number. It can't be that difficult to do and may avoid a lot of confusion. He's made it! (the spider that is)

Thank you! 3 cheers for the spider!

f14tomcat · 01 Dec 2020

Bree said:

In the absence of any .630 image to restore, those stuck on .661 have just one option available as far as I can see. The .661 update did include the fix that allows an in-place repair install that keeps files and installed apps.

That's a bright light for those who can.

Quick link is appropriate here: Repair Install Windows 10 with an In-place Upgrade

Maybe someone can piece together the registry tweaks posted elsewhere that allow .662 to do the same, condense them down, and post here.

DJG · 01 Dec 2020

I just got KB4586876 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 on WU, FWIW.

f14tomcat · 01 Dec 2020

DJG said:

I just got KB4586876 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 on WU, FWIW.

Just checked, got that late yesterday, along with this Preview CU. Thanks for the advisory, though. MS likes to throw .Net's and CUs out at the oddest times lately.

linw · 01 Dec 2020

Whew, this is a long thread!

Got offered the KB4586852 on 3 x 20h2 19042.661 RTM comps yesterday. Two updated to 662 fine but the third will not. Got the 0x800f081f error.

Tried the cab file with same result. Have tried sfc /scannow and dism etc but no change.

Will just wait and see what else comes down the line.

Ghot · 01 Dec 2020

linw said:

Whew, this is a long thread!

Got offered the KB4586852 on 3 x 20h2 19042.661 RTM comps yesterday. Two updated to 662 fine but the third will not. Got the 0x800f081f error.

Tried the cab file with same result. Have tried sfc /scannow and dism etc but no change.

Will just wait and see what else comes down the line.

For some of us, we had to roll back to .630 version, before it would take the .662 update. Others had no problems going from .661 to .662.

In my case, I had a Macrium backup from Nov 13th which was made right after I went to .630. So I just restored to that, and then .662 worked flawlessly.

Some others, did an In-Place "downgrade" to the original 20H2, then used the CAB file to get to .662.

But as you mentioned...waiting is probably fine as well. I've had both .661 and .662 on this comp and honestly can't tell the difference.

midgo · 02 Dec 2020

Ghot said:

For some of us, we had to roll back to .630 version, before it would take the .662 update. Others had no problems going from .661 to .662.

I did an in place upgrade to .630 because .662 installed by the CAB method made my boot up time extremely long for some reason, 1.30 minutes from Start.
Yesterday I was offered the .662 upgrade by WU.
I installed it and so far there have been no issues with my boot up times.
From shut down Windows logo to desk top approximately 15 seconds.
From restart Windows logo to desktop around 30 seconds.

enigma101 · 02 Dec 2020

To all those stuck on .661 i would recommend making yourself an ISO for .662 from UUP Dump and performing an in-place upgrade. This has worked for me on 7 different PCs to date.