Turkey (Turkish)
Germany (German)
Worldwide (English)
Microsoft specifically recommends rerunning SFC in Safe Mode for this result.
Halkali merkez neighborhood fatih st ozgur apt no 46 , Kucukcekmece , Istanbul , 34303 , TR
Diagnose the SFC requested operation error using Safe Mode, WinSxS Temp, DISM, CBS logs and offline SFC.
Microsoft specifically recommends rerunning SFC in Safe Mode for this result.
Microsoft also says to ensure PendingDeletes and PendingRenames exist under %WinDir%\WinSxS\Temp.
SFC validates live files protected by Windows Resource Protection. DISM services the Windows image/component store. If the component store is damaged, SFC's source for clean copies may also be compromised.
Therefore, simply repeating SFC is limited. Separate file-lock/service effects, WinSxS servicing state, component-store damage and filesystem issues.
Microsoft's support page explicitly recommends Safe Mode for this result. Safe Mode reduces third-party services and drivers, which can remove certain file locks and hooks.
If SFC succeeds in Safe Mode, a normal-startup service or driver becomes a stronger suspect. If it fails there too, component store, filesystem or pending servicing state becomes more likely.
sfc /scannowMicrosoft says to ensure the `PendingDeletes` and `PendingRenames` folders exist under `%WinDir%\WinSxS\Temp`. A broken servicing state around these paths can contribute to SFC failing its requested operation.
Do not download replacement folders from the internet. Inspect the local structure and permissions; random ownership or ACL changes can further damage servicing security.
dir %windir%\WinSxS\Tempicacls %windir%\WinSxS\Temp`DISM /Online /Cleanup-Image /ScanHealth` checks the component store. If RestoreHealth fails with a source error such as 0x800f081f, focus on the repair source rather than looping SFC.
DISM /Online /Cleanup-Image /CheckHealthDISM /Online /Cleanup-Image /ScanHealthDISM /Online /Cleanup-Image /RestoreHealthThe SFC console summary lacks detail. Microsoft documents extracting `[SR]` entries from CBS.log with `findstr` so you can see specific files and repeated repair failures.
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt"From WinRE, SFC can target an offline Windows installation. Do not assume C: for `/offbootdir` and `/offwindir`; Windows may be D: or another letter in WinRE.
Verify the real directory first. If the volume is BitLocker-locked, solve volume access before offline SFC.
dir D:\Windows\System32sfc /scannow /offbootdir=D:\ /offwindir=D:\WindowsDo not use destructive boot, BitLocker, firmware, partition or storage commands without backups and a rollback plan. Never copy example drive letters without verification.
Do not loop the same result indefinitely; move to Safe Mode, DISM/component store and CBS logs.
SFC validates and repairs protected Windows system files; it is not a personal-file cleanup tool.
For boot, storage, RDP or update problems on a Windows VPS or physical server, send the exact error code, Windows version and console screenshot to technical support.