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

Installed without error! :)

All three of my machines updated okay albeit slowly. The getting ready and D/L's went quick one to two minutes, it was the installs and restarts back to the desktop that averaged 40'. Surprisingly my 7 to 10 upgraded machine took the least, 26' from getting ready back to desktop, and all three now sit at v1909 | Build -18363.693.

Using an elevated PS I ran a sfc /scannow on all three and it found no integrity violations for either.

Related:
To view my third system specs click on "view my pc album" under: My Computers; System One or Two will take you to the same album.

Farvatten said:

It would be helpful for others to see what was corrupt and fixed in your CBS.logs.

Code:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

By any chance did you use 'Storage Sense' to clean up the update before your SFC /scannow?

sfc /scannow Finds and Repairs after Storage Sense Temp Clean

Back in July of 2019, I and other's ( @Bree ) found this "Windows Resource Protection found corrupt files and successfully repaired them." And yet afterward we could find no evidence in the CBS.logs of a fix taking place.

Yesterday, I did have a clean SFC scan afterwards, but I have not yet run my Storage Sense clean up on this update.

After running Storage Sense on my laptop just now and an immediate sfc /scannow, I've again received this "Windows Resource Protection found corrupt files and successfully repaired them.", and again like before, the log shows nothing repaired.

This had been chronic behavior after using Storage Sense under later versions of 1903 but stopped immediately after 1909 but has now returned.

Cant get this update to install on my desktop always get error 0x8e5e0147.

Installed without any issues on my laptop though.

dalchina said:

Others have found this helps:
Reset Windows Update in Windows 10

E.g.
https://answers.microsoft.com/en-us/...0-87688141a6ec

Thanks, running the windows update reset batch file solved it.

Brink said:

It was from yesterday.

LOL...you caught my deleted post. I mistakenly thought the original date of the event referenced in your post was to a "past" event...and realized after my "butinpushinfingyrs" moved faster than my brain that I really can't read calendars....LOL