Windows 7 Lock Folders / Access Denied

[Medyo]

Anybody have a freaking clue on the real fix for those access denied permission errors on folders or files on Windows 7? I am not taking about system files but even just regular personal files that I have. Each time I do a search for solutions all I get is the fix about taking ownership of folders and giving myself full control. Another one I found is using an unlocker utility to remove whatever locks exists on the files or folders. Both work, but they are not permanent fix.

I am losing my mind on determining where the issue is and to prevent it from even happening rather than fixing it each time it happens. My gut feeling is that somehow those files or folders get attached to some process and that process running is what is preventing me from deleting them. Now I can search the PIDs and find out but that is not a permanent fix either. I say this because sometimes I just let that folder be and then wait 5 minutes or reboot my machine and then I am able to delete them, without even bothering with the permissions.

It is a security feature, I know, but I DON'T WANT IT. It causes more issues for me than saving me from doing something stupid. I am a technical person but obviously not that technical to be able to fix this myself. Can someone please explain to me the logic behind this and how I can prevent it from even happening?

 

[R_1]

I boot to linux on usb and delete the files from there.
linux does not care for any windows permissions, and whatever process that is locking will not be running.

 

[Medyo]

I boot to linux on usb and delete the files from there.
linux does not care for any windows permissions, and whatever process that is locking will not be running.

That's what I am trying to avoid. Those fixes work but they really are more like a band aid. I am after preventing it from even happening.

 

[R_1]

I boot to linux on usb and delete the files from there.
linux does not care for any windows permissions, and whatever process that is locking will not be running.

That's what I am trying to avoid. Those fixes work but they really are more like a band aid. I am after preventing it from even happening.

I understand but without having any idea what the issue is, a reinstall would be in order, which being a PC repairman for 2 decades is the most boring/hated thing in the universe to me. after 10000 manual installs you would be over it too

unless its a recent addition to windows 7 it is not a security feature if you are administrator, that is a faulty product.

 

[Medyo]

I boot to linux on usb and delete the files from there.
linux does not care for any windows permissions, and whatever process that is locking will not be running.

That's what I am trying to avoid. Those fixes work but they really are more like a band aid. I am after preventing it from even happening.

I understand but without having any idea what the issue is, a reinstall would be in order, which being a PC repairman for 2 decades is the most boring/hated thing in the universe to me. after 10000 manual installs you would be over it too

unless its a recent addition to windows 7 it is not a security feature if you are administrator, that is a faulty product.

For someone with two decades of experience you still need to brush up on your technical know how. I understand the desktop support guys' approach of re-imaging or re-installing the OS, it's faster and you won't have to do some thinking. Hence, I also understand how that can be a lame excuse that 'techies' use to hide behind the fact that they don't know what they are doing.

It's not a faulty product; that's a statement that will fly on a regular user but to another I.T. person who knows what he is doing that is a stupid remark. You can re-install the OS again and it will do the same thing. Google "junction points", "Windows 7 permissions", and "Windows 7 Access Denied" phrases and you will know how typical that problem is. Many people provide solutions, but all of them are band aid fixes. I want to go deeper and figure out the security architecture behind it to figure out how to bypass that feature.

 

[ex_bubblehead]

Alright, that's enough of the name calling and off-topic bickering. Stick to the topic. Next one gets some time off.

The only acceptable response to this post is "I have read and understand the warning"