Do you have the same troubles with %USERPROFILE%\AppData\Local\Temp ?
No, I can access that folder without any problems. I dont have any control over where the app stores its data and the target machine doesnt use avast so it wouldnt have this issue.
I logged into my test machine as a non-administrative user and had this problem. Even after entering correct admin credentials at the prompts I got the access denied message. But after I disabled the self-defense and tried to view the c:\windows\temp (after jumping through security hurdles again), my user account was added by Windows to the folder's security with full control and was able to access the folder even when self-defense was enabled again.
I don't know a lot about this mechanism. It appears Avast is not letting Windows apply the security once automatically. Could be a bug, or by design. In either case, I'd suggest logging a support ticket with Avast if your user account is not applying by itself.
So this could explain why some people have problems and some don't. It could be some users have accessed c:\windows\temp before Avast was ever installed and the security was set correctly.
@kevrianate, are you the application developer or not? Why can't you change the location? In general you should not be hard-coding %systemroot%\temp as you might fix the security for one non-administrative user, but not all, and your permissions will be lost if you reinstall Windows etc. This location is a throwback to the Win95 days and is mostly just for Windows internal system use which is why it is now much more secure than in the past.
If you must use %systemroot%\temp, try running the app using Program Compatibility Troubleshooter, or apply appropriate security to the folder yourself (but I disapprove of this!).