A
aramis62
OS: Windows XP Pro
Problem: I download an mp3 or video file to the desktop. I then try
to rename, delete, or move the file (without having ever opened it),
but can't b/c windows says "It is being used by another person or
program." I have administrator privileges, and I'm the only one
logged on.
I have been reading several posts about this, and it appears that it
is a genuine bug in Windows XP. Apparently, the other person or
program is none other than explorer.exe, the freakin windows shell.
The "fix" that people quote is:
1. open a command prompt (dos window)
2. goto task manager, kill explorer.exe
3. delete, rename, or move the file using the command line
4. restart explorer.exe via "New Task" in the task manager
This is hardly a fix in my book. This problem is so frustrating that
I'm actually considering going back to Windows 2000. There is one
other fix that I've seen quoted: using Process Explorer (from
www.sysinternals.com), find all and kill all handles to the file, then
proceed as usual. This would be acceptable except that there are
sometimes 50 or so handles to the same file, and no easy way to kill
all of them at once. At this point, it's easier to do the command
line trick.
Does anybody know of another method? Microsoft reps, will there be a
patch or update for this sometime soon?
Thanks,
aramis62
Problem: I download an mp3 or video file to the desktop. I then try
to rename, delete, or move the file (without having ever opened it),
but can't b/c windows says "It is being used by another person or
program." I have administrator privileges, and I'm the only one
logged on.
I have been reading several posts about this, and it appears that it
is a genuine bug in Windows XP. Apparently, the other person or
program is none other than explorer.exe, the freakin windows shell.
The "fix" that people quote is:
1. open a command prompt (dos window)
2. goto task manager, kill explorer.exe
3. delete, rename, or move the file using the command line
4. restart explorer.exe via "New Task" in the task manager
This is hardly a fix in my book. This problem is so frustrating that
I'm actually considering going back to Windows 2000. There is one
other fix that I've seen quoted: using Process Explorer (from
www.sysinternals.com), find all and kill all handles to the file, then
proceed as usual. This would be acceptable except that there are
sometimes 50 or so handles to the same file, and no easy way to kill
all of them at once. At this point, it's easier to do the command
line trick.
Does anybody know of another method? Microsoft reps, will there be a
patch or update for this sometime soon?
Thanks,
aramis62