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

f14tomcat · 24 Nov 2020

pietcorus2 said:

" I rolled back to .630 from shortly after Patch Tuesday. It will stay there till next PT. "...........so , you wont try/stay on 662 ?
I did not encounter any problems /errors after 662 , but I have my doubts on installing "insider"-updates on a " non-insider" machine ....!

I have no reason to. I have RTM, Release preview, and Beta systems, last 2 are on .662. No reason to force .662 onto my RTM and hope in 2 weeks the whole thing doesn't regurgitate. RTM is, like most people, my daily work machine. I depend on it being up.

Geneo · 24 Nov 2020

Ghot said:

I know one thing... I'm gonna save that .630 backup for a while.

Ditto.

f14tomcat · 24 Nov 2020

kado897 said:

Yes RP but you may have the same problem next PT and it will probably be offered as optional this week.

I didn't have any problems with RP and Beta going from 630>662. I wouldn't expect any on RTM. Only reason I originally had a problem on RTM is because I had updated to 661, and of course 662 didn't like that. RP and Beta were fine.

magilla · 24 Nov 2020

f14tomcat said:

I didn't have any problems with RP and Beta going from 630>662. I wouldn't expect any on RTM. Only reason I originally had a problem on RTM is because I had updated to 661, and of course 662 didn't like that. RP and Beta were fine.

Just for information, I just did a inplace repair install. It completed and when I asked for updates, it applied 662 and no other updates. Update has been on all my other computers with no problem, also.

f14tomcat · 24 Nov 2020

magilla said:

Just for information, I just did a inplace repair install. It completed and when I asked for updates, it applied 662 and no other updates. Update has been on all my other computers with no problem, also.

What build are you talking about? RTM, RP, Beta?

Josey Wales · 24 Nov 2020

pietcorus2 said:

" I joined the IP in the Release Preview and I am getting the same error from yesterday ussing the Cab. "..............from 661 , 630 ??

Should be fine when installing from 630.........( according to my own experience and others )

I do mot have an image dating back to .630. I tried 5 times in the RP same error each time. I am done. I never have had so many problems trying to install a CU.

NavyLCDR · 24 Nov 2020

Bree said:

Possibly related - what I did notice was that after updating 19042.630 to 662 and doing my usual Windows Update Clean up was that my system was now some 2GB larger than before. Didn't even bother to try SFC, just rolled back to the 630 Macrium image I made immediately before updating.

@Bree on three different systems now, one physical, two virtual. When I was on .630, I ran dism /cleanup-image on all three systems with /resetbase and then /restorehealth options. I also ran sfc /scannow on all systems. There were no errors on the systems on .630. Then when I applied the .cab file for either .661 or .662, it did not matter, after the update, sfc /scannow found corrupt files and repaired them on all three systems.

emailx45 · 24 Nov 2020

for me all updates is done by file (not by Windows Update) and all was installed with problem. be in WSU or CAB installation.

magilla · 24 Nov 2020

f14tomcat said:

What build are you talking about? RTM, RP, Beta?

RP.

bbinnard · 24 Nov 2020

After installing Windows10.0-KB4586853-x64_330daa4ac35808160113ccb6b5a6a0fd54b414cd.cab Winver shows that I am on 20H2 Build 19042.661. What is Build 19042.662 and should I be on it? Or can I forget it?