The sfc /scannow command checks protected Windows system files and attempts to replace damaged versions. It does not recover a deleted spreadsheet or repair a failing drive. On a stable Windows 10 or 11 PC, Microsoft recommends preparing the component source with DISM, then running SFC from an administrator Command Prompt. Wait for the final message before deciding what to do next. If personal files are already missing or the storage device is unstable, protect those files and assess the hardware before running repair commands that write to the system.
What SFC checks—and what its result cannot prove
System File Checker, usually called SFC, verifies protected operating-system files. When it finds certain damaged or missing files, it attempts to replace them using Windows’ repair source. This can help when Windows components behave unexpectedly because protected files are corrupt. It is not a general fix for every slow PC, driver crash, damaged document, or disconnected USB device. The same symptom can have several causes, so record the error and when it occurs before assuming SFC is the answer.
DISM serves a different role. The online RestoreHealth operation can repair the Windows component store that supplies servicing files. Microsoft recommends running it before SFC in its System File Checker instructions. Both operations can modify Windows components. They do not replace a backup and do not repair physical storage. A successful integrity scan also does not establish that every personal file or third-party application is intact.
If you can open Windows and documents normally, copy important work to a separate healthy backup and open several copies before proceeding. If the PC cannot enter Windows, this online procedure does not apply as written. Recovery Environment drive letters and offline Windows paths can differ from normal Windows; do not copy an online command or a stranger’s C: path into an offline session. Use the correct documented offline procedure or seek qualified help after protecting the files.
Before repair, distinguish missing files from system symptoms
A document missing after a crash requires a search of its original folder, Recycle Bin, cloud versions, and existing backups. SFC is not a personal-document undelete tool. If the only copy may still be on the affected device, stop installing software or saving new files to that source. Repeated disconnects, clicking, wrong capacity, or severe read errors are additional reasons to stop direct scanning and ask about imaging or professional recovery. Running DISM or SFC repeatedly on unstable hardware can add activity without addressing the failure.
For genuinely deleted or inaccessible local files on a stable source recognized by Windows, Drecov can search the original location in read-only recovery mode. Quick Scan, Deep Scan, filters, and previews help identify candidate documents, photos, or other supported files. It also offers Lost Partition Recovery when a partition is actually missing. Drecov does not replace Windows system files, fix the component store, or repair physical damage. The file recovery overview covers the separate file-loss task.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
Step 1: choose the original stable location
Prepare another healthy drive for recovered files. Do not install Drecov on the partition that held the missing documents. If the affected PC cannot start Windows, a separate working Windows PC must be able to read the source safely. Have a technician connect the drive if removal is unfamiliar; encrypted volumes also require authorized access and any necessary BitLocker recovery key. Open Drecov on the working PC and select the original volume or folder. Stop if the source clicks or disconnects repeatedly; ask about imaging or professional recovery instead.
Step 2: search for the actual work
Run Quick Scan first. Look for the original user folder and filter by file type, name, path, or date when useful. If the target is absent and the source remains stable, run Deep Scan. Preview representative supported documents or images. A preview can identify a likely file but cannot prove every page or linked project asset is complete. Keep several plausible versions if the original names have disappeared.
Step 3: restore elsewhere and verify
Save selected results to the separate healthy drive, never back to the source. Check Drecov Folder or Recovery Folder if they are not in the expected output location. Open sample documents and compare their content with backups. Only after the needed files are protected should you proceed to DISM, SFC, reset, or other changes. A recovered filename is not a substitute for a successful open test.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
Run the online DISM and SFC sequence
This route assumes you can sign in to the Windows installation you want to repair, have administrator permission, and the storage is stable. Save your work and connect a laptop to power. Search for Command Prompt, right-click it, and choose “Run as administrator.” Approve the Windows prompt if authorized. On a work-managed PC, follow your organization’s support policy rather than changing servicing settings without permission.
Enter DISM.exe /Online /Cleanup-image /Restorehealth and press Enter. The spaces before the switches matter. This command targets the running Windows image and attempts to repair its component store; it is not a command for an arbitrary external disk. Let it finish and read the final result. DISM may use Windows Update as a repair source. If it reports that source files cannot be found, record the exact code and use a matching, documented source through an appropriate administrator. Do not invent a source path from an example.
After DISM reports success, enter sfc /scannow in the same elevated window. There is a space between sfc and /scannow. Leave the window open until verification reaches 100% and the result appears. Copy or photograph the final message. Do not judge success from a temporary percentage or from a window that closed before the result. When a restart is requested or appropriate, restart normally and retest the Windows feature that prompted the scan.
Read the final message before choosing another fix
No integrity violations were found
SFC did not report a problem among the protected files it checked. That is useful, but it does not prove the whole computer is healthy. If an application still fails, investigate its own error, driver, settings, or hardware evidence. A missing personal document still needs the file-search or recovery path above. Repeating SFC without new information is unlikely to explain an unrelated USB or application problem.
Corrupt files were found and repaired
Record the message, restart if needed, and repeat the original safe action that failed. Open the affected Windows feature or application and observe whether the same error returns. Successful system-file repair does not certify every personal document. If the symptom persists, note whether it is identical, occurs at a different stage, or now shows a new code. That distinction helps select a targeted next step instead of immediately resetting Windows.
Files were found but some could not be fixed
Do not download replacement system files from unofficial sites. Review the DISM result and the time of the SFC run; servicing logs may contain details for an administrator. Microsoft describes how to examine CBS.log in its instructions. A matching official repair source or supported repair option may be needed. Back up and verify personal files before a repair installation, reset, or reinstall. Avoid manually taking ownership of system files unless you understand the exact supported procedure and its risks.
The scan could not run or the repair service did not start
These messages describe failures at different stages. A scan that cannot perform the requested operation needs its own diagnosis; Microsoft suggests Safe Mode for that result. When Windows says it could not start the repair service, the repair-service guide focuses on Windows Modules Installer. Do not assume either message means the drive should be formatted. Capture the exact wording and stop if storage symptoms indicate hardware instability.
Make the result useful to the next person
Write down your Windows version, the original symptom, the final DISM and SFC messages, and whether the problem changed after a restart. Include the time of the scan if a technician needs to locate the relevant log entries. Avoid pasting private document paths or account information into a public forum. On a company computer, give the details to the administrator rather than changing repair sources or service policies yourself.
If the PC now runs normally, keep the separate backup and confirm that the affected feature still works after ordinary use. If it does not, use the observed error to choose the next investigation. The separate guide to reinstalling Windows with files in mind addresses a more invasive path, not a mandatory next step after every SFC scan. A repair that reports no integrity violations can still be valuable: it narrows one part of the problem.
Conclusion
System File Checker examines protected Windows files; it is not a universal data-recovery or hardware-repair command. On a stable, accessible system, use Microsoft’s DISM-then-SFC sequence and read the completed result. Protect personal files before more invasive repair. If those files are actually missing from stable storage, Drecov can search their original location and save candidates to another healthy device for verification. Let the result, not the urge to run another command, determine the next step.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
