Cannot delete XP invalid folder.
#1
Posted 19 May 2008 - 11:33 AM
I am running a Dell 8500/80GB/1GB running Windows XP Prof.
Someone/something generated a Folder named *,jpg (the comma is real, not a typo)
The folder cannot be deleted, moved or renamed by any normal means, XP always reports an invalid file-name.
I have tried third party software such as "DelvInvFile" with no luck.
I cannot run back-up software any more as a file scan reports disc errors, so this is very serious.
MS wants $59 to try to fix it and I have have spent many thousands on buying their rotten software.
I would appreciate some real help with this one.
Thank you.
Someone/something generated a Folder named *,jpg (the comma is real, not a typo)
The folder cannot be deleted, moved or renamed by any normal means, XP always reports an invalid file-name.
I have tried third party software such as "DelvInvFile" with no luck.
I cannot run back-up software any more as a file scan reports disc errors, so this is very serious.
MS wants $59 to try to fix it and I have have spent many thousands on buying their rotten software.
I would appreciate some real help with this one.
Thank you.
#6
Posted 19 May 2008 - 12:04 PM
Hi KYCDH and welcome to the PCWorld Communities. :D
I have an idea from where you received this file but that is neither here nor there. Now, this is going to be a bit tricky but it is possible to remove. First, as Coastie suggested, try to rename the file. More than likely, any Right Click functionality is gone except for things such as Properties.
If that does not work for you, try these suggestions:
- Copy all essential files from within the folder where the affected file is located and paste them into a new folder. Once done, delete the folder with the file inside.
- With all essential files still out of the folder where the affected file is located, restart your computer in Safe Mode. When in Safe Moder, delete the folder with the file inside. If you are not sure how to access Safe Mode, follow the steps laid out within this Document {document:id=1093}.
- Write down the entire file name of the affected file exactly as you see it (account for spaces, dashes, or any characters). Open C: Prompt and navigate to the affected folder level, not the file level, and delete the file from within DOS. If you are not sure how to navigate within the C: Prompt window, please post.
I have an idea from where you received this file but that is neither here nor there. Now, this is going to be a bit tricky but it is possible to remove. First, as Coastie suggested, try to rename the file. More than likely, any Right Click functionality is gone except for things such as Properties.
If that does not work for you, try these suggestions:
- Copy all essential files from within the folder where the affected file is located and paste them into a new folder. Once done, delete the folder with the file inside.
- With all essential files still out of the folder where the affected file is located, restart your computer in Safe Mode. When in Safe Moder, delete the folder with the file inside. If you are not sure how to access Safe Mode, follow the steps laid out within this Document {document:id=1093}.
- Write down the entire file name of the affected file exactly as you see it (account for spaces, dashes, or any characters). Open C: Prompt and navigate to the affected folder level, not the file level, and delete the file from within DOS. If you are not sure how to navigate within the C: Prompt window, please post.
#8
Posted 19 May 2008 - 12:13 PM
Here's another couple of ideas...
Did you try removing the directory from the command prompt? If not, in Windows Explorer, make sure that the folder in question is not write protected. If it is, remove the write protection, then click on Start, then Run, and type CMD in the box. Type in the following format:
RD Drive:path,jpg, where Drive: is the drive letter the folder is on, and path is the full path to that folder. For example, if the folder is in the root directory, type:
RD C:,jpg
or if the folder was off of the Program Files directory, you would type the following:
RD C:Program Files,jpg
If that doesn't work, download a program called Unlocker... You can get it HERE
Follow the instructions on how to install and use it, and you should be able to delete the folder. After you do that, I suggest you get a good antivirus and spyware program and do thorough scans in safe mode.
Did you try removing the directory from the command prompt? If not, in Windows Explorer, make sure that the folder in question is not write protected. If it is, remove the write protection, then click on Start, then Run, and type CMD in the box. Type in the following format:
RD Drive:path,jpg, where Drive: is the drive letter the folder is on, and path is the full path to that folder. For example, if the folder is in the root directory, type:
RD C:,jpg
or if the folder was off of the Program Files directory, you would type the following:
RD C:Program Files,jpg
If that doesn't work, download a program called Unlocker... You can get it HERE
Follow the instructions on how to install and use it, and you should be able to delete the folder. After you do that, I suggest you get a good antivirus and spyware program and do thorough scans in safe mode.
#11
Posted 19 May 2008 - 04:09 PM
Yes mphenterprises, in fact most of the suggestions were tried before posting the original message. I am an old (70 years to be exact) DOS sys-op from days of yor with tricks up my sleeves from those days when it was easy to modify a DOS FAT to delete etc.
I find it very irritating to use a file system (in XP) which permits files & folders to be generated that cannot be altered or deleted (fixed) Security needs do not excuse such conflicts. I find it even more irritating for the author of such nonsense to ask me (the customer who paid good money for it) to pay to fix the author's shortcomings.
Clearly what is needed here is a pro-tool for modifying file code structure to fix "forbidden" structure. I would not like to cost my time & effort for formatting and re-creating this hard drive content, particularly as I cannot back it up in it's present state.
Thank you for your suggestions.
I find it very irritating to use a file system (in XP) which permits files & folders to be generated that cannot be altered or deleted (fixed) Security needs do not excuse such conflicts. I find it even more irritating for the author of such nonsense to ask me (the customer who paid good money for it) to pay to fix the author's shortcomings.
Clearly what is needed here is a pro-tool for modifying file code structure to fix "forbidden" structure. I would not like to cost my time & effort for formatting and re-creating this hard drive content, particularly as I cannot back it up in it's present state.
Thank you for your suggestions.
#15
Posted 20 May 2008 - 07:46 AM
I would not rely 100% on McAfee to secure your computer. However, since McAfee does not play well with any other security applications, the process to remove McAfee for any other application is not warranted at this point.
If I may ask, from where did you get this file?
If I may ask, from where did you get this file?
#18
Posted 20 May 2008 - 08:34 AM
Okay. I did a couple of test and here is what I determined:
- I created a test text file test.,txt and I was able to delete the file
- I created a test .jpg file test.,jpg and I was able to delete the file
You are right. Windows should not have allowed this but in both instances, I was able to delete the file.
ADDED:
I noticed that your original post reference *,jpg. I tried my experiment using this formatting and I was still able to delete the files.
- I created a test text file test.,txt and I was able to delete the file
- I created a test .jpg file test.,jpg and I was able to delete the file
You are right. Windows should not have allowed this but in both instances, I was able to delete the file.
ADDED:
I noticed that your original post reference *,jpg. I tried my experiment using this formatting and I was still able to delete the files.
#19
Posted 20 May 2008 - 11:05 AM
Is the file name literally ,JPG* (Complete with asterisk)? If so, the asterisk is the problem since it's a filename wildcard, and as such, is not an allowed filename character in either a file or a folder. I believe that a comma is allowed in naming files and folders.
Sign In
Register
Help


MultiQuote
