Brian_Busnitech
Member
- May 9, 2020
- 18
sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.14393.3241
Image Version: 10.0.14393.3241
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
SFCFIX
Processing directive 1 of 1 (AutoAnalysis::)
Checking store directories . . .
Checking CBS.log . . .
Checking CheckSUR.log . . .
Checking CheckSUR.persist.log . . .
SUMMARY:
CBS & SFC total detected corruption count: 0
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
Press any key to continue to explanation of summary . . .
No corruptions have been detected on this computer. Whilst this is a good thing,be aware that not all types of corruption can be detected by this tool.
Therefore, if you are currently experiencing continued problems with your
computer it is likely that you are going to need the assistance of a human
analyst in order to find and fix them.
If your problems persist, and you are currently being instructed by a helper,
you should let them know about this development by sending them the logfile
which will soon be generated and opened so that they can perform a manual fix.
If you are not currently being instructed by a helper but still need assistance,you should seek free advice from your favourite forum or sysnative.com. Create anew thread and provide this logfile in the first post of that thread along with
a complete description of the problems you were experiencing which led you to
run this tool.
SFCFix version 3.0.2.1 by niemiro.
Start time: 2021-03-16 17:43:37.768
Microsoft Windows Server 10 Build 14393 - amd64
Not using a script file.
AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2021-03-16 17:45:19.744
----------------------EOF-----------------------
--------------------- > 8 ----------------------
In the past I have followed the normal routines of renaming the software distribution folder but provides no cure. I have the SFCFix logs from a few other attempts. I had posted to the forum back in Dec but never got a response so this kind of slipped off my radar.
Other patches such as .Net and Servicing Stack updates have no issues.
Attached is the current CBS logs folder here
I am hoping this post has a bit more info in the Log that can help point me in the right direction.
Thanks everyone for your help.
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.14393.3241
Image Version: 10.0.14393.3241
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
SFCFIX
Processing directive 1 of 1 (AutoAnalysis::)
Checking store directories . . .
Checking CBS.log . . .
Checking CheckSUR.log . . .
Checking CheckSUR.persist.log . . .
SUMMARY:
CBS & SFC total detected corruption count: 0
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
Press any key to continue to explanation of summary . . .
No corruptions have been detected on this computer. Whilst this is a good thing,be aware that not all types of corruption can be detected by this tool.
Therefore, if you are currently experiencing continued problems with your
computer it is likely that you are going to need the assistance of a human
analyst in order to find and fix them.
If your problems persist, and you are currently being instructed by a helper,
you should let them know about this development by sending them the logfile
which will soon be generated and opened so that they can perform a manual fix.
If you are not currently being instructed by a helper but still need assistance,you should seek free advice from your favourite forum or sysnative.com. Create anew thread and provide this logfile in the first post of that thread along with
a complete description of the problems you were experiencing which led you to
run this tool.
SFCFix version 3.0.2.1 by niemiro.
Start time: 2021-03-16 17:43:37.768
Microsoft Windows Server 10 Build 14393 - amd64
Not using a script file.
AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2021-03-16 17:45:19.744
----------------------EOF-----------------------
--------------------- > 8 ----------------------
In the past I have followed the normal routines of renaming the software distribution folder but provides no cure. I have the SFCFix logs from a few other attempts. I had posted to the forum back in Dec but never got a response so this kind of slipped off my radar.
Other patches such as .Net and Servicing Stack updates have no issues.
Attached is the current CBS logs folder here
I am hoping this post has a bit more info in the Log that can help point me in the right direction.
Thanks everyone for your help.