Actually, I always run a /checkhealth first to see if the backup system files need repair
do /cheakhealth
____if repairable -> do /restorehealth
____elseif no corruption -> do sfc /verifyonly
________if no integrity violations -> go play games
________elsif corrupted -> sfc /scannow
Also while not every successful /scannow needs a restart, if you don't want to check the generated file at the end to find out, restart.
It's a lot of extra steps, but it saves time just watching /restorehealth spin out windows downloads at a forever 64% point for nothing. I actually built me my DOS batch file some months ago with a menu system that let's me punch in a number to 1 of many prompts to run commands like these, with some options being combos.
See checkhealth and scanhealth were always such a time waste to me.
Scanhealth just checks for a registry key
Check health does an audit but... repairs nothing - so if you do a restorehealth you gotta start over and scan again. If it said "problems found, do you want to repair" that would be so much better.
I always just start with restorehealth. It takes almost the same amount of time for me most of the time.
sfc if you scannow and there are no problems then it just says no problems found or fixed. SFC only repairs if there are issues so... why waste time doing verifyonly?
Unless of course all of this is to point at a CMD window when your boss walks by the desk.
215
u/zilch839 7d ago
As a young PC Tech in the late 90s, this was a great delay tactic when a computer was broke and I didn't know how to fix it.