Fix sfc /scannow Reporting Errors That CBS.log Cannot Identify on Windows 11

When you run the System File Checker tool with the sfc /scannow command on Windows 11, it may report that it found corrupt files but cannot repair some of them. You then check the CBS.log file for details, but the log does not identify which files are corrupted or why the repair failed. This situation leaves you without a clear path to fix the underlying system file corruption. The root cause is often a corrupted Component-Based Servicing component store, a damaged hard drive, or a pending Windows Update that interferes with the repair process. This article explains why CBS.log may not show specific file names and provides step-by-step methods to resolve the issue and successfully repair system files.

Why CBS.log Does Not Identify Specific Corrupted Files After sfc /scannow

The Component-Based Servicing log located at C:\Windows\Logs\CBS\CBS.log records every operation performed by the Windows servicing stack including sfc. When sfc /scannow finds a corrupted file that it cannot repair, it logs a generic entry such as “Cannot repair member file” without specifying the file name or path. This happens because the corruption exists in the component manifest itself rather than in a single user-visible file. The manifest is the XML metadata that describes which files belong to a component and their expected hashes. If the manifest is damaged, sfc cannot match the corrupted file to its expected signature and therefore cannot report the file name.

A second common cause is a corrupted component store. The component store at C:\Windows\WinSxS holds all system file versions. When sfc /scannow tries to replace a damaged file, it pulls the replacement from this store. If the store itself contains corrupted or missing files, sfc fails and logs only a generic CBS error. In this scenario, the log entry may read “Failed to perform operation” with no file name. A third cause is hard drive errors. Bad sectors or file system corruption can prevent sfc from reading or writing files. In that case, the CBS.log may show access-denied or I/O errors without identifying the file.

Steps to Repair the Component Store and Fix sfc /scannow Errors

Before running any repair command, open an elevated Command Prompt. Press the Windows key, type cmd, right-click Command Prompt, and select Run as administrator. Click Yes on the User Account Control prompt.

1. Run DISM to repair the component store
   Type or paste the following command and press Enter: DISM /Online /Cleanup-Image /RestoreHealth. DISM uses Windows Update to download fresh system files from Microsoft servers. This process can take 15 to 30 minutes. Do not close the Command Prompt window while it runs. When the operation completes, DISM will report either “The restoration completed successfully” or “The component store corruption was repaired.” If DISM cannot contact Windows Update, proceed to the next step.
2. Use a Windows 11 installation media as the DISM source
   Insert a Windows 11 USB or DVD. Note the drive letter for the media, for example D:. Run the following command: DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim /LimitAccess. Replace D: with your actual media drive letter. The /LimitAccess switch prevents DISM from using Windows Update as a fallback. Wait for the command to finish. This method works when the local component store is damaged and Windows Update is unavailable.
3. Run chkdsk to check for hard drive errors
   Type chkdsk /f /r and press Enter. The system will prompt you to schedule the scan on the next restart. Type Y and press Enter. Restart your computer. The chkdsk utility runs before Windows loads and scans the file system and disk surface for errors. It can fix bad sectors and file system corruption that prevent sfc from writing repaired files. After chkdsk completes, Windows boots normally.
4. Run sfc /scannow again
   After completing steps 1 through 3, run sfc /scannow in the elevated Command Prompt. The scan now uses a repaired component store and a healthy disk. Sfc should report either “Windows Resource Protection did not find any integrity violations” or “Windows Resource Protection found corrupt files and successfully repaired them.” If sfc still reports errors, proceed to the next section.

If sfc /scannow Still Reports Unidentified Errors After the Main Fix

sfc /scannow fails with “Windows Resource Protection could not perform the requested operation”

This error indicates that a Windows service required by sfc is not running. Open the Services console by pressing Windows + R, typing services.msc, and pressing Enter. Locate the Windows Modules Installer service. Right-click it and select Start if it is not running. Set its Startup type to Manual. Then run sfc /scannow again.

sfc /scannow reports errors but CBS.log still shows no file names

In rare cases, the component manifest corruption is too deep for DISM to repair. You can extract the CBS.log to a text file and search for specific error codes. Run the following command: findstr /C:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfc_errors.txt". Open the file sfc_errors.txt on your desktop. Look for lines containing “0x800f0900” or “0x800f081f”. Error 0x800f0900 means the component store is corrupted beyond DISM repair. Error 0x800f081f means the source files are missing. For these errors, the only reliable fix is a Windows 11 repair installation using the Keep personal files and apps option. Boot from a Windows 11 installation media, select Repair your computer, then Troubleshoot > Reset this PC > Keep my files. This replaces all system files without removing your data or installed programs.

sfc /scannow runs but never finishes or hangs

A hung sfc scan is often caused by a pending Windows Update that is stuck. Open the Settings app, go to Windows Update, and click Check for updates. Install any pending updates. If an update fails to install, run the Windows Update Troubleshooter from Settings > System > Troubleshoot > Other troubleshooters. After resolving the update issue, restart your computer and run sfc /scannow again.

Item	DISM /RestoreHealth	sfc /scannow
Purpose	Repairs the component store and servicing stack	Scans and replaces corrupted system files
Source of replacement files	Windows Update or a local install.wim	The local component store at WinSxS
Log file location	C:\Windows\Logs\DISM\dism.log	C:\Windows\Logs\CBS\CBS.log
Common error when store is damaged	0x800f0900 or 0x800f081f	Generic “Cannot repair member file” without file name
Recommended order to run	First	Second, after DISM completes

When sfc /scannow reports errors that CBS.log cannot identify, the problem is almost always a corrupted component store or hard drive errors rather than individual file corruption. Running DISM with a local installation media source and chkdsk before sfc resolves the majority of these cases. If the issue persists, a repair installation of Windows 11 using the Keep personal files option is the definitive fix. Remember to always run these commands from an elevated Command Prompt and to back up important data before performing a repair installation.