Folder won't Delete - ARGH

Since this has not been mentioned, Maybe try downloading Eraser and right click--> erase file. this program overwrites files to delete them.

Eraser

Edit: erase "folder" I mean (I knew it was a folder...) Hope this helps

Another Edit: This program can also erase previously deleted files. by erasing the non-used space on the hard drive, it overwrites all previously deleted information. files/programs/folders/ everything under the sun......

yes Eraser is an awesome program. you should change your avatar to a smiley face avatar now. Glad your problem got resolved. And quoting a webpage: What can the command RMDIR?

/S Removes all directories and files in the specified directory
in addition to the directory itself. Used to remove a directory
tree.

/Q Quiet mode, do not ask if ok to remove a directory tree with /S

JerometheGiraff said:

The problem has been solved and the folder has been deleted :)

I want to thank Arkhi for his command prompt (DOS) commands that I had not known about which I have to ask what does the codes /q /s after rmdir do, I hope Arkhi can answer :)

And I'd also like to thank Thorsen for the Eraser program suggestion :)

And finally thank you to everyone who pitched in to try to solve this problem, thanks again :)

NP. What did you do exactly? =P

We'll try using the command prompt again. Open an administrative command prompt.

*Go to the directory it is located.
[ cd /d C:\Users\<account name>\Rogue\Desktop]

->wait, isn't your username Rogue? XD

*now type [ dir /x ]. This displays the shortname of files.

*now use rmdir if it's a folder, or del if it's a file to remove it using the short name

[e.g: rmdir /q /s FILEORFOLDER~1 ]
Folder - Delete from Command Prompt
File - Delete from Command Prompt

Thank you lab130 for the suggestion as to how to eliminate a nuisance empty file that I could not delete from my desktop. This worked great & I appreciate it.

I had the exact same issue! I did not do half of the troubleshooting steps because I wasn't able to, but the one that worked was the following DOS commands (I starred out some of the personally identifiable information):

dir /x

Volume in drive C has no label.
Volume Serial Number is ****-****

Directory of C:\Users\***********\Desktop

11/16/2012 09:54 AM <DIR> .
11/16/2012 09:54 AM <DIR> ..
11/16/2012 09:41 AM <DIR> LSV-CS~2.PER lsv-cs-***01 *****_staff_ws ****_staff_ws ******* ***********. Personal Folders Personnel who
11/16/2012 09:54 AM <DIR> NEWFOL~1 New Folder
0 File(s) 0 bytes
4 Dir(s) 2,077,152,612,352 bytes free


rmdir /q /s LSV-CS~2.PER

I could only remove the folder through its short name. I couldn't rename it, move it, copy it, etcetera.

I found out the cause of my folder issue.

I have a script that creates a folder based on a file path. Well some file paths are long so I cut it off at 50 characters long. I then added a "..." to the send of the folder so that people can understand that the folder name is not representing that full file path.

Well Windows does not like folders that end with a period. It is interesting that the windows scripting language (vbscript) allows you to create a folder that way

This thread is still useful. I had the same problem and Google pointed me here :)

My problem seemed to be that the folder name was too long and Windows Explorer had problems with that. I was able to delete the folder in DOS using rmdir and then the short name of the folder, which I determined with dir /x (e.g FOLDER~1).

Thanks for the tips everyone.

May be of interest.

Bitdefender uninstalled from Win 8.1 64 left a Bitdefender folder and files in Program Files and another folder and files in AppData\Local\Temp.

I noticed this after seeing Bitdefender processes running after the uninstall.

Tried the following:

1. LockHunter: no success and tedious reboots.
2. FileASSASSIN: no success and tedious reboots.
3. Wise Force Deleter: Removed files but could not delete folders.
4. Command line: no success - no access report.
5. Boot from a Linux live DVD, as suggested in a previous post: immediate success.

I did not try booting in safe mode as I had a Linux DVD at hand and needed to get done and move on.