0
I've read about 8dot3name problem when there is a large number of files on a hard drive partition (>300'000 is the general rule of thumb, it seems) but all the sources are at least several years old by now. With recent software and hardware developments, does disabling this legacy feature and stripping all existing short file name entries a good idea?
Using the fsutil 8dot3name strip /t /s /v c:
(where /t
is for testing, so no removal occurs) command I've found that I have 450k+ files with 8dot3names assigned to them on my OS drive and on my HDD, I have over a million. The system drive verbatim output shows a bunch of registry entries, which I suppose won't be removed without the /f
flag, and on the HDD there are no such entries.
There are some older posts on this topic on StackOverflow (from 2008-2011) and here on SuperUser (from 2013) some of which are mentioning Windows 7 tests. There has to have been progress made regarding filesystem handling since then.
Specifically, on Windows 10 at the time of posting (build 1803, November 2018 updates) and when using an m.2 SSD (which is several times faster than a SATA SSD) for the OS drive, will it be beneficial to disable 8dot3name generation and strip all existing entries (leaving only the registry-tied entries)? And what about non-system HDDs?