Directory and files there but can't delete, move or rename

Ztruker said:

That was it, needed the 64 bit version. Installed it and was able to delete the folder..... Many thanks

Glad you got it. :)

I tried Take Ownership manually and via the context menu entry but it had no effect.

I don't know what was wrong or how it got messed up, I'm just happy it's gone. If I run across another I'll try again to figure out what the real problem is.

gregrocker said:

I wonder what else Unlocker does besides take ownership and delete. I want to see if it makes deleting the Windows folder easier.

I think one of the techniques it uses is the RunOnce registry key. When it asks if you want to mark a file for deletion that can't be deleted on the spot, it puts the delete command in RunOnce. It fires before the Windows logon. You can do stuff like deleting index.dat files using RunOnce.

In this case, the folder was deleted without having to reboot so there is something else Unlocker does that manually deleting or using LockHunter did not do.

Ztruker said:

In this case, the folder was deleted without having to reboot so there is something else Unlocker does that manually deleting or using LockHunter did not do.

The main function is to close handles held by other processes. That's what gives the "file is in use by another process" error. Explorer is especially notorious for not letting go of files even though it is done using them.

FliGi7 said:

MilesAhead said:

gregrocker said:

I wonder what else Unlocker does besides take ownership and delete. I want to see if it makes deleting the Windows folder easier.

I think one of the techniques it uses is the RunOnce registry key. When it asks if you want to mark a file for deletion that can't be deleted on the spot, it puts the delete command in RunOnce. It fires before the Windows logon. You can do stuff like deleting index.dat files using RunOnce.

RunOnce programs don't run until user logon.

My guess is that the file unlocker programs run as SYSTEM to close file handles, which makes it more effective at getting rid of the locks.

I think you are mistaken. Here's the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce

I use a program started by that key to delete index.dat files. If they were locked as they would be after login, it would not work. Also I get a long pause before I get the desktop. Another indication it's running before login.

I think we're getting tangled up with 2 different scenarios. One is if it deletes the file immediately. The other is marking it for deletion on next boot. The on next boot scenario is where is uses RunOnce.

Anyway, this is all speculation. If you want to know run Unlocker under a monitor or debugger.