Windows 10: SFC scan fails to repair files, returns error 160

The error log is below:2023-07-15 14:25:14, Info DEPLOY [Pnp] Corrupt file: C:\WINDOWS\System32\CIRCoInst.dll 2023-07-15 14:25:14, Error DEPLOY [Pnp] Failed repairing file: C:\WINDOWS\System32\CIRCoInst.dll: 160 2023-07-15 14:25:14, Info DEPLOY [Pnp] Corrupt file: C:\WINDOWS\System32\drivers\1394ohci.sys 2023-07-15 14:25:14, Error DEPLOY [Pnp] Failed repairing file: C:\WINDOWS\System32\drivers\1394ohci.sys: 160 2023-07-15 14:25:14, Info DEPLOY [Pnp] Corrupt file: C:\WINDOWS\System32\drivers\acpi.sys 2023-07-15 1

:)

 

sfc /scannow error repair

Hi,



Thank you for writing to Microsoft Community Forums.



We appreciate the efforts you have taken in trying to resolve this issue. I have analyzed the error logs that you have shared and I would suggest you follow the steps mentioned below:

1. Type Command Prompt in the
   search bar on the Taskbar.
   
2. Right click on the Command Prompt icon and select
   Run as administrator.
   
3. Now, paste the following command and hit Enter:
   DISM.exe /Online /Cleanup-image /Restorehealth
   
4. Once the DISM command is executed, we would suggest you to run sfc /scannow again.
   

If the integrity violations are not repaired after running sfc scan, the best option will be performing a repair installation. A repair installation will repair all the corrupted files.



Refer the steps mentioned below:



Download the Windows 10 Media Creation Tool (MCT) and use it to perform a repair installation
of Windows 10. We have a video that can show you how if you aren’t sure



Let us know the results.



Regards,

Nikhar Khare

Microsoft Community - Moderator

 

SFC Failed to repair corrupt files

I have run a SFC scan and it found corrupt files but failed to repair files. This is the log file details are

here.

 

Missing files after sfc scan

Two things to note.

The first is that the files reported as unrepairable in your CBS.log are all Powershell modules for Defender. This is a known bug in the Defender Platform Update and according to Microsoft should be ignored.

https://support.microsoft.com/en-us/...s-as-corrupted

The second is that when SFC reports it cannot repair a file it's usually because the copy of the file in the store is also damaged. The store can be repaired with the command:

dism /Online /Cleanup-image /Restorehealth


This, followed by another SFC /ScanNow will 'repair' the errors you found, but until MS fix their bug they will probably return with the next Defender Platform update.

For more on this see: sfc /scannow failing after this latest Defender Platfom update.