KB4535996 CU Win 10 v1903 build 18362.693 and v1909 build 18363.693 Win Update

swarfega said:

Mine froze during the updating so had to press reset switch. Fortunately it seems to have repaired the update as I am on 693.

SFC found no errors.

I on the other hand have SFC errors found on 6 different machines ....

PS C:\WINDOWS\system32> sfc /verifyonly

Beginning system scan. This process will take some time.Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found integrity violations.For online repairs, details are included in the CBS log file located atwindir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offlinerepairs, details are included in the log file provided by the /OFFLOGFILE flag.

PS C:\WINDOWS\system32> DISM.exe /Online /Cleanup-Image /Scanhealth

Deployment Image Servicing and Management toolVersion: 10.0.18362.1

Image Version: 10.0.18363.693

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.
PS C:\WINDOWS\system32>

Found problems through sfc/ scannow and repaired them successfully.

Of my 3 PC's, the two updated without problems. But on my antique Thinkpad T60 from 2007, at the end of the update (the cumulative) I got an error message telling that the update had been interrupted and would resume on march the 6th. Why that, and has anybody else encountered this? The T60 has been updated before to latest builds and updates without issues.
/ Hans-Henrik

kado897 said:

Try running the WU troubleshooter.

Just run it and it has indeed fixed the problem, but didn't actually say what it fixed!

A couple of weeks ago I installed a new SSD in my PC. I cloned the old drive to the new drive. Yesterday I updated 9 PCs. The one with the new SSD that was cloned (with Macrium Reflect) gave me a failure to a blue screen where I had an option to insert a repair or installation media or press F8 which sent me to another screen where I had 9 other options (none of which worked) to choose from. Apparently some files got removed or just were not there from the cloning. Tried to use an image to restore and then update again and got the same results. So I just went on and installed Windows again (custom install) and all is well. I suspect there was an issue from cloning the new drive and NOT a windows bug. And this is why I usually don't clone drives but I thought I would just give it another whirl, never again.