我们已经看到系统文件检查器(System File Checker)如何允许用户扫描和恢复损坏的Windows系统文件。我们还看到了如何运行系统文件检查器(System File Checker)等等，更早。但是，如果在运行结束时您看到以下消息怎么办？
Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log.
这条消息的意思是，虽然系统文件检查器(System File Checker)完成了扫描并发现了损坏的系统文件，但它无法继续并用好的系统文件替换它们。
Windows 资源保护(Windows Resource Protection)保护注册表项和文件夹以及关键系统文件。如果检测到受保护的系统文件有任何更改，修改后的文件将从位于Windows文件夹本身的缓存副本中恢复。
Windows 资源保护(Windows Resource Protection)发现损坏的文件，但无法修复其中一些
如果您收到此消息并且系统文件检查器(System File Checker)在您运行时无法完成工作，您可以尝试以下操作。
- 在安全模式下运行 SFC
- 在引导时运行 SFC
- 使用 DISM
- 尝试重置此电脑或重新开始
- 检查日志文件
您需要管理员权限才能执行这些建议。
1]在安全模式下运行SFC
启动进入安全模式(Safe Mode)。打开提升的命令提示符窗口，键入sfc/scannow, 然后按 Enter 键。
只需确保PendingDeletes和PendingRenames文件夹存在于%WinDir%\WinSxS\Temp下。如果某些启动程序产生问题，这可能会有所帮助。
2]在启动时运行SFC
如果您愿意或需要，您可以在Boot Time运行(Boot Time)System File Checker。这是一个可以帮助您的选项，因为它将在Windows加载之前运行系统文件检查器。(System File Checker)
转到此处了解如何在启动时运行 sfc /scannow。看看这是否有帮助。
3]使用DISM
使用DISM。打开提升的命令提示符并运行以下命令并按Enter：
Dism /Online /Cleanup-Image /RestoreHealth
此命令检查组件存储损坏(component store corruption)、记录损坏并修复(FIXES)损坏。不过可能需要一段时间！如果系统文件检查器不工作(System File Checker is not working)时很有用。
4]尝试重置此PC或重新开始
在Windows 11/10上，尝试重置此电脑(Reset This PC)或 重新开始(Fresh Start)。在Windows 8.1上，执行刷新或重置操作。如果您认为自动修复(Automatic Repair)适用于您的情况，您也可以考虑使用自动修复。在Windows 7上，按照您认为最适合您的情况执行启动修复(Startup Repair)或修复安装(Repair Install)或就地升级。
要在Windows 7或Windows Vista中执行就地升级(In-place upgrade)，请备份您的文档，关闭所有打开的应用程序，然后将Windows DVD插入DVD驱动器。在设置(Setup)窗口中，单击立即安装(Install Now)。单击联机以获取最新的安装更新（推荐）。(Go online to obtain the latest updates for installation (recommended).)如果系统提示您执行此操作，请键入 CD 密钥。接下来，在“安装 Windows(Install Windows) ”页面上选择要升级或就地(In-place)升级的操作系统，然后单击“是”(Yes)接受Microsoft 软件许可(Microsoft Software License)条款。下一步点击升级(Upgrade)当被问及您想要哪种类型的安装时(Which type of installation do you want)。该过程完成后，重新启动您的PC。
5]检查日志文件
您可能还需要考虑此选项。打开CBS.log文件并查看损坏文件的详细信息并(CBS.log)手动(manually)将损坏的文件替换为已知良好的副本。导航到C:\Windows\Logs\CBS，您将能够看到并打开SBS.log 文件(SBS.log file)。
检查它是否显示一些错误或消息。这可能会给你一个继续前进的方向。您可以在KB929833(KB929833)中获得有关如何手动执行此操作的更多详细信息。
我希望对你有所帮助。
如何修复损坏的CBS日志文件？
如果CBS日志文件损坏，您实际上无能为力。最好的方法是删除它，然后在需要时让Windows重新创建它。(Windows)
如何修复SFC Scannow中损坏的文件？
要修复SFC Scannow(SFC Scannow)无法修复的损坏文件，您需要运行DISM 工具(DISM Tool)或使用重置(Reset)此 PC 选项。那肯定会帮助你。
我可以恢复损坏的文件吗？
由于它已经损坏，因此您无能为力。您唯一应该做的就是找出导致损坏的原因，然后再次收集日志。如果有的话，那么SFC命令可能会有所帮助，但不能保证它。
是什么导致文件损坏？
很难确定一个原因，但它可能是软件和硬件问题。如果收集的数据被另一个程序重叠，那么它可能会损坏软件。硬件(Hardware)损坏通常发生在旧数据上，但如果您在多个地方看到它，则需要检查您的设备。
这些链接可能会让你们中的一些人感兴趣：(These links may interest some of you:)
- 系统文件检查器 SFC 不起作用或无法修复损坏的成员文件(System File Checker SFC not working or cannot repair corrupted member file)
- Windows 资源保护无法启动修复服务(Windows Resource Protection could not start the repair service)
- Windows 资源保护无法执行请求的操作
- 在外部驱动器上运行 sfc /scannow 系统文件检查器。
Windows Resource Protection found corrupt files but was unable to fix some of them
We hаve already seen how thе System File Checker allows users to scan for and restore corrupt Windows system files. We have also seen how to run System File Checker and more, earlier. But what if at the end of the run you see the following message?
Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log.
What this message says is that although the System File Checker completed the scan and found corrupted system files, it was unable to proceed and replace them with good system files.
The Windows Resource Protection protects registry keys and folders as well as critical system files. If any changes are detected to a protected system file, the modified file is restored from a cached copy located in the Windows folder itself.
Windows Resource Protection found corrupt files but was unable to fix some of them
If you receive this message and the System File Checker is not able to do its job when you run it, here are a few things you can try.
- Run SFC at Safe Mode
- Run SFC at Boot-Time
- Use DISM
- Try Reset This PC or Fresh Start
- Check the Log files
You will need admin permission to execute these suggestions.
1] Run SFC in Safe Mode
Boot into Safe Mode. Open an elevated command prompt window, type sfc/scannow, and press the Enter key.
Just make sure that the PendingDeletes and PendingRenames folders exist under %WinDir%\WinSxS\Temp. This may help if some start-up programs are creating a problem.
2] Run SFC at Boot Time
If you wish to or need to, you may run System File Checker at Boot Time. This is one option that may help you as it will run System File Checker before Windows loads.
Go here to learn how to run sfc /scannow at Boot Time. See if this helps.
3] Use DISM
Use DISM. Open an elevated command prompt and run the following command and hit Enter:
Dism /Online /Cleanup-Image /RestoreHealth
This command checks for component store corruption, records the corruption, and FIXES the corruption. It may take a while though! Useful if System File Checker is not working.
4] Try Reset This PC or Fresh Start
On Windows 11/10, try Reset This PC or Fresh Start. On Windows 8.1, carry out a Refresh or a Reset operation. An Automatic Repair is also an option you may want to consider if you think it applies in your situation. On Windows 7, carry out a Startup Repair or Repair Install or an In-place Upgrade as you think may best suit your situation.
To perform an In-place upgrade in Windows 7 or Windows Vista, back up your documents, close all open applications, and then insert the Windows DVD in the DVD drive. In the Setup window, click Install Now. Click Go online to obtain the latest updates for installation (recommended). Type the CD key if you are prompted to do this. Next, select the operating system on the Install Windows page you want to Upgrade or In-place and click Yes to accept the Microsoft Software License Terms. Next click Upgrade when asked Which type of installation do you want. Once the process is completed, restart your PC.
5] Check the Log files
You may also want to consider this option. Open the CBS.log file and view details of the corrupted files and replace the corrupted file with a known good copy manually. Navigate to C:\Windows\Logs\CBS you will be able to see and open the SBS.log file.
Check if it shows some errors or a message. That may give you a direction to proceed. You can get more details on how to do this manually, here at KB929833.
I hope something helps you.
How do I fix a corrupted CBS log file?
If the CBS log file is corrupted there is actually nothing else you can do. The best way would be to delete it and then ret Windows recreate it when the need arises.
How do I fix corrupted files in SFC Scannow?
To fix corrupted files that SFC Scannow cannot fix, you need to run the DISM Tool or use the Reset This PC option. That is sure to help you.
Can I recover corrupt files?
Since it is already corrupted, there is not much you can do about it. The only thing you should do is find what is causing the corruption and then collect the log again. If at all, then the SFC command may help, but then there is no guarantee about it.
What causes files to corrupt?
It is difficult to pinpoint one reason, but it can be both software and hardware problem. If the data that is collected gets overlapped by another program, then it can corrupt the software. Hardware corruption usually happens on old data, but if you are seeing it in more than one place, you need to check your device.
These links may interest some of you:
- System File Checker SFC not working or cannot repair corrupted member file
- Windows Resource Protection could not start the repair service
- Windows Resource Protection could not perform the requested operation
- Run sfc /scannow System File Checker on External Drives.
