# Storage Win10 FileHistory is a living nightmare

Discussion in 'Tech Support' started by Guinevere, 11 Sep 2018.

1. ### GuinevereMega Mom

Joined:
8 May 2010
Posts:
2,484
176
Machine: Win10 VR Beasty, Has a 12TB+ drive pool as well as a M.2 boot.

Mistake: Switching Filehistory on for Windows 10, and letting it use drive pool.

Problem: I run out of space on the drive pool and turns out that FileHistory has used a few terabytes of data.

Fix: Using command line to delete everything is still taking an age, there's still over 5.5million files to delete

Question:

Other than some method that involves moving the 'I want to keep the data' off the pool, and deleting the whole thing is there any way I can quickly delete a 1TB+ folder that contains tens of thousands of nested folders and millions of files? At it stands at the moment I'm going to have to put the delete into a startup batch and get it to chip away at the files bit by bit.

rmdir seems to be the quickest, but on a slow drive pool with this much data it's still silly slow. Quicker than not using cmd, doing it via the desktop would have taken over 1,500 years.

2. ### ChairboyI want something good to die for...

Joined:
10 Jun 2004
Posts:
1,773
112
I've had success deleting 5TB of data using robocopy to copy the contents of an empty directory into the directory I want to delete.

It can go horribly wrong though, so i'd say only do it as a last resort

3. ### RedFlames...is not a Belgian football team

Joined:
23 Apr 2009
Posts:
12,846
1,893
iirc, just using windows built-in stuff...

in powershell:
Code:
Remove-Item x:\path\to\folder -Force -Recurse
in cmd:
Code:
del /f/s/q foldername > nul
rmdir /s/q foldername

using 3rd party tools -

TeraCopy

EDIT:

iirc -

Code:
robocopy [empty folder] [folder you want gone] /purge

Last edited: 11 Sep 2018
Chairboy likes this.

Joined:
10 Jun 2004
Posts:
1,773