Windows 10: Help with disabling 8.3 file name creation please!

Hello after I cloned my HDD to my SSD and booted up everything seems to be going smoothly so far, but I noticed that Crucial Storage Executive(program for maintaining my SSD) it says I need to disable 8.3 file name creation. I have found directions on how to do this in windows 7 but nothing that specifically says windows 10 and I don't want to mess with the registry unless I am 100% sure. So can anyone tell me how to go about doing this or if I even need to do it? Thanks in advance.

:)

 

Which programs rely on 8.3 filename creation

Hi Jordan,

Thanks for posting your query to Microsoft forum. I will certainly help you with this.

To know about the 8.3 filename creation, I suggest you to refer to the below link and check if it helps:

How to disable 8.3 file name creation on NTFS partitions


Let us know if you need further assistance. We will be glad to assist you further.

Thank you.

 

Which programs rely on 8.3 filename creation

Original Title: 8.3 filename creation

Which programs rely on 8.3 filename creation? I've heard that disabling 8.3 filename creation improves the performance of the computer, but I also heard that some programs rely on it

 

I can tell you 'how', but I have no idea if it is necessary or advisable (probably not). For a start, this may impact registry entries that use 8.3 names.

From a command prompt you can use the FSUTIL command with its 8dot3name parameter to investigate: Fsutil 8dot3name ...in particular, the 'scan' option!

 

ok thanks I am going to do a little more research before I think about doing anything. My crucial SSD managment software says that with the 8.3 name creation disabled it that it will increase the performance of the SSD. I don't know for sure but I have an email in to their support asking about it, just waiting on a reply right now.

 

Technically that's true, but may come at a price. Anyway, with an SSD the performance is already so good that I doubt you'd notice much difference.

https://support.microsoft.com/en-gb/kb/121007

 

Thanks Bree for the reply, that's about the conclusion I was coming to after the research I have done and you sealed the deal . LOL! Thanks again!

 

I believe the setting was intended primarily for file servers that run few applications but have a busy disk system serving many users. That is what a server is for. In such a system the potential problems are minimal but the benefits significant. In a desktop environment the risks of the setting are much greater but they probably don't create enough files for it to make much difference to performance. In some unusual situations the setting might be useful but not for general use.

 

My first learning of/problems with the LFN/Long File Names thingy with earlier versions of Windows [not Win3.xxx running on top of DOS] was that the HDD File Allocation Table stores 2 names for each file, the 8.3 and the LFN. The down side was a reduction of the number of files allowed in the root of a drive. The maximum with 8.3 was 512 files while LFN reduced that to about half. Storing LFN files in a Folder on a drive bypassed the restriction. I haven't had a need to actually test that with the more-modern Win7 and later OSes but most likely is still about the same.

 

Thanks for all the input and I will have to leave well enough alone it is running fine and I don't want to mess that up. Thanks again