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

the4thGodfather · 01 Jun 2019

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'

So, anyone know how to fix it? Thank you!

zbook · 01 Jun 2019

1) Open administrative command prompt and type or copy and paste:
2) dism /online /cleanup-image /scanhealth
3) dism /online /cleanup-image /restorehealth
4) sfc /scannow
5) chkdsk /scan
6) wmic recoveros set autoreboot = false
7) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

the4thGodfather · 02 Jun 2019

Thank you for replying to my post. Here are the results:

Code:

Microsoft Windows [Version 10.0.17134.765]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.765

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.765

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 88% complete.

Windows Resource Protection could not perform the requested operation.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is Windows 10.

Stage 1: Examining basic file system structure ...
  652544 file records processed.
File verification completed.
  26587 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  25561 reparse records processed.
  826082 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.
  25561 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  86770 data files processed.
CHKDSK is verifying Usn Journal...
  38713960 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

 447854090 KB total disk space.
 398059540 KB in 539165 files.
    314448 KB in 86771 indexes.
         4 KB in bad sectors.
    783390 KB in use by the system.
     65536 KB occupied by the log file.
  48696708 KB available on disk.

      4096 bytes in each allocation unit.
 111963522 total allocation units on disk.
  12174177 allocation units available on disk.

zbook · 02 Jun 2019

1) Open administrative command prompt and copy and paste:
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

2) Find the new text file on the desktop > post a share link into the thread using one drive, drop box, or google drive

3) Turn off windows fast startup:
Turn On or Off Fast Startup in Windows 10

4) Place the computer in safe mode with command prompt:
Boot into Safe Mode on Windows 10

5) Run sfc /scannow three times to see whether repetitive runs or safe mode have any impact.

6) If the above steps fix the problem the you are set

7) If the above steps fail then:
a) open administrative powershell and type or copy and paste:
Get-ComputerRestorePoint
b) view the dates to determine whether there is a restore point that predates the computer problems
c) if there is a usable restore point the attempt system restore:
System Restore Windows 10

8) The computer is using Windows 1803.
If the above steps fail then perform an in place upgrade repair: (make sure the computer is no longer in safe mode)
Repair Install Windows 10 with an In-place Upgrade

The in place upgrade repair can be attempted using windows 1803, 1809, or 1903 iso files.