New
#91
That's ok, it is the policy for WU - if it was set to not update, then you would change it to update. Not having a policy is the same as accepting the default - > allow updates
Continue with the other suggestions ....
I'll be out of town for the next few days but the rest of the steps are fairly standard - any member can assist you if you have questions
Completed step 3; Restore health to the component store. Found same problem as last time: sfcdetails10.zip
Should I stop here or do the next step. Please advise.
Apparently Avast is currently NOT playing fair on W10, it is corrupting sfc reports.
Whether or not this is causing a cascade effect on your system im not sure.
This was first reported on the Sysnative forum.
Windows 10 -- Avast causing corrupt manifest files Fix
Roy
That is just a few hash mismatches in the components hive causing 'corruption', not something to be truly worried about because the files themselves are not corrupted.
Regarding Avast: I have removed it during the tests using CCleaner removal tool. Would I have still experienced the issues mentioned above?
@tybee, using CCleaner to remove Avast is the same as running the Avast uninstaller from Programs and Features. It is almost certain it did not remove all pieces of Avast. Even Avast realizes this and supplies a standalone program to run after the standard uninstall. It is strongly recommended that you download and run this standalone uninstaller. Here is the link, download it and follow the instructions carefully. TC
Avast Uninstall Utility | Download aswClear for Avast Removal
Last edited by simrick; 22 Jul 2016 at 13:33.
After I uninstall avast with the new uninstaller I will redo the previous actions. My question is whether or not the files previouly downloaded and used in the tests/actions are good or were they corrupted by Avast remnants? Do I need to download new ones?