I am curious, before I go wandering out in the mine field, is it advisable to run the System File Checker tool without having first run the DISM tool???
My copy of DISM doesn't seem to have the "Repair Image" function, but I would still like to check the System Files to see if they're OK.
Windows 10, Build 2004... 630
Yes.
SFC - TenForumsTutorials
- Option 3, and read the notes at the end that refer to a DISM command run whilst online if SFC could not repair all the faults it found
- Some people swear that they get better results by running DISM before SFC but I don't bother. An MS KB article now says that you should run DISM first but I think they were drunk when they wrote it - Use the System File Checker tool to repair missing or corrupted system files (KB929833) - MSSupport
- I just run SFC Option 3 and then run that DISM command if it is required.
Denis
Last edited by Try3; 29 Nov 2020 at 23:13.
This script will run scannow and dism commands to check / repair the operating system and component store:
Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.
If you want just the SFC and DISM commands, run Tuneup1.bat. It doesn't run the additional WMIC and BCDEDIT commands.
Keith,
I omitted one salient fact from my first post but have now added it. The omission was the result of a mental block caused by my contempt for the advice referred to.
An MS KB article now says that you should run DISM first but I think they were drunk when they wrote it - Use the System File Checker tool to repair missing or corrupted system files (KB929833) - MSSupport
This KB tells you to fix your system before finding out whether your system has a fault or not, i.e. DISM before SFC, without providing any justification or even explanation.
This KB also makes the false statement that the command to extract SFC results from the CBS.log must be run elevated.
This KB fails to make clear in para 2 that you need to be connected to the internet before running the DISM command.
[Mini-rant]
Windows is pretty reliable.
SFC will normally report no faults [because there are no faults].
So why on earth can it be worthwhile doing the step for fixing it before the step for finding out if it needs fixing or not?
Does anybody take their computer to a technician to get the power button tested before each time they want to turn the computer on?
[/Mini-rant]
All the best,
Denis
As far as I can tell sfc DEPENDS on DISM (to check whether the repository or whatever isn't corrupt prior to do repairs). So yes, you should always run DISM before sfc.
I am currently running sfc /SCANNOW, and it doesn't invoke DISM as far as I can see.
Microsoft says -
If you are running Windows 10, Windows 8.1 or Windows 8, first run the inbox Deployment Image Servicing and Management (DISM) tool prior to running the System File Checker.
https://support.microsoft.com/en-us/...rrupted-system
There were many Ten Forums threads where sfc /scannow was ran before and after dism /online /cleanup-image /restorehealth.
These are some threads to display the benefits in running scannow before restorehealth.
When running scannow the end user may want to know whether there was a problem.
Running restorehealth first hides the scannow problems.
The end user would need to scan CBS logs or run sfcdetails to find the problems.
If the end user is looking for diagnostics then run scannow first.
If the end user is looking for therapeutics (a fixed or unfixable scannow) then run restorehealth first.
BSOD after Wakeup from Standby (DRIVER_POWERSTATE_FAILURE)
Upgrade to 2004 green sceen driver_pnp_watchdog - rolls back
Can't Load Into Windows 10 Normally
ZIP ATTACHED Blue screen on my Dell Opt 9020 with Win 10x64 Pro 1909
BSOD Kernal Mode Heap Corruption
Random reboots and "Invalid System Disk" message
If I were just doing diagnostics, I would run SFC /VERIFYONLY, which finds issues, but doesn't fix anything.
Regardless of whether /VERIFYONLY or /SCANNOW is used, if errors are found, and it's a help desk type situation, I would want the user to run...
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log > "%userprofile%\Desktop\sfcdetails.txt"
...and post that log.
Sfc /scannow reports if it finds a problem and performs a fix if it able to.
So the diagnostics are not hidden.
Quote
