Windows 10: scannow fails at 31

After using some software that cleans the registry i am getting some errors about windows explorer that has stopped , so i decided to do a sfc s/scannow but it stuck at 31 %
I read some solution on this forum and what i did
"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) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) bcdedit /enum {badmemory}

10) 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
"

solution provided by zbook
but it didn"t help
this is the report


Microsoft Windows [Version 10.0.19041.388](c) 2020 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scanowMicrosoft (R) Windows (R) Resource Checker Version 6.0Copyright (C) Microsoft Corporation. All rights reserved.Scans the integrity of all protected system files and replaces incorrect versions withcorrect Microsoft versions.SFC [/SCANNOW] [/VERIFYONLY] [/SCANFILE=<file>] [/VERIFYFILE=<file>] [/OFFWINDIR=<offline windows directory> /OFFBOOTDIR=<offline boot directory> [/OFFLOGFILE=<log file path>]]/SCANNOW Scans integrity of all protected system files and repairs files with problems when possible./VERIFYONLY Scans integrity of all protected system files. No repair operation is performed./SCANFILE Scans integrity of the referenced file, repairs file if problems are identified. Specify full path <file>/VERIFYFILE Verifies the integrity of the file with full path <file>. No repair operation is performed./OFFBOOTDIR For offline repair, specify the location of the offline boot directory/OFFWINDIR For offline repair, specify the location of the offline windows directory/OFFLOGFILE For offline repair, optionally enable logging by specifying a log file pathe.g. sfc /SCANNOW sfc /VERIFYFILE=c:\windows\system32\kernel32.dll sfc /SCANFILE=d:\windows\system32\kernel32.dll /OFFBOOTDIR=d:\ /OFFWINDIR=d:\windows sfc /SCANFILE=d:\windows\system32\kernel32.dll /OFFBOOTDIR=d:\ /OFFWINDIR=d:\windows /OFFLOGFILE=c:\log.txt sfc /VERIFYONLYC:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 31% complete.Windows Resource Protection could not perform the requested operation.C:\WINDOWS\system32>dism /online /cleanup-image /scanhealthDeployment Image Servicing and Management toolVersion: 10.0.19041.329Image Version: 10.0.19041.388[===========================85.3%================= ]Error: 5Access is denied.The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.logC:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.19041.329Image Version: 10.0.19041.388[===========================52.8% ]Error: 5Access is denied.The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.logC:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 31% complete.Windows Resource Protection could not perform the requested operation.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 655616 file records processed.File verification completed. Phase duration (File record verification): 28.32 seconds. 13428 large file records processed. Phase duration (Orphan file record recovery): 0.00 milliseconds. 0 bad file records processed. Phase duration (Bad file record checking): 0.33 milliseconds.Stage 2: Examining file name linkage ... 691 reparse records processed. 891244 index entries processed.Index verification completed. Phase duration (Index verification): 35.69 seconds. 0 unindexed files scanned. Phase duration (Orphan reconnection): 3.40 seconds. 0 unindexed files recovered to lost and found. Phase duration (Orphan recovery to lost and found): 0.69 milliseconds. 691 reparse records processed. Phase duration (Reparse point and Object ID verification): 6.90 milliseconds.Stage 3: Examining security descriptors ...Security descriptor verification completed. Phase duration (Security descriptor verification): 31.12 milliseconds. 117815 data files processed. Phase duration (Data attribute verification): 0.42 milliseconds.CHKDSK is verifying Usn Journal... 38256880 USN bytes processed.Usn Journal verification completed. Phase duration (USN journal verification): 188.27 milliseconds.Windows has scanned the file system and found no problems.No further action is required. 242994030 KB total disk space. 126033360 KB in 435171 files. 325248 KB in 117816 indexes. 0 KB in bad sectors. 769866 KB in use by the system. 65536 KB occupied by the log file. 115865556 KB available on disk. 4096 bytes in each allocation unit. 60748507 total allocation units on disk. 28966389 allocation units available on disk.Total duration: 1.12 minutes (67667 ms).C:\WINDOWS\system32>wmic recoveros set autoreboot = falseUpdating property(s) of '\\ALX\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk1\\Partition4"'Property(s) update successful.C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7Updating property(s) of '\\ALX\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk1\\Partition4"'Property(s) update successful.C:\WINDOWS\system32>bcdedit /enum {badmemory}RAM Defects-----------identifier {badmemory}C:\WINDOWS\system32>

:)

 

Windows 10 fails to update


When you finish testing the Avast suggestion, make sure that you restart your machine.

Then if the issue persists, please return to the trouble shooting list in post# 89

I think there are three steps that remain; the WU troubleshooter, reset WU components, and manual WU reset.

 

KB4025339 Fails Install 0x80070564

Thanks
I am trying Eagle 51's suggestions now. Windows Update troubleshooter found a bunch of errors and fixed all but one.The update is trying to download KB4025339 again. I'll see what happens. At step one troubleshooter finishes with one error unresolved "Potential Windows Update Database Error Detected-Not Fixed". Windows update stalled at 0%.

At step 2 same troubleshooter error. The KB finished a new download failed to install.
Did step 3 KB has downloaded but fails to install.

If Eagle's suggestion doesn't work I'll try EdTittel's suggestion

Tried bothe Eagle & Ed 's suggestions - do not work. Anyone else?

I have noticed that the latest update for my nvidia drivers has failed to update. Wondering about that!

 

Apr18WU Fails at 31%

I can't seem to get past this on one of my computers its a clean Install 0f 1709, never had any issues, redownloaded the MCT and recreated the Install media USB.
Ran
Dism /Online /Cleanup-Image /StartComponentCleanup
Dism /Online /Cleanup-Image /RestoreHealth
SFC /scannow

3rd attempt still stopping at this point I did click the debug option this time and nothing seems to be happening, however, there is hard drive activity.