To check and repair Windows system files, use the Benchmark and Diagnostics tab in S.A.K. Utility: on the Diagnostics sub-tab, click Verify System Files under System Maintenance, then confirm. It runs Windows' System File Checker (SFC), then Windows' image repair tool (DISM), and repairs what it can.
When to use this
Use this when Windows behaves strangely: built-in programs crash, updates fail, or features stop working after a bad shutdown or a malware cleanup.
What you need
- Administrator rights. If the app is not already running as administrator, Windows asks for approval when the run starts. The app does not need to restart.
- Time. It usually takes a while, and a single run stops at 60 minutes.
- No internet connection. The repair step only uses files already on the PC, and does not fetch anything from Windows Update.
Steps
Open the Benchmark and Diagnostics tab.
Click the Diagnostics sub-tab.
Turn on the Log switch at the bottom of the tab. The result text appears there.
Under System Maintenance, click Verify System Files.
Read the question, then click Yes. It warns that the tools can modify Windows system files.
The app always asks before this one runs Approve the Windows prompt if one appears.
Wait. A progress bar appears under the buttons. During DISM's scan, the status bar shows how far it has got, such as DISM: Scanning component store... 42.0%.
Read the result in the log and the status bar.
The status bar starts with Completed or Failed
What the result means
The status bar starts with Completed: Verify System Files when both tools finished and nothing was left broken, and with Result unknown: Verify System Files when SFC gave an answer the app could not read, or when SFC passed but DISM's scan ran out of time. Otherwise it starts with Failed: Verify System Files. The log gives one line for each tool, then the details, including where Windows keeps its own record of the run, CBS.log.
SFC:
- SFC found no integrity violations. The protected files are fine.
- SFC found and repaired corrupt files. Restart the PC.
- SFC found corrupt files but could not repair them. Run it again after DISM has repaired its files.
- SFC finished, but this check can only read its result in English. The app understands SFC's English wording only, so on a non-English Windows you see SFC's own words here, in your language. Read them: this is not a failure, and it is not a pass either. If DISM could not finish as well, the run counts as failed.
- SFC did not complete a verification run. It said: followed by SFC's last lines. SFC ran into something, such as a pending restart or could not perform the requested operation, and this is not proof that Windows is damaged.
- SFC did not complete a verification run. SFC could not be started or said nothing.
DISM:
- DISM found no issues. The repair source is healthy.
- DISM repaired component store issues. Run the tool again so SFC can use the repaired files.
- DISM found damage in the component store and could not repair it from this PC. DISM's own error follows DISM said:. A repair needs a source, such as Windows Update or a Windows ISO of the same version.
- DISM did not finish its component store scan in 30 min, so this check is incomplete. Nothing was found and nothing was proved. Run it again when the PC can be left longer. The minutes can be fewer when SFC took a long time, because the whole run stops at 60 minutes.
- DISM did not complete a component store assessment. DISM could not be started, or stopped without an answer the app could read. You can try
DISM /Online /Cleanup-Image /RestoreHealthyourself from an administrator Command Prompt on a connected PC.
How it works
SFC compares protected Windows files with the known-good copies Windows keeps, called the component store, and replaces any that are wrong.
DISM then checks the component store itself. It runs a quick check and a deeper scan. If either finds corruption, it attempts a repair using files on this PC. Because SFC runs first, it cannot benefit from a DISM repair in the same run.
Good to know
This can change Windows system files, and there is no undo. Back up important files first if the PC is unstable.
- Time limit: a run cut off at 60 minutes adds Stopped at the 60-minute limit for one verification run to its result.
- No Cancel button: the other tools on the tab are locked while it runs. If you close the app, it asks you first.
- Declined prompt: if you decline the Windows prompt, the run fails with Administrator privileges required but not granted. Nothing has changed.
- Log file: the same messages are saved to
quick_actions.login thedata\logsfolder besidesak_utility.exe.