Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This question already has an answer here:

I was running a node script that went awry and created a folder structure like so:


This is nested to an extent of over 300 times, I would estimate, if not more.

I cannot del it because it is too long a file path.

I cannot use robocopy because it actually freezes around this point:

I cannot use FileAssassin as it is only for files apparently.

I have tried using the .bat script from this answer How do I delete a folder which is nested quite deep and avoid "File name too long"? , and it is still running, but I fear at the level of recursion that the folder is at even if every single subfolder was renamed to one character it would still be longer than 260 (or whatever the limit is).

How do I remove this problem from my filesystem?


DeepRemove is successful! Victory! 3,421 levels of recursion. Jeesh! I'll be more careful with nodejs (or any programmatic modification of the filesystem) from now on, esp. when recursion is involved!

share|improve this question

marked as duplicate by DavidPostill, mdpc, Scott, BlueBerry - Vignesh4303, Moses Oct 27 '15 at 18:39

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

Did you try deleting the root folder? – and31415 Feb 16 '14 at 15:30
@and31415 yes. the file path is too long for windows to handle it itself. – Aristides Feb 16 '14 at 15:31
Maybe someone will come up with a better solution, but what about booting on a GNU/Linux Live-CD, mounting the Windows partition and just rm'ing the problematic directory ? I think that Linux'es file path limit is way longer than Windows'es so it may work. – user256743 Feb 16 '14 at 15:34
@André that might work, but it is probably my last resort. – Aristides Feb 16 '14 at 15:41
@Aristides Yeah, just making sure. Now it would be interesting to know what actually created the problem in first place. – and31415 Feb 16 '14 at 15:42
up vote 6 down vote accepted

I have not tried this software but you may want to review it and give it a go.

Good Luck.

share|improve this answer
Excellent, good news. – Jim Feb 16 '14 at 16:14

For posterity I'm sharing SiloSix's solution.

He created a bat file to move the folder structure around and delete small chunks at a time. It's simple and beautiful. (I also had several thousands folders to deal with.)

It worked on my problem in less than 2 minutes.


REM  CD deep into the problem directory...
cd D:\a\calculator.sikuli\calculator.sikuli\calculator.sikuli\calculator.sikuli

REM Move the rest of the problem dir to a temporary parent folder
move /-Y calculator.sikuli D:\b

REM CD to the temp folder
cd D:\b

REM delete the section of problem-dir above
rd /s/q D:\a\calculator.sikuli

REM Move the rest of problem-dir back to origin
move /-Y calculator.sikuli D:\a

REM Call the script until problem directory is gone!
call D:\remdirs2.bat

The REM tags are just comments, they can be left in or taken out as you please. (In case the next person to find this isn't versed in bat scripting.)

share|improve this answer
I think that DeepRemove is an easier solution, esp. someone not well versed in using the command line. – Aristides Oct 7 '14 at 23:08
@Aristides By the time I stumbled on this my directory issue has been resolved uaing the batch script so I wasn't able to test DeepRemove out. Some other tools created to solve the same problem hadn't worked, though. So I figured re-posting the script might be beneficial for anyone who stumbled across this. :) – Squish Oct 7 '14 at 23:15

Not the answer you're looking for? Browse other questions tagged or ask your own question.