New
#1
DISM, once over...
Windows version: 21H1 (OS Build 19043.1165)
In this thread, the issue with DISM just recently had been resolved.
The system had a BSOD today due to "MEMORY_MANAGEMENT, according to the BlueScreenView app. The actual BSOD screen stated something about critical system files, but it had not been recorded.
Running the commands of "scf and dism..." gave some interesting results:
The "/CheckHealth and /ScanHealth" disagree on the status of the component store; shouldn't they be the same?
Running the the DISM command with "/RestoreHealth" option finishes normally. After reboot, checked the component store again with "/CheckHealth and /ScanHealth". The results were the same as in the image above.
What is the reason for the difference and how can it be remediated?
TIA...