Can't Seem to Disable File Monitoring

[REDACTED]

Hey all,

Running Windows 8.1 and Avast 2015.10.2.2215.  When I install SQL Server 2014 Developer edition, the installation programs wants to make changes to the C:\Windows\Temp folder.  But, it fails with a message that access is denied.  When totally uninstalling Avast, the problem does not occur.  Disabling Avast for what ever period I decide doesn't help; I still get the error.  Adding an exclusion for this folder doesn't help; I still get the error.

So, what gives?  I can certainly uninstall and reinstall Avast when I do software installations, but I would think there is a better way.

Any help would be appreciated.

Greg

[DavidR]

Well avast has a sub-folder within that area (_avast_), so may well be protected by the avast self-defence module. If that is the case it would be easier to disable that than uninstall to make changes in that area.

AvastUI > Settings > Troubleshooting.

[Eddy]

I can be wrong,
but if my memory serves me well there is a post from someone who had the same problem and it was solved in another way.

Not sure, but I believe this had something to do with it:
To what are tmp and temp set in the Environment Variables ?

[REDACTED]

Disabling doesn't work.  I tried that numerous times.  I didn't try to stop the services.  As a side note, my account, nor the administrator accounts can do anything with that folder (C:\Windows\Temp) with Avast installed.  I originally thought it had something to do with Windows' UAC.  But, that's not it.  The folder behaves just like any other folder when Avast is uninstalled. 

[DavidR]

Disabling 'what' doesn't work ?

Did you try what was suggested in my last post (disabling the avast self-defence) ?

[REDACTED]

Hey David,

By disabling, I meant Systray -> Right Click -> Avast shields control -> Disable (whatever option).  Turning off the self-defense module definitely changes the behavior of the rights to that folder.  That looks promising.  I'll try the install tomorrow morning.  I think that's going to work.

On side note, even stopping the service doesn't release the access to that folder.  Other than it being a hassle when installing programs that try to reference that folder (I have to remember to turn "self-defense" off), I think I like that feature.  Especially now that I know how to get around it when needed.

I'll have to get back on here tomorrow. 

Thank you.

Greg

[DavidR]

You're welcome.