When I start my computer I get an error about aswFsBlk service failed to start.

Just did a repair and the error is still there.

Also, both “Program” and Engine & Definitions" updates start, but are not downloading anything. So more fun, figuring out if its your servers or something else that was broken.

Oh and one more thing, has anybody noticed all the user added exclusions are now gone?

Normally I would just laugh and call this type of thing as job security. But I recommended Avast, so my management perceives I own this mess and a reflection on my competency.

On build 2011 you can delete registry key HKLM\SYSTEM\CurrentControlSet\Services\aswFsBlk.

and that’s safe to do?

Yes, we removed aswFsBlk from 9.0.2011 but it seems that it didn’t get deleted for you (file got deleted but registry key didn’t).

So what exactly do I delete?

The entire “folder” on the left side of the Registry for awsFsBlk found at the location you said or a specific file?

You can delete entire “folder” (key). If you are not comfortable with that, you can also set “Start” value in this folder to “4” and revert it back if you encounter some issues.

I got an error when attempt this.

“Cannot Delete aswFsBlk: Error While Deleting Key”

Do I need to turn off the self defense module?

Yep.

Just did that, checked the error console and it didn’t return this time on restart and everything is running fine now, so I think this fixed the issue.

I ended up doing a clean install with the pro version as well.
Should have checked here first. Ah Well, all is now working :slight_smile:

Good.
[OT]: For further/future questions, a sig might help. :wink:

This may not be significant, but I totally removed RC2 with AvastClear.exe in safemode(CleanInstall) BEFORE installing v 9.0.2011 and did not have this Reg Key issue.

Before making any changes to the registry, make sure to back it up.

Even though a clean install is the long way around, it’s safer than modifying the registry.

It shouldn’t be needed by now. We released an update which should take care of this issue.

Thanks for the update :slight_smile: