I've used that method too. switched to using cmd because the GUI has crashed before while making changes to large amounts of data. with more recent versions of windows the more unstable it seems to get.

[–] Brkdncr@lemmy.world 2 points 3 days ago (1 children)

I recently changed the acls on 20tb of documents. On 2cpu and 8gb mem serving a few hundred users.

Seems stable enough for my needs.

[–] sad_detective_man@leminal.space 1 points 3 days ago* (last edited 3 days ago) (1 children)

sheesh, all in one go? I can't get through 1 tb with it even before I start doing hairbrained shit like in my post. on a private machine, with 16gb. I assume that system is on 11?

[–] Brkdncr@lemmy.world 2 points 3 days ago (1 children)

Server 2022, but was previously server 2016 and doing the same things.

Only time there are issues is when someone has used an app to extract files with extremely long folder names and even that hasn’t happened in years.

Ntfs hasn’t changed a whole lot recently so I doubt there’s much difference between server 2022 and win11.

[–] sad_detective_man@leminal.space 2 points 3 days ago

you know I got some torrent files that start to exceed the limit on filenames. I wonder if those are doing something similar. I just assumed newer versions of windows are just running shittier script shells on top of old Windows 7 architecture, but maybe that's worth looking into

but I would guess there are some wide differences between Server 2022 and a consumer Windows build. A lot of effort seemed to get put into transparency visual effects and window transitions. Maybe this is just my bias but I think industry applications are little better stress tested and optimized for things like file management