Windows 7: Files can't be deleted

Yes, I've googled. Many, many times over the past year.


I am constantly running into issues trying to delete files--mostly .exes. It really interferes with many "autoupdate" programs like Steam and Origin. I have to use safemode to install updates... It also affects other things like compiling; I get occasional (essentially random) errors when the output file already exists and I want to overwrite it. I also can't delete the affected file(s) for a long time--often upwards of 1 minute. However, if I wait long enough, I can eventually delete the files.

The error is always something like "you don't have permission blahblah." I have tried those unlocker programs, and while they can sometimes delete the file, an autoupdater (for example) can never actually write the new copy, even though I don't see the file in the directory.

I have tried running programs as administrator.
I am using an administrator account.
I have UAC disabled.
I am not running an antivirus or any program that should be interfering.
I've tried changing folder permissions as per multiple guides I have read (some from this site).
None of the above does anything..




This problem has been plaguing me for almost 1 year. I have reinstalled Windows 7 twice in that time, and the problem exists from the get go. I have been using Windows 7 for over 2 years, but I never had this problem until my second to last installation. I don't know what changed.

Please help!



here's a hijackthis log so you can see apps I have running:
Logfile of Trend Micro HijackThis v2.0.4 Scan saved at 5:14:56 PM, on 12/31/201 - Pastebin.com

are you have try using unlocker to delete that file?

Unlocker will either:
1) Delete the file, but the program trying to overwrite the file will still fail to overwrite the file, despite the file not being visible in explorer.
2) Fail to delete the file.

In either case, Unlocker says there is no program "locking" the file, which is not typical for "typical" locked files (i.e., still open from a crashed program or whatever).



Even if Unlocker (using Unlocker 1.91 btw) DID resolve this issue, I would not consider that an acceptable solution.

bump