New
#11
Bottom line - I cannot use this machine unless I F8 and opt for "Last Known Good Configuration"
every time I start up.
BUT what I don't understand is why it doesn't throw up BSOD when using
"Last Known Good Configuration" because it stills starts from scratch (albeit F8).
Your last known good is controlset005. Comparing that with controlset001 reveals an additional avast filter driver in controlset001.
Attachment 407835
There is also a driver set to start type 0 called aswARdisk
Attachment 407836
Possibly your Avast updated itself and added this new driver which is causing the problem.
1. Boot up using last known good - then use avast uninstall tool.
Avast Uninstall Utility | Download aswClear for Avast Removal
That might do the job - without having to do any manual registry editing. I don't know how effective their uninstall tool is at scouring dormant controlsets- maybe it will do a great job.
OR
2. If that doesn't work - then you will need to make some registry edits manually:
Boot up using last known good.
Then open regedit and use the find function on controlset001 to remove the extra filter, and also set the start type to 4.
You will need to check the other controlsets ( except 005 which is fine because it works)
You can then unistall avast using their tool.
Last edited by SIW2; 15 Apr 2019 at 11:09.