After installing Avast on Win11, everything in Documents folder is read-only!!

[Robert1034]

Hello,
   Two days ago 10/4/22, after installing Avast on a brand new laptop with Win11 all kinds of problems started popping up.   

I finally traced the problem down to the fact that everything from the Documents folder on down is now Read-Only.

I tried uninstalling Avast but the Read-Only condition remained.
I tried changing permissions on Documents folder but it wouldn't work.

Could this be a bug in the Ransomware Shield?
Is anyone else experiencing this?   

Thanks,
Rob

[r@vast]

Hi,

This does not sound like an issue that would be caused by Avast.
What type of files (e.g. doc, pdf) are in the documents folder? Which application(s) do you use to work with these files?
Can you provide a support file, please? https://support.avast.com/article/submit-support-file/

[bob3160]

I'm on Windows 11. That's not a problem I'm having on 4 Win. 11 systems in my home.

[Robert1034]

Hello,
  Here's a piece of info that I did not know before...

Malwarebytes (PAID vers.) now has a Ransomware Sheild option just as Avast does.

I did NOT  know that this was already running on the laptop as I installed Avast.

Question: Could it be?...  that both (Malwarebytes - Ransomware shield) and (Avast - Ransomware shield) were both trying to lockdown unauthorized writing to the main C:/Users/xxxx/ Documents folder and this caused the condition I'm now seeing...  that nothing can write to the Documents folder??

Question 2:  Shouldn't Avast have a warning that installing it would conflict with the already installled Malwarebytes??

Thanks,
Rob

[Dinobot2]

Kind of a stupid question that i'm sure you checked already, but when you go to your Avast Ransomware settings, is it on Smart mode or Strict mode?

[CraigB]

Hello,
  Here's a piece of info that I did not know before...

Malwarebytes (PAID vers.) now has a Ransomware Sheild option just as Avast does.

I did NOT  know that this was already running on the laptop as I installed Avast.

Question: Could it be?...  that both (Malwarebytes - Ransomware shield) and (Avast - Ransomware shield) were both trying to lockdown unauthorized writing to the main C:/Users/xxxx/ Documents folder and this caused the condition I'm now seeing...  that nothing can write to the Documents folder??

Question 2:  Shouldn't Avast have a warning that installing it would conflict with the already installled Malwarebytes??

Thanks,
Rob

Personally I'd recommend removing Malwarebytes or Avast, it is possible to run Malwarebytes alongside Avast with exclusions in place though Malwarebytes is a complete standalone service these days.

You also have Windows Security on Win 11 and that also requires exclusions between Malwarebytes and itself if you choose to run them together.