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

eLPuSHeR said:

I think you can use 7-zip's TEST function on .CAB files to check if they are fine (CRC-Check). At least, I can do it from inside Total Commander.

You can also open Powershell and type the command:

Code:

(Get-FileHash <complete path to cab file>).Hash

e.g. (Get-FileHash C:\Temp\somecabfile.cab).Hash

@Brink

Rolled back to 19042.630 via a Macrium Reflect backup, and .662 installed no problem.
It seems that "either" .661 or .662 will work coming from .630

And sfc /scannow came back with no problems, before or after the .662 update.

Ghot said:

@Brink

Rolled back to 19042.630 via a Macrium Reflect backup, and .662 installed no problem.
It seems that "either" .661 or .662 will work coming from .630

And sfc /scannow came back with no problems, before or after the .662 update.

I had the same using WU in the RP Channel. Had to restore back to 630 before it would work. So it looks like waiting for it to be officially released via WU will not solve the problem.

pietcorus2 said:

" Rolled back to 19042.630 via a Macrium Reflect backup, and .662 installed no problem. ".............yes, did the same , went fine !

Wonder if this "insider-update " will make troubles with next CU update , as Im not an "insider "............!!

Yes. See my reply to Ghot above

kado897 said:

I had the same using WU in the RP Channel. Had to restore back to 630 before it would work. So it looks like waiting for it to be officially released via WU will not solve the problem.

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