Why won't XP allow me to rename/delete files?

[Igor]

I recently switched over from Windows 98SE to XP (was on SP2 and for a
while, then upgraded to SP3). There's a recurring phenomenon in XP
that's been puzzling me. Sometimes when I try to edit a folder name,
move a folder, or delete a file within a certain folder, I get a
message telling me that it cannot be done because the file is "in use
by another person or program." This can go on for days, sometimes even
after a reboot. Thing is, it _can't_ be in use by another person,
since there's only one account on this computer, and I'm not running
any applications that could be using the file.

Does anyone have an explanation for this, and what I can do to stop
it?

 

[Jason]

I get the same problem with deleting files and directories. The strange
thing is I can sometimes rename the parent folder (directory). I can't
remember whether I've renamed files though.

 

[Jim]

I recently switched over from Windows 98SE to XP (was on SP2 and for a
while, then upgraded to SP3). There's a recurring phenomenon in XP
that's been puzzling me. Sometimes when I try to edit a folder name,
move a folder, or delete a file within a certain folder, I get a
message telling me that it cannot be done because the file is "in use
by another person or program." This can go on for days, sometimes even
after a reboot. Thing is, it _can't_ be in use by another person,
since there's only one account on this computer, and I'm not running
any applications that could be using the file.

Does anyone have an explanation for this, and what I can do to stop
it?

Files may be in use by processes other than your own. Contrary to what some
believe, your personal process is not the only process that can and does
run.
Use Process Explorer to find out which process has a handle to a given file.
You will need to search the internet for this program.

Jim

 

[Igor]

Files may be in use by processes other than your own. Contrary to what some
believe, your personal process is not the only process that can and does
run.

That much is obvious, though you'd think in an OS as otherwise
polished as XP they'd have found a way to run these processes in a
manner that wouldn't interfere with the user's processes.
Moving/renaming/deleting files and folders is about as basic and
common a task as one can do with a computer, and it's rather
surprising that the most popular desktop OS would have problems in
this department.

Use Process Explorer to find out which process has a handle to a given file.
You will need to search the internet for this program.

Thanks. Will check it out.

Do you have any idea if there's a way to disable these hidden
processes from the get-go so that I wouldn't have to use a third party
program to cancel them? Just what the hell is Windows doing with a
folder for days on end anyways?

 

[Jim]

That much is obvious, though you'd think in an OS as otherwise
polished as XP they'd have found a way to run these processes in a
manner that wouldn't interfere with the user's processes.
Moving/renaming/deleting files and folders is about as basic and
common a task as one can do with a computer, and it's rather
surprising that the most popular desktop OS would have problems in
this department.


Thanks. Will check it out.

Do you have any idea if there's a way to disable these hidden
processes from the get-go so that I wouldn't have to use a third party
program to cancel them? Just what the hell is Windows doing with a
folder for days on end anyways?

You need to determine which process has a handle to the subject
files/folders. Only then can anybody how (or if at all) you can proceed.

The only time that I had such a problem was when spybot's Teatimer program
caused some system process to put a hold on the HOSTS file. This instance
is not Windows fault.
The spybot people are well intentioned, but as I wanted to edit the file,
they did interfere with me. The solution in this case is not to run
Teatimer.

Jim

 

[Twayne]

I recently switched over from Windows 98SE to XP (was on SP2 and for a

while, then upgraded to SP3). There's a recurring phenomenon in XP
that's been puzzling me. Sometimes when I try to edit a folder name,
move a folder, or delete a file within a certain folder, I get a
message telling me that it cannot be done because the file is "in use
by another person or program." This can go on for days, sometimes even
after a reboot. Thing is, it _can't_ be in use by another person,
since there's only one account on this computer, and I'm not running
any applications that could be using the file.

Does anyone have an explanation for this, and what I can do to stop
it?

Yes, but from the look of some of your responses, the answer has to meet
your own criteria and have a solution that you create, which disconnects
it from reality.

There are other users, regardless of how many accounts you have.
First, you have local and network services using some files (network
includes internet).
System is a user, as are you, Administrator, probably ASPNET, Help
Assistant and possibly things in the SUPPORT category to name just a few
possiblities. There are a lot of other possibilities too; way too many
to list or guess at since I can't see your machine from here.

"in use by another person" can sometimes mean any/all or none of the
above or something else entirely. It depends.

many programs that start up at boot time have files they are using in
order to be ready for use for you or to perform background tasks you
wish to run such as indexing, tasks set to run during idle times, OS
files necessary to keep windows running, all kinds of things.
What you need to do is track down WHO/WHAT started and is using the
file in question. That's been given in other posts so I'm not repearing
it here.

To help yourself, provide a LOT more information such as:
OS/version (XP what; HOme? Pro?)
The problem filename
Path to the filename
The exact, complete error message.
And whatever else you think might be relevant.
Sometimes you just have to help others to help you. A file in use
simply can not be deleted/pasted/copied/moved/written to quite often.

Here's an example of what NOT to do: to move the My Documents folder.
Create a My Documents folder on another drive, wherever ýou'd like it.
Copy all the files in the current My Documents folder over into the new
one. Start using it.
That won't work. You won't be able to Delete the old My Documents
folder. Even if it appears deleted, it'll just come right back into
existance. It's in use. You must you the MOVE button in My Documents
Properties in order to relocate it since it's a system folder and in
use. It'll look like you moved it; but you didn't. You only copied hte
data to somewhre else and the old location is still whre the system will
look for it.

HTH

Twayne

 

[Igor]

The only time that I had such a problem was when spybot's Teatimer program
caused some system process to put a hold on the HOSTS file. This instance
is not Windows fault.
The spybot people are well intentioned, but as I wanted to edit the file,
they did interfere with me. The solution in this case is not to run
Teatimer.

Ah, OK. So it might not be a problem with Windows, it could just be a
problem with a program I've installed.

I'll install that program you mentioned so I'm ready the next time it
happens.

 

[Igor]

To help yourself, provide a LOT more information such as:
OS/version (XP what; HOme? Pro?)
Pro.

The problem filename

No filename. In this last instance, it's a folder I created to store
files I downloaded off the net. I was simply trying to rename the
folder.

There are no system files in the folder. There are no program files in
the folder. The folder was not one created by a program to store its
files in.

Path to the filename

C:\Documents and Settings\default\My
Documents\documents\articles\recording\mixing

The exact, complete error message.

I can't provide more than what I have since I was just able to rename
the folder. Still, I'd like to get to the bottom of this since I have
no doubt it'll happen again.

And whatever else you think might be relevant.

Nothing that I can think of. If I had a hunch as to what might be
causing this, I'd be exploring it instead of asking on this newsgroup.

Sometimes you just have to help others to help you. A file in use
simply can not be deleted/pasted/copied/moved/written to quite often.

Neither the folder nor the files in the folder were in use by any
application that I was using.

 

[beamish]

No filename. In this last instance, it's a folder I created to store
files I downloaded off the net. I was simply trying to rename the
folder.

There are no system files in the folder. There are no program files in
the folder. The folder was not one created by a program to store its
files in.


C:\Documents and Settings\default\My
Documents\documents\articles\recording\mixing


I can't provide more than what I have since I was just able to rename
the folder. Still, I'd like to get to the bottom of this since I have
no doubt it'll happen again.


Nothing that I can think of. If I had a hunch as to what might be
causing this, I'd be exploring it instead of asking on this newsgroup.


Neither the folder nor the files in the folder were in use by any
application that I was using.

Hello,
This free application may help.
http://ccollomb.free.fr/unlocker/

take care.
beamish.

 

[Igor]

Hello,
This free application may help.
http://ccollomb.free.fr/unlocker/

That's the ticket! Thanks.

To the earlier poster who was asking for the text of the error
message, this was the *exact* message:
http://ccollomb.free.fr/unlocker/example.png

 

[N. Miller]

That much is obvious, though you'd think in an OS as otherwise
polished as XP they'd have found a way to run these processes in a
manner that wouldn't interfere with the user's processes.
Moving/renaming/deleting files and folders is about as basic and
common a task as one can do with a computer, and it's rather
surprising that the most popular desktop OS would have problems in
this department.

I have only run into this problem under certain, specific circumstances.

I.e., download images from the Internet, using a web browser, and managing
the images in a photo program, such as HP Photosmart Premiere. If I decide I
needed a different folder name, the browser may still have a handle on the
folder, and I can't change the folder name until I close the browser.
I.e., I want to change a folder name, and have a file open which is
contained in that folder. Windows XP won't let me rename the folder until I
have closed the open file, which is contained in the folder I am trying to
rename.

Thanks. Will check it out.

Do you have any idea if there's a way to disable these hidden
processes from the get-go so that I wouldn't have to use a third party
program to cancel them? Just what the hell is Windows doing with a
folder for days on end anyways?

I've never encountered "hidden processes" blocking folder renaming. Depends
upon what sort of memory resident background applications you have opted to
set up. I just don't know of any native MSFT apps, running in the
background, which might cause this issue.

 

[N. Miller]

No filename. In this last instance, it's a folder I created to store
files I downloaded off the net. I was simply trying to rename the
folder.

Close your browser, then try to rename the folder.

 

[Igor]

Close your browser, then try to rename the folder.

That was one of the first things I tried. It didn't help.

 

[Igor]

I've never encountered "hidden processes" blocking folder renaming.

Then consider yourself lucky.

I just don't know of any native MSFT apps, running in the
background, which might cause this issue.

Well, thanks for informing me that you don't know anything that could
assist me in resolving this problem. Generally, when someone doesn't
know the answer to a question, he doesn't try to answer it, but don't
let that stop you.

 

[Igor]

Anyone ever notice how the most long-winded responses are usually the
ones that have the least substance, while the ones that actually
contain useful info are just a few sentences short?

I guess there's some truth to the adage that it's the empty can that
rattles the worst.

 

[Olórin]

Anyone ever notice how the most long-winded responses are usually the
ones that have the least substance, while the ones that actually
contain useful info are just a few sentences short?

I guess there's some truth to the adage that it's the empty can that
rattles the worst.

There are plenty of lengthy replies in this group that are long because they
contain much information and detail many steps needed for OPs to try. I
personally wouldn't write off, or sarcastically belittle, any poster who was
genuinely trying to help (or even just relevantly adding to a discussion).

 

[VanguardLH]

I recently switched over from Windows 98SE to XP (was on SP2 and for a
while, then upgraded to SP3). There's a recurring phenomenon in XP
that's been puzzling me. Sometimes when I try to edit a folder name,
move a folder, or delete a file within a certain folder, I get a
message telling me that it cannot be done because the file is "in use
by another person or program." This can go on for days, sometimes even
after a reboot. Thing is, it _can't_ be in use by another person,
since there's only one account on this computer, and I'm not running
any applications that could be using the file.

Does anyone have an explanation for this, and what I can do to stop
it?

One of the blunders that I've seen most often is that the user has a
subfolder or file highlighted (selected) under a parent folder. They
then right-click on the parent folder to delete it. However, they still
have that subfolder or file selected. That means YOU (in the guise of
explorer.exe which is managing your desktop GUI) has a handle on this
file. You will need to change your selection so the parent folder (or
one above it) is selected and then you can delete that folder. The
folder was inuse because you had a subfolder or file under there
selected.

While there are open handle (oh.exe) utility in the W2K resource kit
(part of which is free from Microsoft's FTP site), a similar
command-line utility from SysInternals, and the Process Explorer from
SysInternals that can show you what process or object has control over
the file that you are trying to delete but can't, I use Unlocker which
detects the conflict and pops open to show you who has a handle on the
file. You can then either exit that application or have Unlocker try to
remove the handle (http://ccollomb.free.fr/unlocker/; free).

If explorer.exe (your desktop GUI) is the one with a handle to the file,
and instead of using Unlocker, you open Task Manager and kill the
explorer.exe process. Your desktop disappears. Then use File -> New in
Task Manager to run cmd.exe to get a command shell. Then use DOS
command to delete the file. Then use File -> New in Task Manager to run
explorer.exe and your desktop GUI reappars. That way, you unload
explorer.exe to remove its handle to your problematic file.

 

[Mike Tm]

Anyone ever notice how the most long-winded responses are usually the
ones that have the least substance
(...) it's the empty can that
rattles the worst.

Igor.
While in fact you might be right, it seems to me to be unwise to
criticize posters in such generalized way.
If indeed someone seems to annoy you, there is an appropriate way to
give him feedback: the personal e-Mail.
This approach seems to be by far more diplomatic, comply to the
netiquette, and the results can be much more in your interest.

Best
Mike

 

[N. Miller]

On Mon, 22 Sep 2008 03:58:51 -0700, "N. Miller"

Then consider yourself lucky.

It is not luck, that I know of.

Well, thanks for informing me that you don't know anything that could
assist me in resolving this problem. Generally, when someone doesn't
know the answer to a question, he doesn't try to answer it, but don't
let that stop you.

It is also good form not to gripe about responses from people who offer
them. I might just be inclined to put your ID in the "ignore" list, and
never respond to your pleas for assistance again.

 

[Jason]

I've installed Windows onto another drive and booting into that installation
and still can't delete files and folders on the HDD that is no longer being
used.