Windows 10: SFC /scannow stuck, Windows Resource Protection could not perform...

Hello! It's my first post here. Sometimes my computer isn't booting on the first try. It just displays a black screen after POST. I had to reset it for it to boot the second time. So I tried to run sfc /scannow to maybe fix the problem. But it always get stuck at 88% with the error, Windows Resource Protection could not perform the requested operation.

I looked at the log file, CBS.log, and looks like a file is missing. It's looking for a wowreg32.exe and tries to repair/regenerate it but fails. Here is a part of the log file.

Code: 2019-06-02 04:28:18, Info CSI 000056e1 [SR] Repairing corrupted file \SystemRoot\WinSxS\Manifests\\[l:93 ml:149]'wow64_microsoft-windows-setupapi_31bf3856ad364e35_10.0.17134.1_none_24ca905a63c9023a.manifest' from backup location 2019-06-02 04:28:18, Info CSI 000056e2 Hashes for file member [l:12]'wowreg32.exe' do not match. Expected: {l:32 b:b75000da980b029a91a8334949d80a3958c6786eca0e19e85ae06ccc301b6128}. Actual: {l:32 b:0299f757a85a1aad6cbe1ad2b0eda925d8df667cd04e646af8917f65cbf24537}. 2019-06-02 04:28:18, Error CSI 000056e3 (F) Failed on regenerating file [l:12]'wowreg32.exe'[gle=0x80004005] 2019-06-02 04:28:18, Info CSI 000056e4 [SR] Unable to repair \SystemRoot\WinSxS\wow64_microsoft-windows-setupapi_31bf3856ad364e35_10.0.17134.1_none_24ca905a63c9023a\\[l:12]'wowreg32.exe' 2019-06-02 04:28:18, Info CSI 000056e5 [SR] Repaired file \SystemRoot\WinSxS\wow64_microsoft-windows-setupapi_31bf3856ad364e35_10.0.17134.1_none_24ca905a63c9023a\\[l:12]'wowreg32.exe' by copying from backup 2019-06-02 04:28:18, Info CSI 000056e6 CSIPERF - BackupPI Queue 106ms 2019-06-02 04:28:18, Info CSI 000056e7@2019/6/1:20:28:18.167 Primitive installers committed for repair 2019-06-02 04:28:18, Info CSI 000056e8 [SR] Cannot repair member file [l:12]'wowreg32.exe' of Microsoft-Windows-SetupAPI, version 10.0.17134.1, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file is missing 2019-06-02 04:28:18, Info CSI 000056e9 [SR] This component was referenced by [l:155]'Microsoft-Windows-Client-Features-WOW64-Package0017~31bf3856ad364e35~amd64~~10.0.17134.1.microsoft-windows-client-features-wow64-deployment00170-Deployment' 2019-06-02 04:28:18, Info CSI 000056ea Manifest hash for component [l:84 ml:140]'wow64_microsoft-windows-setupapi_31bf3856ad364e35_10.0.17134.1_none_24ca905a63c9023a' does not match expected value. Expected:{l:32 b:6f160057d3e7628d5fab1464e38ac8ac666e9616cb430f56cf1164fd5cbd0940} Found:{l:32 b:1e6ed764d49ec5eb2751495eb38807b02ed5a895c250494ed6f559e4b372a9d9}. 2019-06-02 04:28:18, Info CSI 000056eb Unable to load manifest for component [l:84 ml:140]'wow64_microsoft-windows-setupapi_31bf3856ad364e35_10.0.17134.1_none_24ca905a63c9023a'[/quote] So, anyone know how to fix it? Thank you!

:)

 

SFC /SCANNOW, Windows Resource Protection Could Not Perform....


Good news.. this issue has been fixed in build, 14942.

Screen Shot:

 

sfc /scannow "Windows Resource Protection could not start the repair service"

Hi,

Windows Resource Protection could not start the repair service is an error which may occur if you are trying to run the System File Checker tool (SFC /SCANNOW) to scan and repair Windows system files. To resolve this error, we suggest that you follow the
steps below:

• Press the Windows + R keys to open run command box.
• In the run command box, type services.msc, and press
  Enter.
• In the list of services, double click the Windows Modules Installer service.
• Set the startup type to Auto, and click OK.
• Restart your computer.
• After the restart, you'll be able to run the sfc /scannow command without any problems.

We would appreciate it if you could get back to us and provide us your feedback.

 

Error message "Windows Resource Protection could not perform the requested operations" when running SFC /Scannow

I am running Windows 10 Ver. 1703 Build 15063.296. When I run SFC /Scannow, using Windows PowerShell, I receive the following message: Windows Resource Protection could not perform the requested operation. This occurs at 23%.

I ran DISM Repair-WindowsImage -Online -RestoreHealth and it returned ImageHealthState: Healthy. I rebooted computer and reran SFC /Scannow and it returned Windows Resource Protection did not find any integrity violations. If I rerun SFC /Scannow 2 or
3 hours later and I receive Windows Resource Protection could not perform the requested operation, again at 23% process.

What is causing this and how do I resolve it? It is a bug?

***Subject edited for clarity by the moderator.***