I'm on Windows 10. I have Avast installed to C:\Programs\Avast. Which is the folder where all my other programs are installed as well. Naturally, the other programs need read and write access to their own folders within C:\Progams. The following issue has occurred to me within a span of about 2 months, maybe less. Something restricted the access flags in C:\Programs to read only. I discovered this at first when Notepad++ crashed and the restored session was from 2 weeks earlier. N++ runs from C:\Programs\N++ on my machine, and writes the session backup files in a subdirectory under that path. At the time I found that I needed special privileges to delete files and folders from C:\Programs and that running N++ with admin privileges resolved the problem. That is not really a way I want to run it. Trying to give my user permission to write in C:\Programs ran into Avast throwing an error, as did giving write permissions to only the other folders in C:\Programs didn't work. So I tried to disable Avasts self defense, and the change of permission went through without a hitch, N++ would save backups again. I even enabled the self defense and all seemed to work as it should. That was until the middle of this week. By chance, I discovered the same symptoms today again. And it appears that the same thing happened again. I could "fix" it in the same manner as last time, but it leaves me in a position where I have to be paranoid of Avast setting flags where it shouldn't and causing loss of data and work as a result. I'm fine with Avast restricting access to C:\Programs\Avast, but I need it to stay out of C:\Programs way as several programs there need to write to subfolders therein. The second point is that I don't know when this happens. I'm assuming it is a silent update that is causing the issue, but that is a guess. I know from the first time this happened that a restart won't fix the issue, and that the manual fix sticks through a restart as well.
So what do I do? Am I turning off self defense? Do I uninstall Avast and install it to C:\. Neither are options I like very much.
PS:
This seems to be a similar issue