I have a remote user about 1000 miles away , was just going to install sec updates, ran an sfc /scannow - with errors.
ran dism repair - returned the error "The component store has been corrupt.
OS is 20h2.
It has been totally stable that actually is the problem! LOL
I was thinking IF I tried to install Windows updates, if it could introduce OS stability issues, if it completed the updates, or perhaps even start with BSODs upon reboot. I've seen this occur before.
What totally throws me off with Windows 10 is you see these errors, when running sfc or dism, and at times even updates fail because of them, BUT - if the computer is stable, it is not logical to format/reinstall etc., to address errors that are not affecting the overall stability of the system.
I also ran surface scan, no block errors.... So once again, logical problems, which I see often with Windows 10, I wonder if the file system issues is simply buggier under Windows 10 - IDK
I guess if it prevents you from installing sec updates, then it should be addressed. Agreed? Just not logical to have to rebuild if there is no impact on the OS.
I have actually not seen this occur with older versions of Windows, where the OS can have errors, yet the the system is completely stable. I only recall seeing the errors when there is an impact on the OS Stability.
What do you guys think? What approach would you take!