Hot answers tagged


Download 7zip, its file manager can delete them. Invaluable if you use something like Cobian Backup, which has a nasty habit of creating long paths... From comments: If you're still having trouble make sure you're using shift+del. This is because windows tries to move those files to the Recycle Bin.


None of the other (free) answers here worked for me, but I found one on another site: rimraf <dir> rimraf is a Node.js package, so you will need to install Node.js which includes npm. Then you can run: npm install -g rimraf Then you can run rimraf from the command line. I found this solution because npm itself was causing this problem due to the ...


If you have rm from GNU coreutils (most probably if it's a regular Linux distro), rm -rf / will be refused by the built-in protection (according to manpage and Wikipedia, haven't tried that). You can override this protection with --no-preserve-root. rm will then remove everything it possibly can, without stopping after having attempted to remove every ...


unlink -rf Or rm -- -rf


cd to/dir/where/you/want/to/start find . -type d -name '.svn' -print -exec rm -rf {} \; Use find, which does recursion in the current directory . filetype is directory filename is .svn print what matched up to this point (the .svn dirs) exec the command rm -rf (thing found from find). the {} is a placeholder for the entity found the ; tells find that ...


The best delete tool that (little) money can buy: EDIT: To counter the detractors No one mentioned the need for government level security, so arguments with that objective are pointless goalpost shifts. This is good enough for anyone who isn't James Bond or Bruce Wayne. P.S. Governments sanction shredders. What is a hammer but a high velocity shredder? ...


It's possible that by upgrading, the old XP user was not converted well to Windows 7 - therefore these files are owned by a phantom user. You can follow the steps below: Take ownership of the files. Start a Command Prompt (cmd) as an administrator, and enter: takeown /f file takeown /f directory /r Give yourself full rights on the file: cacls file /G ...


If you are like me and don't like to install additional software to fix a problem like this, I'd go with XQYZ's suggestion and use robocopy to solve the problem. (In my case the problem was created by robocopy in the first place, by copying a directory which had recursive junction points in it without supplying /XJ to robocopy). To delete the directory ...


I believe I've found a way to delete things from cmd. Originally I tried the del command, but that didn't work. Then I remembered rmdir. Doing the following: rmdir /S /Q <dir> seems to have worked.


Another option: rm ./-rf ... asuming your current directory is the one where the file resides.


Heath Stewart's The Patch Cache and Freeing Space on MSDN blogs explains in detail. An excerpt: [..] cause the Windows Installer service to cache any of the original files being replaced into the baseline cache. [..] It is this baseline cache that consumes a lot of drive space on the system drive after installing [..] The baseline cache facilitates patch ...


I think it should be safe to remove the files, provided you're able to download them again in future if they're needed or if you have access to your original install disks. I had something similar on my computer, I just deleted it and install things from the original disk every time it asks me now. Inconvenient, yeah; but I don't often install stuff and it's ...


For those who like to do stuff like this visually while listening to techno music. Running rm- rf on Linux (video) Bonus points if you can name the processes as they start dying.


Do you have a virus scanner that does on-access scanning? Disable it during your delete action. With my virus scanner disabled deleting is over 10 times faster. (I never understood why it checks files that are about to be deleted)


This is actually quite simple to fix. Say that the directory structure is as such: C:\Dir1\Dir1\Dir1\Dir1… To fix it, just rename each folder to a one-character folder-name until it is no longer too long to delete: Rename C:\Dir1 to C:\D Navigate to C:\D\ Rename C:\D\Dir1 to C:\D\D Navigate to C:\D\D\ Goto 1 until total length of path is <260 ...


You can’t delete the root nodes. They don’t physically exist. You can, however, delete their contents, via Regedit (as opposed to reg). Regedit hangs as soon as I try to delete HKLM\SYSTEM. After resetting the VM (because I’m lazy), I get the following screen (OS is Windows XP): (“Windows could not start because the following file is missing or corrupt: \...


Go to /Users/YOUR_HOME_FOLDER/Applications and delete the folder Chrome Apps.


Windows keeps an 8.3 file name for every file to ensure compatility. So if you have the files test1.ext test2.ext test3.long the last file gets stored with the alternative name TEST3~1.LON thus matching the pattern *1.*. You can execute dir /x to see all 8.3 file names. Fixes: To strip all files in the directory directory of their 8.3 name, ...


Alternatively you can always edit the directory its in and remove the file that way. vim . and then just delete the line with the file on it (using D, dd won't work).


For Windows: Deny "Delete" permission on the file. Remove or deny "Delete child items" permission on the parent directory. For Unix (including OS X): Remove "Write" permission on the parent directory. Note that this will only prevent the file from being removed (deleted), but won't do anything against accidental truncation or overwriting with garbage....


You can do this using del and the /S flag (to tell it to remove all files from all subdirectories): del /S C:\Path\to\directory\*


Found the solution. It is as simple as the last step from the commands I wrote here. I.e. VBoxManage clonehd fullpath/{uuid-of-last-snapshot}.vdi thedisk-full.vdi So I should clonehd only the last snapshot, not every snapshot from the chain. And it is thousands percent faster. The uuid can be found from VBoxManage list hdds | grep VmName | tail In the ...


del is for deleting files, rd aka rmdir is for deleting folders, so... rd /s "\\?\C:\1\2\Favorites\Wien\What To Do.." ...should do the job! :-) The /s parameter removes all directories and files in the specified directory in addition to the directory itself. Used to remove a directory tree. If this doesn't work; even not with wildcards/...


It depends on who your adversary is. If it is a casual user, e.g. friend/coworker/spouse/etc., then preventing regular undelete is good enough: format the flash drive, then fill it with random/non-private files till it's 100% full, then format the flash drive again. Your original sensitive data will be gone for good, and unrecoverable using undelete tools or ...


The command line arguments for taking ownership should be in this order takeown /f <directory> /r /f filename or directory name pattern /r recurse NOTE: cacls is now deprecated, please use icacls icacls <directory> /grant <user>:f /t f full access /t recurse


A generic technique for deleting weird filenames is to use. ls -li to find the inode number of file and then use. find ./ -inum <number of file> -delete No need to remember all the special cases.


In Linux you could create a hard link to it. Then you can write to it and "delete" it, but you'll be only removing the reference in your directory. The other hard-link will still point to the file's contents, so it won't have been deleted anyway. In Unix world, you don't "delete" files. You just decrease the number of hard links to it. When nothing else is ...


For a nice GUI tool, there is File Shredder. With File Shredder you can remove files from your hard drive without fear they could be recovered. There are quite a few software tools today for retrieval of deleted files under Windows OS. Those tools, often referred to as "file recovery" software, are taking advantage of shortcoming of ...


Set up a VM and try for fun? It'll go quite far... if you're using a gui you might have fun noticing things degrade more visibly. (icons on menus stop loading etc.) If you let it go, the OS will pretty much be beyond recovery though you may be able to get some data back easily. Either way, you'll be wanting to do a reinstall of the OS.


Just drop from Powershell into command by running below: Cmd /C "rmdir /S /Q <dir>"

Only top voted, non community-wiki answers of a minimum length are eligible