Windows takes more time than usual to know that an executable file has been closed or is not used

Question

Okey my fault, only my fault.

Trying to speed up an old laptop, I searched for registry tweaks and perform many of them on this computer. Windows 7 Enterprise, 64 bits.

I found some of this tweaks were not really good things. For example, one of them cause, hanging application to automatically close. Or other behavior was that under low memory conditions it automatically closed apps.

So I went and tried to reverse them and apparently it did.

But my computer is still having a very strange behavior. I'm going to try to say it in a single phrase: it takes more time than usual for windows to know that an executable file has been closed or is not used.

For example, I have a batch file that compiles a file (Delphi), then compresses it, then signs it, all via old good MSDOS command batch. This started to behave strangely, now after copying the file, many times I get access denied errors to that file. At first I thought it was either the antivirus, or antimalware, or the VCS that was locking the newly created files, but not, I have stripped the computer of those software and the problem persist.

Another example, I put executable "dummy.exe", say a standalone executable built in Delphi, in directory "c:\mydirectory". I execute the file, than close it. Then I tried to delete the file and Windows tells me that I can't, that the file is open... but it is not, I closed it. I just wait a couple of minutes, try later and now it works.

What missing or changed registry key could be causing this behavior?

EDIT 1:

Using Sysinternal's Handle, I found the process blocking my file was the PID:4, which is the NT Kernel and System.... so, what is really going on here !? :(

EDIT 2:

I think I'm sure what is the problem, but still don't know how to fix it. I remember some "tweak" was related to UAC. The file was just created by Delphi running as Administrator, if I run the Command Prompt as administrator and run my batch to copy/aspack/sign it works smoothly. It is when I run the batch directly by double clicking the batch file that the locking is fired.

Also, there's still the other weird. A newly created folder in which I drop and executable (say notepad.exe), then run it, then close it, keeps locked and can't be deleted. This is not normal, I just checked in a few other computers.

EDIT 3:

I can confirm that just by opening the Windows Explorer and have it "viewing" the directory where my exe and batch resides (even if I run my batch directly from a previously opened CMD prompt session), it causes the files to being locked and get: "The process cannot access the file because it is being used by another process." So, it is the Windows Explorer viewing my files, which causes this lock..... but again,why? And Windows Explorer extension could be? I have Mozy backup and use Tortoise for version control, both have installed items under "File" menu.

Answer 1

The problem was caused by disabling the service Application Experience. After enabling it again, everything works as it should. :)

Thank you very much for helping troubleshooting this one. The use of "Handle" was very helpful, cause it helped me to narrow down the exact moments where the files were being locked.

This is where I find the clue to solve this problem: http://social.msdn.microsoft.com/Forums/office/en-US/40f15ae2-017d-4101-aff8-3981964addb3/error8-unable-to-copy-file-objdebugxxxexe-to-bindebugxxxexe-access-to-the-path?forum=visualstudiogeneral