[Fixed] Windows Resource Protection found corrupted files but was unable to fix some of them

Error: Windows Resource Protection found corrupted files

"Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log file, such as C:\Windows\Logs\CBS\CBS.log."

"Windows Resource Protection found corrupt files but was unable to fix some of them" is one of the most common errors you might encounter when running the System File Checker tool (SFC) and using the sfc/scannow command to repair missing or corrupted system files, indicating that the SFC/scannow failed, and you might need to fix the damaged files manually.

A quick overview of the methods to fix the issue "Windows Resource Protection found corrupt files but was unable to fix some of them":

Please provide the English content you want translated, and I will do my best to translate it into Chinese.

Regarding the Windows Resource Protection System File Checker

In the Windows operating system, System File Checker (sfc.exe) is integrated with Windows Resource Protection to safeguard registry keys and folders along with critical system files. Users can invoke the sfc utility through the Windows Command Prompt. The command `sfc /scannow` is used to scan all protected system files, and if issues are found, it attempts to replace problematic files with cached copies from the compressed folder located at %WinDir%\System32\dllcache\.

Ideally, running the sfc /scannow command would automatically fix corrupted system files for us, but this isn't the case when the file is not in the DLL cache or is damaged. In this case, sfc /scannow will return an error stating “Windows Resource Protection found corrupt files but was unable to fix some of them.”

There is no need to panic: when you encounter these problems, there are practical steps you can take to address them.

Read more: SFC SCANNOW Stuck

Found 5 solutions to fix Windows Resource Protection and discovered some corrupted files, but unable to repair some of them.

There are a few known common scenarios that might cause the System File Checker to be disabled and display the “Windows Resource Protection found corrupt files but was unable to fix some of them” error message. The following general troubleshooting procedures should help resolve this issue promptly.

Solution 1: Check and fix the hard drive

If you encounter hard drive issues, you may come across the problem of "sfc scannow found corrupt files but was unable to fix some files". First, check and repair any possible errors and bad sectors on the hard drive. To do this, you can easily accomplish it with a free partition manager - AOMEI Partition Assistant Standard. With its "Check File System" feature, you can check and fix hard drive partition errors with just one click.

Aside from the hard drive recovery, Partition Master also provides an all-in-one solution for disk partitioning, such as resize and move partition to solve the low disk space issue, clone disk, merge partition, create/delete/format partition, wipe data, and convert disk/partition (like convert FAT32 to NTFS) and more, all for free.

Download this powerful disk management tool, and then follow the steps below to fix your hard drive and address the “Windows Resource Protection found corrupt files” issue.

Step 1: Right-click the problematic partition.

Step 2: Select Advanced > Check File System.

Step 3: Confirm that you want to hide the partition.

Click “Start” to begin checking for disk partition errors.

If you don't want to use a third-party repair tool, you can scan and fix damaged files from the Command Prompt with chkdsk.

1. Hold down the ⊞ Win key, then type `cmd`. Right-click Command Prompt and select "Run as administrator." 2. Type the following command: `chkdsk E: /f /r` (where E is the letter of your target drive).

Fix 2: Run the DISM command to repair corrupted files

If Windows Resource Protection finds corrupted files but is unable to fix some of them, you can use the Deployment Image Servicing and Management (DISM) tool to repair the Windows image.

While SFC scans and replaces corrupted files with a potentially corrupted local store copy, DISM uses the Windows Update component to do the job. As such, you need to ensure that you have a stable Internet connection before running the scan.

The RestoreHealth command in DISM scans for any corruption in the Windows image and automatically performs the necessary repairs. Here are the steps you can follow.

1. Press the Windows key + R to open the "Run" dialog box. Type cmd, then hold down Ctrl+Shift and press Enter to open Command Prompt with administrator privileges.

Step 2: Type the following command, and then press Enter. This command checks for and records corruption in the component store, and then repairs it.

The command dism /Online /Cleanup-Image /RestoreHealth translates to: DISM /Online /Cleanup-Image /RestoreHealth This command is used in the Windows operating system to repair the integrity of the system image. It employs the System File Checker (SFC) to scan and fix system files, ensuring the health of the system files.

Or, if you're in the Windows DVD/USB repair mode, use this command:

Here are the command-line arguments to repair a Windows image using the DISM tool: Dism /Image:C:\ /Cleanup-Image /RestoreHealth This command means: Apply the Deployment Image Servicing and Management (DISM) tool to the Windows image located at C:\, executing a cleanup operation to restore its health. This is typically used to repair system files or address update issues. Make sure to replace "C:\\" with the actual path of the Windows image.

This may take a while, depending on your computer's specifications. When it's finished, you'll receive a message stating that the corruption was fixed. Restart your computer and run the SFC scan with administrative privileges at startup to see if the problem is resolved.

If you still see the “Windows Resource Protection found corrupt files but was unable to fix some of them” message, proceed to the next method.

Don't hesitate to share detailed guides to help your friends or other users who run into the same problem.

Fix 3: Run SFC/DISM scan in Safe Mode

If the above solutions don't work, run the SFC command in Safe Mode. This can help you avoid the “Windows Resource Protection found corrupt files but was unable to fix some of them” error caused by third-party apps.

In Safe Mode or with a Clean Boot, only the basic system programs and services start up. This will help us determine if a third-party app, driver, service, or startup item is interfering with the SFC scan. Here's a quick guide on running SFC in Safe Mode.

Step 1: Press the Windows key + R to open the "Run" dialog box. Type in msconfig and press Enter to open the "System Configuration" screen.

Step 2: Go to the General tab and selectSelective startup. Under Selective startup, uncheck Load startup items.

3. Next, click on the “Services” tab and check the box that says “Hide all Microsoft services.” Then, click “Disable all” to prevent any third-party services from running on the next startup. Click “Apply” and then restart your computer.

Step 4: After restarting your computer in a clean boot state, press the Windows key + R to open another Run dialog box. Then, open Command Prompt and run SFC or DISM again by typing the following commands:

DISM Command-Line Options:

The command in American English is: DISM.exe /Online /Cleanup-Image /RestoreHealth Its Chinese translation is: DISM.exe /在线 /清理映像 /恢复健康状态 This command is used to fix the Windows system image by scanning and fixing system files, making sure the system image is in good condition.

SFC command line:

sfc /scannow This is a command in the Windows operating system used to run the System File Checker tool. It scans the system's system files and checks for any corrupted or missing files. If issues are found, it attempts to repair them.

If Windows Resource Protection finds and successfully repairs corrupted files while in Safe Mode, this indicates that the issue might be caused by a software conflict.

Read more: There is a system repair pending sfc scannow

Fix 4: Run SFC from the Windows Recovery Environment (WinRE)

Another way to fix the issue with Windows Resource Protection finding corrupted files but unable to fix some of them is to run the SFC utility in the Windows Recovery Environment (WinRE).

Step 1. Boot from your Windows installation DVD.

Step 2: Choose "Repair your computer."

Step 3: Select the target system.

Step 4: In the Recovery Tools window, select Command Prompt.

Step 5. Type sfc /scannow in the Command Prompt window and press Enter.

If SFC /scannow finds corrupted files but is unable to fix some of them, proceed to the final method below to replace all Windows components and resolve the issue.

Fix 5: Perform a Windows 10 Repair Upgrade

The last resort to fix Windows Resource Protection found corrupt files but was unable to fix some of them on Windows 10 is to perform a Windows 10 Repair Upgrade.

A "Clean/Repair Install" will overwrite everything on the Windows installation drive, meaning you'll lose any information tied to your OS, personal files, and customized settings. However, this is likely to resolve your issue.

To do a repair install, follow the detailed steps in Install Windows 10 on a new PC from USB.

Conclusion

That's it for all the possible solutions to the “Windows Resource Protection found corrupt files but was unable to fix them Windows 10” error.

Frequently Asked Questions about Windows Resource Protection Finding Corrupted Files

Below are some closely related issues about sfc scannow finding corrupted files but unable to fix some of them. If you're also experiencing these problems, you may refer to the brief demonstration.

How to fix "Windows Resource Protection found corrupt files but was unable to fix some of them"?

To address the issue where "sfc scannow" fails to fix certain files, you can try the following methods:

Check and fix hard drive errors Run the DISM command to repair corrupted files Run sfc / scannow in Safe Mode Run SFC from the Windows Recovery Environment (WinRE) Perform a Windows 10 Repair Install

How to fix corrupted files with SFC Scannow?

You can run sfc /scannow to check and fix corrupted system files.

1. Click the Search button on your Windows computer. Type in CMD, then right-click Command Prompt and select "Run as administrator."

2. Type SFC /scannow and press Enter.

3. Wait for this process to complete.

How to fix the 'SFC cannot repair corrupted files' issue in Windows 10?

Try running the Windows Update troubleshooter to see if that fixes problems with Windows Update.

1. Press the ⊞ Win key, type troubleshoot, and select it from the list.

2. In the left pane, click “View all,” and then run the “Windows Update Troubleshooter” from the list.

3. Click “Advanced,” and make sure “Apply repairs automatically” is checked and that you've selected “Run as administrator.”

4. Click "Next" and follow the on-screen instructions to complete the troubleshooting process.

Then, run SFC and see if the problem persists.

Can I recover a corrupted file? How do I fix a corrupted file?

File corruption refers to a situation where a computer file suddenly becomes inoperable or unusable. There can be various reasons for file corruption. In some cases, the corrupted file can be recovered and repaired, whereas in other instances, it might need to be deleted and replaced with a previously saved version.

You can fix the issue with the help of a file recovery tool – Data Recovery Wizard, in just 3 steps:

1. Scan your hard drive for damaged files.

2. Select and preview the damaged file you want to recover.

3. Easily repair corrupted files, and then restore them to your storage device.