I've seen a couple of references to SFC /scannow here occasionally.
That's the built-in utility to check whether there is any corruption in
your running Windows system, and (hopefully) fix it. It's an invaluable maintenance tool and I use it regularly.
It was a long time before I realised that you should also check the "component store" first, as that's what the SFC command uses as its reference. (For years SFC didn't seem to fix anything - that was why).
You use the DISM utility to check that.
I've seen a couple of references to SFC /scannow here occasionally.
That's the built-in utility to check whether there is any corruption in
your running Windows system, and (hopefully) fix it. It's an invaluable maintenance tool and I use it regularly.
It was a long time before I realised that you should also check the "component store" first, as that's what the SFC command uses as its reference. (For years SFC didn't seem to fix anything - that was why).
You use the DISM utility to check that.
These utilities are very slow on slow machines, and you need to check
whether both succeeded, though it doesn't do any harm to run SFC even if
DISM reports problems - you just need to know, so you can run DISM
agains with the options that fix the component store. Here's one of
many articles telling you how to do this: https://www.windowscentral.com/microsoft/windows-help/how-to-use-dism- command-tool-to-repair-windows-10-image
To make my life easier, I've gradually evolved a script which:
1) Checks if it's being run as admin
2) Changes colour once the utilities have completed
3) Spawns a new window once DISM has completed which runs SFC
-- these things make the check easier.
It isn't particularly easy to make the SFC run conditional on the
findings of DISM, so while it's possible to analyse the output message
(no relevant exit stats available) I haven't bothered. If you want to
try it, create a text file, copy and paste the lines below into it, and
then change the file extension to .CMD. Then right-click and pick "run
as administrator. And yes, it's probably easier in PowerShell, but who
at my age has time to learn PowerShell? ======================================================================
### ENSURE THE LINE INDICATED BELOW IS SAVED AS ONE LINE
- LIKELY TO BE WRAPPED HERE ### ======================================================================
@echo off
echo Administrative permissions required.
echo Detecting permissions...
net session >nul 2>&1
if %errorLevel% == 0 (
echo Success: Administrative permissions confirmed.
) else (
color 4F
echo.
echo ### Failure: Current permissions inadequate:
echo ### Right-click the file and pick 'Run as administrator'
echo ### Exiting...
echo.
pause
exit
)
REM ### NEXT LINE MUST BE ALL ON ONE LINE
title "DISM" & dism /online /cleanup-image /scanhealth & color 1F &
start "SFC" cmd /K "sfc /scannow & color 5F"
echo.
echo "Check status messages. Ready to exit"
pause
exit
On 5/21/2026 6:10 AM, Philip Herlihy wrote:
I've seen a couple of references to SFC /scannow here occasionally.
That's the built-in utility to check whether there is any corruption in
your running Windows system, and (hopefully) fix it. It's an invaluable
maintenance tool and I use it regularly.
It was a long time before I realised that you should also check the
"component store" first, as that's what the SFC command uses as its
reference. (For years SFC didn't seem to fix anything - that was why).
You use the DISM utility to check that.
Thanks, Philip.
I did not do this the last time I ran SFC. I am going to after sending this and run SFC again and see if it changes anything regarding the
Secure Boot TPM-WMI error. If it does I'll post about it.
On 5/21/2026 12:30 PM, sticks wrote:
On 5/21/2026 6:10 AM, Philip Herlihy wrote:
I've seen a couple of references to SFC /scannow here occasionally.
That's the built-in utility to check whether there is any corruption in
your running Windows system, and (hopefully) fix it. It's an invaluable >>> maintenance tool and I use it regularly.
It was a long time before I realised that you should also check the
"component store" first, as that's what the SFC command uses as its
reference. (For years SFC didn't seem to fix anything - that was why). >>> You use the DISM utility to check that.
---snip---
Thanks, Philip.
I did not do this the last time I ran SFC. I am going to after
sending this and run SFC again and see if it changes anything
regarding the Secure Boot TPM-WMI error. If it does I'll post about it.
Your batch file worked nicely, thanks.
Running DISM I got the "Your system is repairable" message. It then did the repairs successfully.
I restarted next, and got the same 4 event viewer informative warnings
after I earlier ran SFC, not the TPM-WMI error, saying the system is
"The TPM was successfully provisioned and is now ready for use."
I then ran SFC and it reported no errors.
I then re-ran winston's powershell command and it again returned true.
Good to go....HA!
Have a look at this ... it covers just about everything:
https://www.stefanobordoni.cloud/projects/sys_minion/
I've been using it a few years.
On 5/21/2026 6:41 PM, Hank Rogers wrote:
---snip---
Have a look at this ... it covers just about everything:
https://www.stefanobordoni.cloud/projects/sys_minion/
I've been using it a few years.
And it's totally free! Looks like something I could really screw things
up properly with, though. Heh.
On 5/21/2026 12:30 PM, sticks wrote:
On 5/21/2026 6:10 AM, Philip Herlihy wrote:
I've seen a couple of references to SFC /scannow here occasionally.
That's the built-in utility to check whether there is any corruption in
your running Windows system, and (hopefully) fix it. It's an invaluable >>> maintenance tool and I use it regularly.
It was a long time before I realised that you should also check the
"component store" first, as that's what the SFC command uses as its
reference. (For years SFC didn't seem to fix anything - that was why). >>> You use the DISM utility to check that.
---snip---
Thanks, Philip.
I did not do this the last time I ran SFC. I am going to after
sending this and run SFC again and see if it changes anything
regarding the Secure Boot TPM-WMI error. If it does I'll post about it.
Your batch file worked nicely, thanks.
Running DISM I got the "Your system is repairable" message. It then did the repairs successfully.
I restarted next, and got the same 4 event viewer informative warnings
after I earlier ran SFC, not the TPM-WMI error, saying the system is
"The TPM was successfully provisioned and is now ready for use."
I then ran SFC and it reported no errors.
I then re-ran winston's powershell command and it again returned true.
Good to go....HA!
| Sysop: | Scott Duensing |
|---|---|
| Location: | Freeburg, IL, USA, Earth |
| Users: | 5 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 494354:34:41 |
| Calls: | 5 |
| Messages: | 20,594 |