jvidal
8
From what I read on the other topic, it seems that avast is blocking access to some registry sections (I believe it’s HKLM\Software\Wow6432Node) due to it’s self-defense. Disabling avast’s self-defense solves the problem (not recommended, though).
I think avast is blocking access to the whole section, instead of just protecting its own startup entry (and only that).
Another bug that needs fixing ASAP.