New
#1
Thanks for the reply which was expected. This post is not aimed at the forum. It was aimed at Microsoft developers who regularly read and analyze user issues posted on this forum. I already discussed the use of sfc on one of the Microsoft forums but the reply didn't convince me.
I created various scenarios repeatedly, and your scenario is the logical choice, provided chkdsk /f/v (fix and verify) is executed prior to backup. This is more important than sfc, or dism, based on experience.
I would love to hear your, and the community's opinion on this issue.
Last edited by ineuw; 14 Nov 2021 at 01:13.
"Microsoft developers who regularly read and analyze user issues posted on this forum"? I wasn't aware that there are any such.
Unfortunately for most users the customizations and uninstalling of built-in features tend to get set back to an as-shipped condition with the twice-yearly Version Upgrades and sometimes with the more-frequent Updates. Most of the unwanted features I ignore them or when possible disable from loading in the background.
Windows updates are not necessarily complete as soon as the "100% - Done" message appears.
I've seen large Windows Update/Trusted Installer services activity for hours and sometimes days
in Task Manager after a big update. I doubt very much any files are actually corrupted, as SFC may
claim. Probably it's just a temporary lack of syncronization between whatever it is SFC checks and
the actual state of system files as they are brought up-to-date over that extended period of time.
@kreemoweet, thanks. This is the logical and best explanation. Otherwise, if the corruption is permanent, it would have been noted on forums by professionals and other users earlier. I search before posting and would have stumbled upon the explanation. — Now, I will wait a few days after an update before using sfc.