Windows 10: SFC failed to repair corrupted files Windows Resource Protection found corrupt files but...

Hi,

I have performed sfc /scannow to check the integrity of the system files as the system is taking much time to boot and the disk read time is getting higher and often encounters STOP ERROR memory management error. and came to know that,
"Windows Resource Protection found corrupt files but was unable to fix some of them."

some of the errors: hash for file number does not match, the source file in the store is also corrupted hence failed to repair and some warning such as overlap directory,

It's gonna be a great help if anybody guides me regarding what I should do.

OS Name: Microsoft Windows 10 Pro N
OS Version: 10.0.19041 N/A Build 19041
-> Furthermore, I use an ordinary account to login and run mmc with the administrative privileges to perform any other administrational tasks but for last few days whenever I try to apply "run as administrator" - it shows, " your app is blocked by the system administrator", I didn't modify any group policy, what is the possible cause for the issue and how to resolve the issue.
even when I login using a privileged account whenever I try to access manage / disk management from my computer: same message is shown.

Any help will be highly appreciated.

Thank you .
_______________________________________________________________________________
Some of the entries of the log file is as follows:

2020-12-06 09:11:57, Info CSI 0000010b Hashes for file member [l:10]'pnidui.dll' do not match.
Expected: {l:32 ml:33 b:39f89789cf3e17e915cb6194ddda1a072ace6583569586b00c8d1c5146e41743}.
Actual: {l:32 b:a527163c5efe0fba2ca75a079005fa2559c433301309a25852fa1d4ed47129c5}.
2020-12-06 09:11:57, Info CSI 0000010c [SR] Cannot repair member file [l:10]'pnidui.dll' of Microsoft-Windows-Pnidui, version 10.0.19041.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-12-06 09:12:03, Info CSI 0000010d CSIPERF - FilePI Queue 359ms
2020-12-06 09:12:03, Info CSI 0000010e Hashes for file member [l:10]'pnidui.dll' do not match.
Expected: {l:32 ml:33 b:39f89789cf3e17e915cb6194ddda1a072ace6583569586b00c8d1c5146e41743}.
Actual: {l:32 b:a527163c5efe0fba2ca75a079005fa2559c433301309a25852fa1d4ed47129c5}.
2020-12-06 09:12:03, Info CSI 0000010f [SR] Cannot repair member file [l:10]'pnidui.dll' of Microsoft-Windows-Pnidui, version 10.0.19041.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-12-06 09:12:03, Info CSI 00000110 [SR] This component was referenced by [l:124]'Microsoft-Windows-Client-Desktop-Required-Package04111~31bf3856ad364e35~amd64~~10.0.19041.1.add754de325f746fb8e99c7de928ea16'
2020-12-06 09:12:03, Info CSI 00000111 Hashes for file member [l:10]'pnidui.dll' do not match.
Expected: {l:32 ml:33 b:39f89789cf3e17e915cb6194ddda1a072ace6583569586b00c8d1c5146e41743}.
Actual: {l:32 b:a527163c5efe0fba2ca75a079005fa2559c433301309a25852fa1d4ed47129c5}.
2020-12-06 09:12:03, Info CSI 00000112 Hashes for file member [l:10]'pnidui.dll' do not match.
Expected: {l:32 ml:33 b:39f89789cf3e17e915cb6194ddda1a072ace6583569586b00c8d1c5146e41743}.
Actual: {l:32 b:a527163c5efe0fba2ca75a079005fa2559c433301309a25852fa1d4ed47129c5}.
2020-12-06 09:12:03, Info CSI 00000113 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\\pnidui.dll; source file in store is also corrupted

2020-12-06 09:07:46, Info CSI 0000007d Warning: Overlap: Directory \??\C:\WINDOWS\System32\drivers\en-US\ is owned twice or has its security set twice
Original owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.19041.1, arch amd64, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
New owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.19041.1, arch amd64, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
2020-12-06 09:07:46, Info CSI 0000007e Warning: Overlap: Directory \??\C:\WINDOWS\System32\wbem\en-US\ is owned twice or has its security set twice
Original owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.19041.1, arch amd64, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
New owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.19041.1, arch amd64, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
2020-12-06 09:07:46, Info CSI 0000007f Warning: Overlap: Directory \??\C:\WINDOWS\help\mui\0409\ is owned twice or has its security set twice
Original owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.19041.1, arch amd64, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
New owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.19041.1, arch amd64, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}

:)

 

Corrupted file RAR

If the archive has been created using WinRAR, why don't you try WinRAR itself? It has a built-in repair feature for repairing corrupted archive (ZIP as well as RAR). Follow the steps given below:

• Open WinRAR application in your system.
• Now click on File tab > Open or simply press Ctrl+O.
• A small window "Find Archive" will pop up. Locate the corrupt RAR archive from your system directory and select it.
• Now click Open button.
• Click Tools tab > Repair archive or simply press Alt+R.
• Again a small window "Repairing File name.rar" will pop up.
• Now click Browse to select a location to save the repaired archive.
• Check the box "Treat the corrupt archive as RAR" and click OK.
• WinRAR will start repairing of corrupt RAR archive. Once it gets completed click Close.

I hope the above steps will help you repair the corrupted RAR archive.

Thanks.

 

Why SFC can not repair corrupt files?

Hi

When I run SFC and Windows Resource Protection found corrupt files. Why SFC can not repair? I reformatted SSD drive and reinstall Windows 10 Pro then when internet disconnected, I run SFC again and Windows Resource Protection did not find any
integrity violations. When internet connected and after update, I run SFC again and Windows Resource Protection found corrupt files again (see screenshot). I don’t understand Windows Resource Protection found corrupt files. What happen found corrupt files?

 

Windows Resource Protection Found Corrupt Files

This Win10 Pro 1903 desktop began to display signs of instability. SFC /SCANNOW indicated problems. I ran these commands as suggested in another TenForums discussion:

Code:

I thought the problem was fixed. Unfortunately, the error message has returned with later runs of SFC /SCANNOW. The message:

I would consider reinstalling Windows 10, but I just got through doing that to defeat the same problem. I must be doing something wrong. But how to proceed? That is the question.