File that cannot be deleted

hamster143

Registry has absolutely nothing to do with it. If the file is not in use, but you still can't delete it or even access its properties, something must be wrong with the file system.

It does not matter what software you use, as long as the file system is OK. If you expect to see two different outcomes from the delete operation in Windows and in Linux, then evidently the file system is not OK, but maybe the Linux driver handles abnormal situations in a different way from the Windows driver.

Here's a simple analogy. You want to get a book off the book shelf. In the normal circumstances, books stand next to each other and can be pulled individually, and anyone can take any book without any problems.

You send your servant to that book shelf and he comes back and says "I can't get it easily, other books are in the way". Your solution is to find a more obedient servant. He'll bring you the book, but possibly at the expense of creating a big pile of books on the floor (maybe books were stacked vertically for some reason, and the book you wanted was at the bottom of the stack.) The correct solution is to send a servant to put the books in order.

hamster143

You can download a bootable USB drive with Linux on it from ubuntu.org.

caffenta

"If the file is not in use" is a big if. There is no way of easily telling if it is indeed in use, except for the fact that you cannot delete/move it. Not being able to see file properties is not necessarily a file system corruption. The program that has a lock on the file can deny any access to it, including property queries.

I agree with the rest of your post. If there is indeed a file system corruption, trying to forcibly delete it with Linux is only asking for trouble. A better way is to let Windows do a filesystem scan during the boot sequence.

But it really all comes down to this: is the file actually a problem? Or is it just some irrational need to delete it. If it's not a problem, forget about the file.

hamster143

The OP stated that the file is located in the temp folder and that he was unable to delete it in safe mode. That's a strong indication that the file is not in use.

caffenta

Not necessarily. I have a zero-length file in my temp folder that can't be deleted (it's a debug log). I'm using Win7, but XP is not that different. If I boot in safe mode and log on as myself, I still can't delete it. If I log on as another user with administrator privileges, I can delete the file. But guess what? The file is right back when I reboot and log on under my normal account because the program recreated it.

I'm not sure the OP has tried the "log on as an another administrator" method that rcgldr suggested:
Being an administrator doesn't mean that he was logged on as another administrator.

JaredJames

As has been pointed out before, the file can appear to be in use when it isn't. So you can't do anything with it.

I've had it a number of times where a program has an error (whether internal or simply crashes - even no error appearing to exist) and it has maintained file locks even though the file is no longer in use.

There was a common error I kept having with media player where the player would be closed but the files were untouchable - the error was it was showing as media player still using them, even after checking it wasn't running anywhere.

Given it's the temp folder and it's been checked it isn't running, this to me would be the most likely cause.

As I said before, given its location (with the nature of this folders use) it doesn't seem to be a likely file system corruption. Again, anywhere else and I'd be questioning it or with a number of instances within the temp folder.

When you diagnose the fault you have to take these factors into account.

Here is a site outlining everything we've discussed here, but they've also mentioned using the prompt: http://winhlp.com/node/39

mathman

Update on bad file. The name of the file seems to be far too long (over 150 characters) to be handled. Furthermore the "type" has about 40 characters. I suspect these factors are the cause of the problem, and the file itself is probably not corrupted.

mathman

I raised the same question on another forum and after many back and forths someone was able to supply a very simple solution that worked! The obstacle to deleting the file was that its name L.asp* has far too many characters.

The essence was to use the concept of a virtual folder as follows. Here I am displaying the original recipe and my changes.

subst P: "c:\Documents and Settings\Herb\Local Settings\Temp"
P:
attrib -r -a -s -h P:\filestart*.ext (my note - I did not need this step)
del filestart*.ext (my note - del L.asp*)
C:
subst P: /d

zalathel

Try with LongPathTool. I should help in your case, it helped me in a similiar problem :)