Can't access C:/Windows/Temp/ with indication that /_avast_/ folder is involved

I’ve been trying for a few weeks to access my Windows 8.1 Temp folder to perform a regular cleaning of the folder, but have not been able to access it.

When clicking on the folder, I get “You don’t currently have permission to access this folder. Click continue to permanently get access to this folder." followed by "You have been denied permission to access this folder. To gain access to this folder you will need to use the security tab (link to security tab).

When changing Advanced Security, I get the “Error Applying Security", "An error occurred while applying security information to: C\Windows\Tempo_avast_ Failed to enumerate objects in the container. Access is denied.”

I am only able to access the folder in Safe Mode. After clearing the folder and rebooting, the issue reappears.

I have tried the following without positive results (possibly not a complete list):

  • Use an admin account - I have Admin access and can perform the same task on other computers.
  • Run as Administrator - No effect.
  • Scan HD and run sfc /scannow
    CBS.log indicated STATUS_RM_NOT_ACTIVE errors however I’m not experiencing BSOD
  • ntblog.txt Boot Log indicated dxkrnl.sys would not load however I’m not experiencing any update problems
  • Cleaned Registry using multiple utilities
  • Checked various forums including TechNet but haven’t found the exact same problem.

The computer itself has been 100% malware free for over a year.

Any advice is appreciated!

Try TFC cleaner http://www.geekstogo.com/forum/files/file/187-tfc-temp-file-cleaner-by-oldtimer/

The folder mentioned above, may be protected by avast selfprotection and may be needed to turn off before access

Hi,
the avast folder in TEMP is required for avast, it is the place where temporary unpacking and scanning takes place. This folder is protected from being deleted. It shouldn’t however affect which users can and cannot access the parent C:\WINDOWS\Temp.

Lukas.

Thanks Pondus and lukor,

@Pondus - I didn’t remember to list everything I tried. I can clear out the folder using a utility. That allows me to clear out the folders, but it doesn’t address the concern that the folder is locked. Although I haven’t seen problems with other software, I’m concerned about what other affects there may be.

@lukor - That’s a good point that I didn’t consider and it may be that I’m being shown the Avast folder only because it’s the first one that’s locked. That opens the chance that the problem isn’t caused by Avast but for now, I don’t have anything else to go by.

Thanks again!

Hi Lukas,
There a few other topics relating to this as well so there is something going on, because when the self-defence is disabled users have access to the windows temp folder.

@ myNameHere
The TFC cleaner program suggested by Pondus is somewhat different as is shuts everything down before it goes about its cleaning.

It looks like it was the Self-Defense feature. Not sure why I only get it on one machine but that seems to be it.

Thanks much!

You’re welcome.

If your cleanup tool tried to clean up all of the windows temp folder and its sub-folders including avast then the self-defence module would block that. But I don’t know why it would block access to other areas of the windows temp location.

I use windows 10.
Avast was updated to latest version.
I could not access C:\windows\temp
Neither could Ms SQL Server express 14 installation.
Unistalled Avast. Problem solved.
I guess i would rather be less secure that make battle with constantly new bugs in Avast.
Bye bye until a better version.

I’ve informed Avast.

No issues here with W10 and Avast Free latest version getting to c:\windows\temp

Thanks for the report,

the problem will be solved ASAP by micro update.

It would be nice to know when the fix has been applied so I can turn on the self protection feature again.
Thanks

its the 23rd of feb and no asap miro fix has come my way just fyi

Reported to Avast.

Hi,

the fix is live, please restart your PC and try again.

Had this issue, found this thread, updated Avast, problem fixed.