Originally Posted by ThrashZone
Yep sure enough throwing errors
Had to also scannow after using restorehealth to actually report anything being repaired restart back to clean.
A while back sfc was reporting falsely errors guess it's doing it again
Someone pointed out windows defender update caused it which I wouldn't doubt it seeing the new bs account protection features if not used may throw an error.
Yep. Looking at CBS.log showed errors related to PowerShell Defender modules. I don't know if any of this would cause problems down the road, but thankfully running dism and sfc again solved my errors.
This is only the 2nd time I have found system errors after an update. I have had very few minor problems with Windows 10 since switching over three years ago. I have to wonder if many of the people that have major issues when upgrading (e.g to 1903) have tons of system errors that need to be repaired.