New
#1
DISM RestoreHealth gives error, should I be worried?
After updating to Creators (Win 10 ver 1703), I ran SFC /scannow from admin-level command prompt, which found no integrity violations. I then ran DISM RestoreHealth option (I don't have exact syntax memorized, I always copy/paste from Brink's tutorial), which gave an error.
I rebooted, and ran DISM ScanHealth, which completed and said the component store was repairable, but when I ran DISM RestoreHealth, it gave an error again - probably exact same error as previously. I took screenshot this time.
Everything other than DISM seems to work fine so far, so is there really no problem here?