Author Topic: When I start my computer I get an error about aswFsBlk service failed to start.  (Read 15955 times)

0 Members and 1 Guest are viewing this topic.

Offline Asyn

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 76213
  • Urlaub/Vacation
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
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.

Good.
[OT]: For further/future questions, a sig might help. ;)
W8.1 [x64] - Avast PremSec 22.7.7366.BC [UI.713] - Firefox ESR 91.11 [NS/uBO/PB] - Thunderbird 91.11
Avast-Tools: Secure Browser 103.0 - Cleanup 22.2 - SecureLine 5.18 - DriverUpdater 22.2 - CCleaner 6.01
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline schmidthouse

  • VIRUS FREE A Long Time
  • Avast Evangelist
  • Starting Graphoman
  • ***
  • Posts: 7118
  • When you think you know, Think Again
On build 2011 you can delete registry key HKLM\SYSTEM\CurrentControlSet\Services\aswFsBlk.

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

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.
***HP ENVY 15K LT W10 Pro 21H2 64Bit/250GB SSD/16GB Ram/ADU v.22.2b/VS/SANDBOXIE-plus/MailWasherPRO
**HP Compaq 8510p LT W10 Pro 21H2 64Bit/1TB HD/8GB Ram/ADU v.22.2b/VS/SANDBOXIE/HotSpot Shield
 Avast Mobile Security (Android)
LAYERED SECURITY SOFTWARE

jwoods301

  • Guest
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.

Offline drake127

  • Avast team
  • Sr. Member
  • *
  • Posts: 324
It shouldn't be needed by now. We released an update which should take care of this issue.

crofty59

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

Thanks for the update :)