IsoQuantic
Member
I have been dealing with SFC errors that began with Avast Antivirus manifest SHA errors that conflict with registry entries.
My output from running your SFCfix tool:
----------------------BEGIN-----------------------
SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-07-16 01:25:11.121
Microsoft Windows 10 Build 10586 - amd64
Not using a script file.
AutoAnalysis::
WARNING: Performed DISM repair due to manifest damage on component "x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c". See CBS logfile for more details.
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 1
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
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2016-07-16 01:34:10.726
----------------------EOF-----------------------
I have attached my CBS and DISM log:
View attachment CBS.zip <--CBS
View attachment dism.zip <--DISM
I am reasonably savvy with Windows tools, registry manipulation, group policy editing, etc., so anyone that can help me may assume a computer literate respondee in all communications.
DISM complains a source must be specified. I ran it with the following syntax:
I also have a Specify Windows installation file location group policy set that points to the sources with the following entry:
Wim:\\Patrickslaptop\O\Windows\sources\install.wim:0
The install.wim was created from the install.iso file. I use DISM GUI and it complains "An attempt was made to load a program with an incorrect format.
The DISM log, showing a complaint about header mismatches for this attempt is attached:
View attachment dism mount error.log <--DISM mount error log
I am wondering if the wim.install index should be set to 1 in my group policy, or the fact that the image is for Windows 10.0.10586 and I am running 10.0.10586.494.
I appreciated the posts by user Go The Power at the Avast forum for the Avast issues so I decided to come here to see if someone can walk me through my problems per his direction at the Avast support site.
My output from running your SFCfix tool:
----------------------BEGIN-----------------------
SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-07-16 01:25:11.121
Microsoft Windows 10 Build 10586 - amd64
Not using a script file.
AutoAnalysis::
WARNING: Performed DISM repair due to manifest damage on component "x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c". See CBS logfile for more details.
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 1
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
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2016-07-16 01:34:10.726
----------------------EOF-----------------------
I have attached my CBS and DISM log:
View attachment CBS.zip <--CBS
View attachment dism.zip <--DISM
I am reasonably savvy with Windows tools, registry manipulation, group policy editing, etc., so anyone that can help me may assume a computer literate respondee in all communications.
DISM complains a source must be specified. I ran it with the following syntax:
Code:
DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:O:\Windows\sources\install.wim:1 /LimitAccess
I also have a Specify Windows installation file location group policy set that points to the sources with the following entry:
Wim:\\Patrickslaptop\O\Windows\sources\install.wim:0
The install.wim was created from the install.iso file. I use DISM GUI and it complains "An attempt was made to load a program with an incorrect format.
The DISM log, showing a complaint about header mismatches for this attempt is attached:
View attachment dism mount error.log <--DISM mount error log
I am wondering if the wim.install index should be set to 1 in my group policy, or the fact that the image is for Windows 10.0.10586 and I am running 10.0.10586.494.
I appreciated the posts by user Go The Power at the Avast forum for the Avast issues so I decided to come here to see if someone can walk me through my problems per his direction at the Avast support site.