[SOLVED] Win10 - Avast Corruption

M

MeSo2

New member
Joined
Jul 20, 2016
Posts
4
The script worked for one of my systems, but for the other it is not sticking. The outcome looks like it would work, but after a reboot it is back to the old error. This is the SFCFixScript.txt file:

Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-07-20 16:55:21.271
Microsoft Windows 10 Build 10586 - amd64
Using .txt script file at C:\Users\nathaniel\Desktop\SFCFixScript.txt [4]




RegistryScript::
Successfully  took ownership and permissions for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396.
Successfully  took ownership and permissions for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c.

Successfully  imported registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396.
Successfully  imported registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c.

Successfully  restored ownership and permissions for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396.
Successfully  restored ownership and permissions for registry key  HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c.
RegistryScript:: 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-20 16:55:22.396
Script hash: Ytl4LY447JqC9qrxi+JoCASFwgP3DflFodDT1k/A4sw=
----------------------EOF-----------------------
 
BrianDrab said:
Your script may not be complete.
Click to expand...
I used the exact same set of files (script and executable) I used on the first system. Because it worked there, I thought it would also work with the second system. This is strange.

I did used Corrupt Manifest (manifest is damaged) on the first system; and not, as you suggested Manifest is missing (manifest is missing). I will go ahead and try this other script.
 
I tried the other script, and it did also not work. This is the resulting prompt after running it.
SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-07-21 08:33:20.753
Microsoft Windows 10 Build 10586 - amd64
Using .txt script file at C:\Users\nathaniel\Desktop\SFCFixScript.txt [1]

RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.

Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.11.0.avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_b2556b4035446b41.

Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
RegistryScript:: directive failed to complete successfully.

Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2016-07-21 08:33:21.779
Script hash: /obSQMtMefLQkM13I9SCK2iXlUslj2V+2uxnIwHBhPw=
----------------------EOF-----------------------
Click to expand...

after a reboot and running sfc /scannow again and then using SFCFix it get this:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-07-21 08:49:12.069
Microsoft Windows 10 Build 10586 - amd64
Not using a script file.

AutoAnalysis::
WARNING: Performed DISM repair due to manifest damage on component "amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_53c8344321b452ba". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.23918.0_none_9b756b1a36307bc0". 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: 20
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 3 datablocks.
Finish time: 2016-07-21 08:56:13.962
----------------------EOF-----------------------
Click to expand...

am I doing something wrong?

I have avast still installed, but it is disable.
 
You're not doing anything wrong. The fixes were for v. 11.0.60610.1 however your issues are with v14.0.23918.0 as shown below.

Code: 
WARNING: Performed DISM repair due to manifest damage on component "amd64_avast.vc140.crt_fcc99ee6193ebbca_[COLOR=#FF0000]14.0.23918.0[/COLOR]_none_53c8344321b452ba". See CBS logfile for more details.
 WARNING: Performed DISM repair due to manifest damage on component "x86_avast.vc140.crt_fcc99ee6193ebbca_[COLOR=#FF0000]14.0.23918.0[/COLOR]_none_9b756b1a36307bc0". See CBS logfile for more details.

Is it your intention to keep Avast?
 
BrianDrab said:
The fixes were for v. 11.0.60610.1 however your issues are with v14.0.23918.0 as shown below.
Is it your intention to keep Avast?
Click to expand...
Sorry, I missed the version number part not matching up. Yes, I would like to keep Avast, but if need be I can do without it.
 
The reason I ask is that I believe Avast may have fixed the issue in this version. What I would suggest is to do a complete uninstall of the software and then a re-install of the software. Then do a sfc /scannow again. If errors are still reported then we'll handle manually. Let me know.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top