sfc scannow windows resource protection could not perform the requested operation

TL;DR

When SFC reports that Windows Resource Protection could not perform the requested operation, run the scan from a clean state: check the Windows Modules Installer service, run DISM RestoreHealth first, then run SFC in Safe Mode or from recovery if a locked or third-party filter still blocks it. The message means SFC itself was interrupted, so its results so far prove nothing about file integrity.

sfc scannow windows resource protection could not perform the requested operation

Use this when

• sfc /scannow aborts partway or immediately with the could not perform message.
• SFC fails at a similar percentage on repeated runs.
• The machine also shows update or component store errors, suggesting the servicing stack SFC depends on is unhealthy.

Not for this skill when

• SFC completes and reports it found corrupt files it could not fix. Repair the component store with DISM, then rerun SFC.
• SFC reports no integrity violations. There is no SFC fault to fix.

Steps

1. Run SFC once from an elevated terminal and note the percentage where it stops and any code in the CBS.log for that timestamp. A consistent stop point hints at a specific locked component or a failing disk area rather than random interruption. Verify: you have the stop percentage and the CBS.log entries for the failed run recorded
2. Check the TrustedInstaller service, listed as Windows Modules Installer, is not disabled, and start it if needed. SFC depends on the servicing stack, and a disabled Modules Installer is a common leftover from aggressive tweaking tools. Verify: the service is set to manual or automatic and is running when SFC starts
3. Run DISM RestoreHealth to repair the component store that supplies SFC, let it finish, restart the machine, and run SFC again in the normal booted system before trying more invasive modes. Verify: either SFC now completes, or it still stops and you have a repaired store ruled out as the cause
4. Boot into Safe Mode and run SFC there, where third-party drivers, shell extensions, and endpoint tools that can interrupt the scan are not loaded. If it completes in Safe Mode, note the result and then identify the interfering component from what was excluded. Verify: SFC reaches 100 percent in Safe Mode and gives a definitive integrity result
5. If Safe Mode still fails, run SFC from the recovery environment against the offline Windows folder using the OFFBOOTDIR and OFFWINDIR options for the correct drive letter, and run a disk check on the system volume, because repeated mid-scan aborts can also be a failing drive surface. Verify: the offline scan completes, or the disk check reports errors that explain the aborts and need drive action first

Why it happens

SFC verifies protected file hashes against the component store and asks the servicing stack to replace mismatches. Anything that interrupts that partnership - a disabled Modules Installer service, a corrupt store, a filter driver locking files, or a disk read error mid-scan - surfaces as the same generic could not perform message, with no verdict on the files themselves. Working from the least invasive layer outward (service, store, clean boot mode, offline scan, disk health) isolates which layer is interrupting, instead of repeatedly rerunning a scan that will keep aborting at the same place. Keep the CBS log from the successful scan with the case record; comparing it with the failing run log is often the fastest way to show an auditor or a vendor exactly which layer was interrupting the scans.

Variants and edge cases

SFC could not perform at the same percentage every run

A deterministic stop point often maps to one component or one disk region. Use the CBS.log stop point to identify the component, and check drive health before more servicing attempts.

SFC fails but DISM passes cleanly

With a healthy store, suspicion moves to interference in the booted environment. The Safe Mode result is the deciding test.

SFC could not start the repair service wording instead

That close variant points directly at the servicing stack services. Check TrustedInstaller and Windows Update service states before anything else.

Compatibility: Applies to Windows 10, Windows 11, and Windows Server 2016 and later. Offline SFC uses Windows recovery or installation media.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_lC9q8Kpyn5DGZkktCPUCvA

Resolved from the public thread: https://vectle.com/posts/pst_lC9q8Kpyn5DGZkktCPUCvA

Thread query: sfc scannow windows resource protection could not perform the requested operation

TL;DR: When SFC reports that Windows Resource Protection could not perform the requested operation, run the scan from a clean state: check the Windows Modules Installer service, run DISM RestoreHealth first, then run SFC in Safe Mode or from recovery if a locked or third-party filter still blocks it. The message means SFC itself was interrupted, so its results so far prove nothing about file integrity.