Windows Resource Protection could not perform the requested operation.Īn unknown issue occurred and the scan could not be performed.

No missing or corrupted system files were detected, meaning your system’s integrity is intact. Windows Resource Protection did not find any integrity violations. Let us now see all the possible outputs of the SFC scan that different users can encounter and what they mean: Output Statement It then also states the location of a CBS.log file which contains the details of the performed scan – we’ll get into that a moment later. Outputs of SFC ScanĪs you can observe in the image above, the output of the SFC scan states the following: Windows Resource Protection found corrupted files and successfully repaired them. However, that is not always the case, and users may encounter different errors from time to time.īefore we discuss these different errors, let us discuss the various outputs of the basic scan and what each of those means. The cmdlet will then perform its job and attempt to repair any protected files that may have been corrupted. The simplest (and most convenient) method to run the system file checker command is by running the following cmdlet in an elevated Command Prompt window: sfc /scannow Running basic SFC scan Today, we are only going to be focusing on the “sfc /scannow” cmdlet as it is the one that quickly and effectively fixes your operating system. Set the cache size of the Windows File Protection to X MBs. Will remove the Windows File Protection cache and begin a scan over the system files. Revert the scanning functionality to its original (default) state.

If found, replace the file from the DLL cache.

The table below lists all the switches which can be used with the SFC command-line tool, and their functions: Commands How to Fix 'Windows Resource Protection Could Not Start The Repair Service'.Log In From Built-In Administrator Account.

Sfc command