Backtest consump too massive storage

[Pheaktra Capo]

Hello everybody
I was with fxdreema and done thousand of config MT5 backtest. My PC was kind of beast (14900K/Z790/128G 6400MT/1T NVMe. i back test 12 to 15 tmernimal at the same time (every tick, no visual mode). It was very wll and consumpt total around 250Gb only. But recently, only 1 terminal wipe out my 2Tb drive C. Done lots of solution from ChatGPT, DeepSeek, still cant fix it.

Did it happen to you brothers? ( i tried different broker, new Windows install, change some of PC part. Even different new PC, but it still the same).

The main problem is the MT5 back test with EA(made from fxdreema) consump massive Drive C space. Run until 0 disk space(drive C) and the PC stuttering and stuck).

Please help me fix this problem.

Thanks you guy

@fxDreema

[jstap]

Is unlikely to be FX, is more likely to be what MetaTrader has to download so you can backtest... in simple terms every new chart or day you backtest, the more data your terminal needs to download to do the test.

Try downloading this: https://www.diskanalyzer.com/download
should show you where the space is used, allow you to delete, and let you see the reason for used space.

[Pheaktra Capo]

All the disk space when to MT5 data folder (C/user/PCname/Appdada/Roaming/Metaquotes/Tester and Terminal

Now back test even 1 terminal, my 2TB drive C can get around 2month only and 0 free disk space.

I change 2 PC with fresh windows install already but still can not fix.

[jstap]

Ok, then that says it is the MT5 that's doing it, what I put above will allow you to delete some so you can download different.

[Byens]

what version of windows? I have restarted pc/server and hard disk back to normal. Maybe you should try it too

[Pheaktra Capo]

@Byens I try Win10 22H2 and Win 11 23H2, 24H2, 25H2, with different PC and still the same. (Fresh Windows and chip set driver only)

[Byens]

mine was windows 2025 and ssd nvme, after fresh restart it will always create empty spaces. Maybe bugs only with ssd , anyway all windows problem resolve with restart . Just turn of contents indexed on hard disk properties