scannow fails at 72%

Hello,

I am trying to improve my Windows experience so I ran "sfc /scannow" but it stopped at 72%. I don't have the exact error but it was something like:

Windows resource protection could not perform the requested operation.

I also ran:

DISM.exe /Online /Cleanup-image /Restorehealth

and got a very similar error that occurred at 72% again.

I looked up this error and one thing said to run CHKDSK and it came back with no errors. I am wondering is the scannow problem a real potential problem? Does anyone know about it not working?

Thanks.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan

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





8) Please perform an in place upgrade repair.

9) Windows 10 iso can be downloaded to the desktop or to a flash drive.

The in place upgrade can be performed with Windows 1809, 1903, or 1909 depending on the preferred version.

Unless you deliberately blocked Windows upgrades it is likely there was a Windows upgrade failure with error code and message.

See if you can fix the operating system and component store problems by starting with the identical iso: 1809

Windows Download - #1 Windows ISO Download Source
Microsoft Windows and Office ISO Download Tool
TechBench by WZT (v4.1.1)


https://www.microsoft.com/en-us/soft...load/windows10
Download Windows 10 ISO File
Create Bootable USB Flash Drive to Install Windows 10



Repair Install Windows 10 with an In-place Upgrade

Here are the results of the commands you asked me to execute:

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

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

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

Windows Resource Protection could not perform the requested operation.

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

Deployment Image Servicing and Management tool
Version: 10.0.17763.771

Image Version: 10.0.17763.973

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

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

Deployment Image Servicing and Management tool
Version: 10.0.17763.771

Image Version: 10.0.17763.973

[==========================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 72% complete.

Windows Resource Protection could not perform the requested operation.

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

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

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

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

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

487377734 KB total disk space.
280541896 KB in 744593 files.
378344 KB in 122157 indexes.
0 KB in bad sectors.
1211786 KB in use by the system.
65536 KB occupied by the log file.
205245708 KB available on disk.

4096 bytes in each allocation unit.
121844433 total allocation units on disk.
51311427 allocation units available on disk.

C:\WINDOWS\system32>

Place the computer in safe mode:
Boot into Safe Mode on Windows 10..

Run sfc /scannow three times

If this does not fix the underlying problem then perform the following steps:

1) open administrative command prompt and copy and paste:


findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

2) find the txt file on the desktop and post a share link into the thread

3) post share links for each:
a) C:\Windows\Logs\CBS\CBS.log
b) C:\Windows\Logs\Dism\Dism.log

Thanks, Do you still want me to do #8 & #9 from post #2?

If the steps in post #4 do not fix the scannow problem it should be able to be fixed by the in place uprade repair.

Ordinarily a normal component store (restorehealth) fixes problems with scannow.

The CBS and DISM files may have information about the cause of the scannow problem.

So post the share links to see if there is any useful information.

The in place upgrade will be done if there is not an easy fix.

Ok,

In Safe mode it failed each time @72% Here are the logs:

CBS.log - Google Drive
dism.log - Google Drive
sfcdetails.txt - Google Drive

Thanks.

The logs displayed Windows defender hash mismatch and corruption repair:

Code:

2020-02-10 22:39:48, Info                  CSI    00003975 [SR] Cannot repair member file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-02-10 22:39:48, Info                  CSI    00003977 [SR] Cannot repair member file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-02-10 22:39:48, Info                  CSI    00003979 [SR] Cannot repair member file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-02-10 22:39:48, Info                  CSI    0000397b [SR] Cannot repair member file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-02-10 22:39:48, Info                  CSI    0000397d [SR] Cannot repair member file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-02-10 22:39:48, Info                  CSI    0000397f [SR] Cannot repair member file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-02-10 22:39:48, Info                  CSI    00003981 [SR] Cannot repair member file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-02-10 22:39:48, Info                  CSI    00003983 [SR] Cannot repair member file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-02-10 22:39:48, Info                  CSI    00003985 [SR] Cannot repair member file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

Code:

2020-02-10 22:49:01, Info                  CSI    0000689a [SR] Repairing corrupted file \??\C:\ProgramData\Microsoft\Windows\Models\\SBCModel.json from store
2020-02-10 22:49:01, Info                  CSI    0000689c [SR] Repairing corrupted file \??\C:\ProgramData\Microsoft\Windows\Models\\SBCModel.txt from store

An in place upgrade repair can be attempted to 1909.

Thanks. What is "1909" exactly?