Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

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

\myfolder
    \myfolder
    \file.txt
        \myfolder
            \file.txt
                \myfolder
                \file.txt
                    \etc.

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: http://i.imgur.com/CzXsIHY.jpg.

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?

EDIT

currently trying this: http://deepremove.codeplex.com/releases

EDIT 2

Deepremove just froze, just like robocopy, at about level 2,200. Going to attempt sys restore.

EDIT 3

Strike that, DeepRemove is still chugging along.

FINAL EDIT

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
    
Did you try deleting the root folder? –  and31415 Feb 16 at 15:30
    
@and31415 yes. the file path is too long for windows to handle it itself. –  Aristides Feb 16 at 15:31
2  
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. –  André Daniel Feb 16 at 15:34
    
@André that might work, but it is probably my last resort. –  Aristides Feb 16 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 at 15:42
show 8 more comments

1 Answer 1

up vote 2 down vote accepted

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

https://deepremove.codeplex.com/

Good Luck.

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

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

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